DashClaw

60-second proof path

1. Read the loop: DashClaw intercepts risky agent intent, enforces policy, records the decision, routes approval when required, and verifies the final outcome.
2. Run the local demo: npx dashclaw-demo. Expected proof: a simulated high-risk deployment is blocked and opens Decision Replay.
3. Self-host the runtime from the deploy guide, then run npm run doctor locally or dashclaw doctor against the hosted URL. Expected proof: the doctor command exits 0 or names the blocking setup item.
4. Connect one agent with DASHCLAW_BASE_URL and DASHCLAW_API_KEY. Expected proof: one action appears in /decisions, any held action appears in /approvals, and /api/setup/live-proof can capture setup evidence for onboarding or CI.

What DashClaw does

Choose your integration path

DashClaw meets agents where they already are. Every path lands on the same governance primitives, audit ledger, and approval queue — pick the one closest to how your agent already runs.

Coverage at a glance

Working end-to-end examples for each runtime live in examples/ — anthropic-governed-agent, autogen-governed, claude-code-review-agent, codex-review-agent, crewai-governed, langgraph-governed, managed-agent-governed, managed-agent-mcp, openai-agents-governed, and more.

1. Coding-agent plugins (Claude Code, Codex, Hermes Agent)

One plugin source, three ecosystems. Distributed via plugins/dashclaw/. Each manifest ships the MCP server config, the dashclaw-governance protocol skill, the dashclaw-platform-intelligence reference skill, and a distinct agent_id so Mission Control separates sessions per host.

# Claude Code — no clone needed: the CLI downloads the hooks bundle from your
# instance, wires ~/.claude/settings.json, and defaults to observe mode
npm i -g @dashclaw/cli
dashclaw install claude            # prompts for endpoint + API key
dashclaw install claude --trial    # browser signup on a hosted instance, paste the key

# Codex — installer wires manifest, hooks, and AGENTS.md governance protocol
node cli/bin/dashclaw.js install codex --project /path/to/your/project

# Hermes Agent — 8 lifecycle hooks (pre/post tool, pre/post LLM, on-session
# start/end, secret redaction, subagent_stop ROI tracking)
bash scripts/install-hermes-plugin.sh        # macOS / Linux
powershell -File scripts/install-hermes-plugin.ps1   # Windows

For Claude Code specifically, dashclaw install claude governs Bash, Edit, Write, MultiEdit, sub-agent spawns, and every mcp__* tool call with semantic classification, risk scoring, and per-turn token capture — no SDK calls in your agent code, no repo clone. It starts in observe mode (decisions logged, nothing blocked); flip to enforce by setting DASHCLAW_HOOK_MODE=enforce in ~/.dashclaw/claude-hooks/.env. Working from a checkout instead, npm run hooks:install does the same wiring. Full details in hooks/README.md.

Verify it fires: pipe a fake tool call through the hook — a clean exit (and a guard evaluation when DashClaw is reachable) confirms the wiring. Use python3 if your system has no python on PATH; the installer picks the right one automatically.

echo '{"tool_name":"Bash","tool_input":{"command":"echo hello"},"tool_use_id":"test_001","session_id":"smoke"}' | python .claude/hooks/dashclaw_pretool.py

2. MCP server (zero code, any MCP host)

@dashclaw/mcp-server exposes 30 governance MCP tools across 11 groups — core governance, optimal files, session continuity, credential hygiene, skill safety, open loops, learning + retrospection, agent inbox, agent identity, behavior learning, governance posture — plus 6 read-only resources (dashclaw://policies, dashclaw://capabilities, dashclaw://agent/{agent_id}/history, dashclaw://status, dashclaw://code-sessions/projects, dashclaw://code-sessions/sessions/{session_id}).

As of v2.0.0 the local stdio server also carries governed execution: provider tools for GitHub, Vercel, Neon, Stripe and ten more (each registering only when its credential env var is present), and stateful launch plans (create_launch_plan / get_launch_status / preflight_launch / verify_launch) that track the launch tail with reality-checked, never self-reported completion — every step through the same guard/policy/approval path. See mcp-server/README.md and mcp-server/docs/launch-plans.md.

Stdio (Claude Code, Claude Desktop, any stdio MCP client):

{
  "mcpServers": {
    "dashclaw": {
      "command": "npx",
      "args": ["@dashclaw/mcp-server"],
      "env": {
        "DASHCLAW_URL": "https://your-dashclaw.vercel.app",
        "DASHCLAW_API_KEY": "oc_live_xxx"
      }
    }
  }
}

Streamable HTTP (Claude Managed Agents, any remote MCP client): every DashClaw instance serves MCP at /api/mcp — no npm package, no client install.

agent = client.beta.agents.create(
    name="Governed Agent",
    model="claude-sonnet-4-6",
    tools=[{"type": "agent_toolset_20260401"}],
    mcp_servers=[{
        "type": "url",
        "url": "https://