task-intake-router

Route Copilot CLI requests by applying explicit intake routing to evaluate the incoming request and assign the correct mode, agent type, and model. This prevents defaulting to the wrong execution path out of habit and ensures predictable handoffs.

Use Plan Mode for structured decomposition and planning before coding multi-file features, and switch to Autopilot for autonomous execution with guardrails. Plan Mode handles complex decomposition, while Autopilot executes tasks within defined safety boundaries.

Delegate typed tasks by routing incoming requests to specific task agents like explore, task, general-purpose, or code-review. This ensures each request is matched to an agent type optimized for its specific execution and analysis requirements.

Yes, you can route requests to /fleet for parallel execution or use background delegation to cloud execution to generate draft PRs. These modes handle fan-out scenarios where multiple tasks need to run concurrently.

Optimize cost and quality by applying per-agent model overrides during the routing process. This allows you to match specific model capabilities to the complexity and security sensitivity of each delegated task.

Copilot CLI defaults to the wrong mode because routing decisions are often made by habit rather than explicit intake. Applying structured routing dimensions and guardrails ensures security-sensitive reviews are directed to the correct plan-first or typed agent path.