Ops Deck
Analysis
Ops Deck appears to be a disclosed local dashboard setup guide, but it involves local services, package installs, persistent processes, and sensitive local operational/code data that users should review before installing.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
npm install -g pm2 pip install fastapi uvicorn aiofiles ollama pull qwen3-embedding:8b
The setup relies on external package/model downloads, including a global npm install and unpinned Python packages. This is expected for the dashboard stack, but users should review and pin dependencies if needed.
PM2 (process manager)
The dashboard expects persistent local services managed by PM2. This persistence is coherent with a self-hosted dashboard and is not hidden, but users should know it can keep running after setup.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Semantic search across your entire codebase using local embeddings.
The code search feature indexes local source code into embeddings. The artifact says this is local and purpose-aligned, but codebases can contain secrets or private business logic.
Tabbed viewer for your agent configuration files: AGENTS.md, SOUL.md, TOOLS.md, USER.md, MEMORY.md, IDENTITY.md.
The dashboard is designed to display agent configuration, memory, identity, and user files. This is disclosed and relevant to the tool, but those files may contain sensitive personal or operational instructions.
