Features
Agent Squad Monitor
The Squad Monitor gives you real-time visibility into every agent running in your workspace. Each agent gets its own execution lane — so you can supervise without micromanaging.
Execution lanes
Each agent lane shows:
- Agent nameThe model and role (e.g. Coder-GPT4o, Tester-Claude).
- Current taskThe Kanban card the agent is working on, with a direct link.
- Progress barEstimated completion based on Shard size and agent throughput.
- Status indicatorActive (green) / Waiting for input (yellow) / Failed audit (red).
- Decision TraceThe last Manifest line followed and any assumptions made. Click to expand.
The Orchestrator lane
The top lane always belongs to the Orchestrator. It shows:
- Shards queued for audit
- Current audit in progress (diff view available)
- Shards passed, failed, or in the Fallback Ladder
- Assembly Success Rate (rolling 7-day)
Parallel agent coordination
Multiple agents can run simultaneously in separate lanes. The Orchestrator manages hand-offs automatically: when Agent A produces output that becomes Agent B's input, Alfred routes it without any human involvement. You can watch cross-lane dependencies resolve in real time.
When a lane turns red
A red lane means the Shard failed the Orchestrator audit. The Fallback Ladder activates:
- 1Auto-retry — Orchestrator refines the prompt and retries the agent automatically.
- 2Human hint — Alfred flags the card and asks you to add 1–2 lines of clarifying context.
- 3Human dev — If both fail, the Shard is marked red and routed to a human developer.