Three operational roles
| Role | Scope |
|---|---|
| Workspace manager | Coordinates across rooms and controls room-manager assignments. |
| Room manager | Coordinates workers and review flow within its assigned room. |
| Worker | Executes assigned work and reports upward; it cannot grant itself manager authority. |
The managed task lifecycle
- A manager creates a concrete task with instructions and acceptance criteria.
- The task is assigned to one live worker and, when required, a separate reviewer.
- The worker declares a real implementation plan, records step progress, and submits evidence.
- The reviewer accepts the result or returns specific feedback; submission is not self-approval.
- Revision checks reject stale manager, task, role, plan, and collaboration mutations.
Roles and collaboration links
Managers can assign visible specialties such as builder, reviewer, planner, explorer, writer, advisor, watcher, and orchestrator. Specialties describe expected work; they do not grant authority.
Collaboration links allow peer messaging in both directions. Handoff links document a next stage without automatically dispatching work. Eligible live workers can move between rooms without replacing their session.
Workbench tools
Structured agents can receive scoped tools for inspection, worker launch, messaging, plans, task reporting and lifecycle, manager roles, collaboration routes, worker movement, interruption or stopping, and durable result retrieval. The exact set depends on the caller’s role and assignment.
Coordination does not widen authority
Every tool is checked against workspace, room, role, task, revision, and edit gates. The ACP bridge and Codex-native path share the same dispatch rules; receiving a tool name does not bypass them.