RUSH Deep Tasks
Start through Task in the AI panel or the current command entry. Specify goals, constraints and acceptance criteria. This guide does not promise a dedicated launch shortcut. Save existing work, review the plan and affected files, then inspect Changes and test results.
Workflow
Planner decomposes tasks and dependencies. After you approve the plan, Coder edits code and Verifier runs project checks. Failures may trigger diagnosis and replanning. Parallel execution and worktrees depend on the execution path and repository conditions; not every task or Coder uses an independent worktree. A worktree is not a runtime security sandbox.
Current production verification wires V1 static checks, V2 unit tests and conditional V3 integration tests when suitable project commands exist. Missing integration-test commands do not count as passing integration verification. Checks cannot guarantee all business requirements; review changes and run your own acceptance workflow.
Models, Configuration and Billing
Models and limits depend on configuration and the actual request path. There is no guarantee of optimal automatic model selection, fixed completion time or cache savings. See configuration for global configuration location. Hosted requests consume credits based on model usage; BYOK follows provider billing. Subtask counts do not imply a fixed bill.
Recommendations
- Provide runnable tests and explicit acceptance criteria.
- Inspect tool output and failures rather than only the final summary.
- Check cross-file conflicts and preserve existing uncommitted work.