The Pulse
Kiro makes Conductor mode available in standard Crew builds
Kiro Crew's conductor mode lets users give a goal to an agent that delegates work to worker agents and tracks tasks on a shared board. Version 0.13.0 turns the mode on in every standard build, while the LTS edition does not offer it.

Kiro Crew users can now give a coding goal to a conductor agent that divides it among worker agents and tracks their reports on a shared board. The mode uses the default Kiro Crew agent and global memory to coordinate work toward a defined goal, Kiro said.
Kiro previously called the feature Ultra Mode and kept it behind a developer preview setting. Kiro’s November 19 changelog says version 0.13.0 enables conductor mode in every standard build without a preview switch; it is not available in the LTS edition.
From goal to coordinated tasks
The switch appears in the composer for a new chat. Starting new chats in conductor mode by default is a separate setting that is off initially; the board also offers controls to pause and resume running workers, including sub-teams.
The feature sits between a single chat for a focused task and a Kiro bot that handles a continuing responsibility. A user sets the goal, while the conductor delegates tasks and reviews results; the user can adjust direction and see progress or items awaiting review in one chat and board.
Kiro says the feature grew out of work on browser usage, which lets an agent drive a browser window. Changes to that work were spread across chats, making it difficult to carry decisions and context between sessions.
One example was a planned ability for a person to take control of the browser from an agent and hand it back. That required work across the interface, the agent loop and testing, including a way to pause the agent during the takeover.
Ledgers, patrols and checks
The default conductor has no direct file-editing tool and delegates changes to workers. Each worker is assigned one task and uses work_report to report progress, completion, a blockage or a question, with evidence such as a pull request; the conductor reads the board through work_ledger_read.
State is stored outside the chat in an append-only crew log. The work ledger stores tasks and results, while a session ledger records the goal, next step and approaches already rejected. Kiro says the arrangement lets the conductor resume from saved state after a connection drops rather than relying solely on summarized chats.
A patrol check reads the work ledger and skips a model turn when nothing needs attention. When a worker reports that it is done, blocked or has a question, the next patrol check moves up. Assigning a worker also attempts to start a patrol if none is running, and Crew flags a missing patrol.
Worker reports do not by themselves establish that a task is complete. The procedure accept_eval checks evidence against the task’s completion condition, such as pull request checks or a pending request for a person’s approval. After three failed checks, the procedure tells the conductor to close the task as rejected.
What internal tests exposed
In one internal run, Kiro gave a conductor a queue of open repository tickets and instructed it not to write code. Kiro says the agent coordinated workers and checked their reports, but also made an incorrect judgment about failing checks on a pull request.
In that case, the conductor saw no failing checks on the main branch and attributed the failures to the worker’s changes, even though the main branch did not run the same tests. It later found the same failures on other pull requests and a fix already merged to main, then corrected its judgment. Kiro says the worker had not acted on the incorrect call and instead waited for the fix and rebased.
On another ticket, Kiro says the conductor sent a tradeoff to a person rather than making a quick fix that would have let unapproved scheduled scripts read cached credentials. The company described that as a security-boundary decision it wanted a person to review.
Sources
- Original source · Blog post Kiro · Conductor mode kiro.dev
Other pages read
- Kiro · page 2 kiro.dev