Skip to main content
Ask for something substantial and Corbits Code does not attempt it alone. It classifies the work, dispatches specialists, and synthesizes what they send back. Ask for a feature and an implementer goes and builds it while a reviewer reads what came back. Ask for a survey of an unfamiliar tree and an explorer goes and reads it, unable to change a line while it does.
This page describes Corbits Code, the app. It does not describe credentials or grants held by the control plane, and it does not speak for the shared agent runtime.
Two words are worth separating before the rest makes sense. A director is a role definition that ships with Corbits Code: one job, an explicit list of work it must refuse, a system prompt, a tool envelope, an authority tier, and the shape of report it owes back. An agent is a running instance. Your session is one. Every specialist it dispatches is another. Directors are what agents are made from, and they do not change while you work. (director definitions; director registry)
On the Corbits Code overview, a reactor director governs event-loop policy, while fleet directors define dispatchable roles and their authority. Corbits Code composes both in a session. Where this page says “director” on its own, it means a fleet role. (event-loop policy; director definitions)

​
Authority is a tier, not a prompt

Every director carries one of three tiers, and the tier decides what it may do to the rest of the tree.

Orchestrator

Tier 1, the primary agent. Full fleet control over the whole tree.

Nested orchestrator

Tier 2. May manage only its own descendants, never a sibling and never anything above it.

Leaf

Tier 3, the workers. Each carries an explicit tool allowlist sized to its job, finishes with a report envelope, and mounts no fleet verbs at all.
The check runs where tools are assembled, not in prompt wording. That is what makes the tiers worth anything: a reviewer that cannot write is not a reviewer that has been asked nicely not to, and no amount of conversation hands a leaf a fleet verb it was never mounted. Same pattern as the safety middleware, one layer owning the constraint.

​
Picking a specialist

Dispatch by intent and take the default, or name a director directly. implement defaults to build, explore and plan default to directors of the same name, and review defaults to critique. Naming an id that is not registered fails with the list of valid ones rather than quietly falling back to something general. The shipped fleet is a closed set, and its names are reserved. A profile is the general shape a dispatchable role takes, the same job/prompt/tool-envelope/tier/report-shape as a director, just not in that closed set. Roles of your own are still yours to add, as profiles, from a plugin or your project tree. What you cannot do is take a director’s name: a profile whose id collides with a shipped director is skipped at load, so a director can never be quietly replaced by something wearing its id.

​
Working a live fleet

Workers are sessions you can steer, not fire-and-forget calls.

​
How a run ends

A worker runs until it produces a report envelope: a structured Summary, Findings, Blockers, and Paths. Short of that, it stops for one of four recorded reasons. It was cancelled by the operator, it hit an opt-in wall-clock deadline, it stalled after a long silence with no tool activity, or it narrated an answer instead of writing an envelope. (director definitions; director tool sets; worker lifecycle) None of those is a turn count. Turn budgets were removed outright, including the maxTurns setting, the per-director cap, and the argument on the dispatch tools. A worker is bounded by the clock, by its own completion, or by you, and never by a number of inference passes it was allowed to spend.

​
Support

Help Center

Join hundreds of developers building with Corbits and speak with the team directly.