Argus
An AI manager that orchestrates multiple coding sessions in parallel — reading your mission, spawning child agents in git worktrees, and monitoring their progress.
Argus is a session-backed agent orchestrator. It's a long-running harness session (Claude Code, Codex, or OpenCode — whichever you have as your default) that reads a mission note you write, then spawns and manages coding sub-agents — each in its own git worktree — to execute the work in parallel.
Creating an Argus
- Open the Creation Picker (Cmd+N).
- Select Argus.
- Give it a name and pick or create a Mission note.
The Mission note is a Scape note where you write your instructions — what repos to work on, what tasks to complete, constraints, priorities. Argus stays idle until the Mission note has content.
How it works
Argus runs on a pulse timer (configurable from 30 seconds to 4 hours). On each pulse it:
- Reads the Mission note for instructions.
- Evaluates the current state of its child sessions.
- Spawns new child sessions as needed — each in a fresh git worktree.
- Reports status and progress.
Children are real coding sessions with full capabilities. They can edit files, run tests, create PRs — everything a normal session can do.
Child sessions
When Argus spawns a child, it:
- Creates a git worktree via
create_worktree. - Launches a coding session in that worktree via
create_session. - Seeds the child with full auto-approve for coding tools (edit, write, bash) so it's never blocked on permissions.
Limits
- Max children: Defaults to 8. Configurable (2, 4, 8, or 16) via right-click on the Argus card.
- Spawn depth: Children cannot spawn further children — depth is limited to 1.
Risky tools
By default, children are denied risky tools (playbooks, remote execution, external browsing). You can enable these per-Argus via right-click → Allow risky tools for new children.
Monitoring
Status pill
The Argus card in the sidebar shows a status pill:
| Status | Meaning |
|---|---|
| Watching (green) | Actively pulsing and managing children |
| Paused (grey) | Click to resume |
| No mission | Needs a Mission note assigned |
Click the pill to toggle between Watching and Paused.
Log table
Argus automatically provisions a table and appends structured log entries on each pulse — timestamp, event kind, child info, repo, status, and summary. Open it via the database icon on the Argus card header.
Fleet view
Click the Argus card to open its backing session (the manager's terminal). Child sessions appear nested beneath the Argus card in the sidebar.
MCP tools
Argus uses two capability-gated MCP tools:
get_argus_status— returns the fleet view: the Argus's own state plus every child's live activity.set_argus_log_store— binds a table as the Argus's log table.
These are gated by a per-Argus capability secret (SCAPE_ARGUS_CAP env var) that prevents other sessions from impersonating the Argus.
Deleting an Argus
Right-click the Argus card → Delete Argus. A confirmation dialog lets you choose whether to close child sessions or keep them running independently.