choosing-task-vs-main-session

Dispatch a Task subagent for codebase exploration or parallel subtasks, but stay in the main session for context-dependent implementation requiring iterative user feedback to minimize context loss.

Handle multi-file exploration by dispatching an Explore Task subagent. This isolates the search process, returning only summarized results to the main session to preserve your working context.

Execute parallel subtasks by dispatching multiple specialized Task subagents simultaneously. This allows independent operations to run concurrently, aggregating results back into the main session workflow.

Overusing Task subagents for context-sensitive work causes problems because delegated subagents lack the accumulated session context, leading to disjointed iterative refinement and potential context loss.

Yes, the main session workflow supports iterative refinement better when user feedback is needed mid-task. It maintains continuous context, whereas Task dispatch isolates the process from ongoing collaboration.

Choose between Task-based exploration and main-session work by evaluating if the operation needs parallel execution or context-dependent collaboration, then apply the decision pattern to recommend the optimal flow.