feat(orchestrate): let a dispatch override the profile's fast mode - #322
Merged
Merged
Conversation
Add an optional `fast` parameter to the orchestrate `dispatch` tool. `true`/`false` overrides the child profile's fast-mode setting for that one child; omitted, the profile decides. The tool description, fleet table intro, and the three orchestrator prompt assets tell the lead to pass it only when the user explicitly asks for fast mode on or off. Providers without a fast mode still ignore it. Verified: clippy clean, cargo test --workspace green, including a new runtime test covering both override directions.
Add an optional `fast` parameter to the orchestrate `send` tool. It rewrites the child's fast-mode selection (Claude `fastMode`, Codex `fast` service tier) and persists it, so the existing launch-option restart machinery resumes the child on a fresh process before its next turn. A turn already running keeps its speed; the tool description and the orchestrator prompt assets tell the lead to cancel first and then send with `fast` set when the user wants work in progress sped up. Verified: clippy clean, cargo test --workspace green, including a new runtime test that the switch persists on both the resident and the index and flags a live child for restart.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two related additions so the lead model can control a child's fast mode on the user's explicit instruction:
dispatch
fast?—true/falseoverrides the child profile's fast-mode setting for that one child; omitted, the profile decides. Providers without a fast mode ignore it.send
fast?— switches an already-dispatched child's fast mode. The selection is rewritten and persisted, so the existing launch-option restart machinery resumes the child on a fresh process before its next turn. A turn already running keeps its speed; to speed up work in progress the lead cancels first, then sends withfastset, and the child resumes its transcript on a fresh process.The tool descriptions, the fleet-table intro, and the three orchestrator prompt assets tell the lead to pass
fastonly when the user explicitly asks.Verified: clippy clean, cargo test --workspace green, with new runtime tests for both override directions on dispatch and for the send switch persisting and flagging a live child for restart.