Skip to main content
Three controls answer different questions: Auto or Plan sets the intent of your conversation, sprints define a unit of work, and effort controls how deeply a sprint approaches it. Model selection chooses the models used for that work.

​
Auto and Plan

Auto is the default. Plan mode returns to Auto when the plan is produced. Selecting Plan does not itself start a build: send the requirements you want to develop, review the artifacts, then request implementation.

​
Choose a unit of work

For a small change, describe it in chat. Use a dedicated sprint for a defined feature:
/fork <prompt> starts another task in a separate session. In projects with a roadmap, Build Next Task works on the next unit of planned work and Build on Autopilot continues through the roadmap. Availability depends on the project’s plan and active work. Follow the session that owns the run. Parallel work, queuing, and admission limits depend on the client and account; submitting another message is not a guarantee that it starts immediately.

​
Sprint effort

Set effort with /effort before launching the sprint. Higher effort can involve more model work and credits. Effort controls the workflow; it does not promise a particular duration or result. A direct chat change does not necessarily run the full high-effort pipeline.

​
Review the outcome

State the checks you need in the request: for example, type checking, a specific test suite, or a browser journey. Read the actual verification evidence and inspect the diff before shipping.