Guide · Tasks and delegation · 9 min read

Tasks and Delegation

Delegation is useful when the task is bounded, the route is appropriate, and the output remains inspectable.

What delegation means

In Kaptain, delegation is handled through the delegate_task Krew Tool. The user enables it in Krew Tools settings and configures the model route it should use. When available, suitable subtasks can move away from the primary reasoning model to that configured delegate route.

The delegate receives a focused goal and returns a result for review, compression, or final synthesis.

This can reduce pressure on premium models, but only when the assignment is appropriate. Delegation is not automatic quality improvement.

Good delegation candidates

• Search summaries and evidence packaging.
• Rough classification or extraction.
• Log summarization and repetitive helper passes.
• First-pass context compression before premium reasoning.
• Private low-risk preprocessing with a suitable local route.

Poor delegation candidates

• Final production-impacting decisions.
• Security-sensitive reasoning without human review.
• Tasks requiring deep cross-file judgment when the delegate lacks enough context.
• Actions where a wrong answer would be more expensive than a premium route.

Review the delegated result

A delegated result should show what goal was assigned, which route was used, what evidence was considered, and what came back. If the output is uncertain, the final route should know that rather than smoothing it into false confidence.

Cost discipline without quality collapse

The goal is not to make everything cheap. The goal is to stop routine work from consuming the same route as difficult reasoning. Keep premium models available where they change the outcome, and move only suitable work elsewhere.

Continue with Choosing Model Routes and How Kaptain Reduces Unnecessary Token Spend.