Start a run
Orchestration requires an explicit user request and ULTRA, including help/control commands. Prerequisites: authentication/plan, clear task, reviewed workspace and budget.
Note: The following command sends model requests, may incur costs and may write result files.
/orchestrate --mode plan --max-cost 20 Prepare a validation plan with acceptance criteria
Modes are ask, plan, agent and auto; auto follows the current mode. Ask returns an answer, Plan produces a plan and Agent performs implementation. A plan result does not automatically authorize implementation. The total budget defaults to 20 EUR, with a minimum of 5 EUR. Supply a finite number. This is a cumulative cost limit, not a balance reservation or duration guarantee.
| Flag | Effect |
|---|---|
--mode | ask/plan/agent/auto. |
--max-cost | Cumulative EUR limit. |
--model | Public selection for all roles unless individually overridden. |
--planner-model, alias --analyst-model | Planning/analysis selection. |
--implementer-model, alias --architect-model | Implementation selection. |
--reviewer-model, alias --critic-model | Review selection. |
You can supply flag values separately or with =. If a flag occurs more than once, the last value takes precedence; -- ends option parsing. Select models from the public list. A large task alone does not trigger automatic orchestration.
Status, budget and resume
Note: Increasing the budget permits further spending. abort stops the run but does not guarantee that earlier file changes are undone.
/orchestrate status <run-id>
/orchestrate budget <run-id> 30
/orchestrate resume <run-id>
/orchestrate abort <run-id>
Replace <run-id> with the actual run ID. status, resume and abort each require exactly one ID; budget also requires a new total limit. You can raise the budget only while the run is waiting for a budget decision (waiting_budget) and that decision is still pending. The new limit must exceed the existing limit and costs, and is capped by your available balance. After changing the budget, explicitly continue with resume.
resume uses the saved prompt, mode and budget rather than starting a new run. Budget pauses, handoffs, partial results and failures are different states. abort stops the run but does not guarantee file rollback. Review existing results and changes.
No cancel, pause or start subcommands. cancel can be interpreted as a new start prompt! Use only documented controls. Aborting is not deleting files/sessions.
Connect the IDE
/ide
/ide enable
/ide disable
Without an argument, /ide shows connection status. enable connects an available compatible IDE extension for file changes and linter diagnostics; disable disconnects it. There is no separate diagnostics subcommand or comprehensive health check. Unknown arguments simply show status.
Troubleshooting
If your plan is rejected, check that ULTRA is active. If the budget is unchanged, check the waiting state, new total limit and balance. Changing the budget requires a separate resume command afterwards. If the IDE is disconnected, check that a compatible extension is installed and reachable. After abort, do not assume changes have been reverted.