Agent Teams
Most requests can stay Solo. Solo collaboration can use reusable research helpers and isolated coding helpers. Helpers inherit the active provider, account, model, and reasoning settings; the coordinating agent reviews their evidence and validates combined changes. Non-Git or unsupported coding snapshots fall back to research instead of shared writes. Grill remains a one-question-at-a-time clarification flow and does not modify the project.
Choose an explicit team when you need named provider routes, roles, access ceilings, a dispatcher plan, dependency-ordered writers, team budgets, durable assignment history, or a final reviewer.
In a Work conversation, choose Solo or team… from the composer workflow menu to select the route for the next request.
Fixed boundaries
- A dispatcher can route only to profiles in the selected team.
- Hosted members require one-time Automatic Hosted Routing consent.
- Read-only specialists may overlap; write-capable jobs are ordered or isolated in bounded parallel worktrees.
- Each team has bounded jobs, rounds, concurrency, model calls, and tokens; monetary controls are estimates subject to available usage and price coverage.
- Credentials, hidden reasoning, and provider signatures are excluded from durable run history.
- Computer Control is foreground-only, writer-only, and globally exclusive.
Teams use the same permission mode and hard safety boundaries as Solo work. Selecting a team never grants broader access by itself.
Runs now has its own inspector icon. The orchestration glyph belongs to the team dispatcher, making the difference between “open run history” and “route a team” explicit.
Agents, specialists, goals, and capsules
In 3.0, the Agent page configures saved agents with persistent chats and optional schedule, event, and price triggers. Specialists & teams configures reusable behavior, models, and access ceilings for delegated work.
An ordinary Solo or team chat can use a Persistent Goal for continued work across turns. Task Capsules save a detailed plan with planning, implementation, and optional review profiles. Each keeps its own execution and recovery controls.
Duo is a lighter way to pick just a planner and a builder. Teams remain useful when you need explicit multi-role routing. Team repairs retain their consumed allowance, rerun affected checks, and require a current valid review; a stale or malformed verdict does not approve work. Reusable Checks can add explicitly approved project requirements to future team tasks.