docs: add agent control interfaces section to CLAUDE.md

This commit is contained in:
Nyk 2026-03-21 21:41:36 +07:00
parent 7994aa6c6c
commit a9d9005bac
1 changed files with 25 additions and 0 deletions

View File

@ -72,6 +72,31 @@ Database path: `MISSION_CONTROL_DB_PATH` (defaults to `.data/mission-control.db`
- **Icons**: No icon libraries -- use raw text/emoji in components - **Icons**: No icon libraries -- use raw text/emoji in components
- **Standalone output**: `next.config.js` sets `output: 'standalone'` - **Standalone output**: `next.config.js` sets `output: 'standalone'`
## Agent Control Interfaces
Mission Control provides three interfaces for autonomous agents:
### MCP Server (recommended for agents)
```bash
# Add to any Claude Code agent:
claude mcp add mission-control -- node /path/to/mission-control/scripts/mc-mcp-server.cjs
# Environment config:
MC_URL=http://127.0.0.1:3000 MC_API_KEY=<key>
```
35 tools: agents, tasks, sessions, memory, soul, comments, tokens, skills, cron, status.
See `docs/cli-agent-control.md` for full tool list.
### CLI
```bash
pnpm mc agents list --json
pnpm mc tasks queue --agent Aegis --max-capacity 2 --json
pnpm mc events watch --types agent,task
```
### REST API
OpenAPI spec: `openapi.json`. Interactive docs at `/docs` when running.
## Common Pitfalls ## Common Pitfalls
- **Standalone mode**: Use `node .next/standalone/server.js`, not `pnpm start` (which requires full `node_modules`) - **Standalone mode**: Use `node .next/standalone/server.js`, not `pnpm start` (which requires full `node_modules`)