product

Director Console

The dashboard for the human who is steering the agents.

The role

The new role this category needs is the director. A director is not the person who types the most. They are the person who knows what each agent should be working on, how those workstreams relate, and when one of them is going off the rails.

What the console shows

Three things, at all times:

1. Nodes. Every machine docked to the project, with a live status (idle, thinking, awaiting input, blocked).
2. Threads. Every active conversation, with the intent, the agent’s current step, and the files being touched.
3. Output. The latest preview URL (Phase 3+), the most recent test run, the most recent telemetry event, and Recaps of completed Threads.

What the console enables

• Interrupt and redirect. The director can step into any Thread and add a prompt mid-stream (Phase 2 — view-only in v0.1).
• Approve and merge. When a Thread produces a candidate change, it surfaces here for human approval before it lands.
• Reassign. Nodes can be moved between branches without restarting the agent.

Why the director matters more in Phase 2

In single-user Phase 1, you are your own director. In team Phase 2, the director is a real role with real leverage — one experienced person can credibly steer three or four agentic workstreams at once.