dispatch-subagent

To dispatch a subagent with auditability, you provide a scoped task description and target a defined agent role. The subagent operates only within a specified directory scope while logging the full dispatch prompt and mandatory result updates.

The controller worker dispatch pattern separates task coordination from execution by isolating subagents with curated context. Use this pattern for complex tasks that require reproducible steps, clearly defined directory scope, and traceable execution logging.

You restrict subagent access by providing a scope_directory along with include and exclude rules for subagent inputs. This ensures the dispatched agent operates strictly within the defined directory boundaries and logs the full dispatch action.

Yes, you can curate context for an isolated subagent by defining include and exclude rules for inputs. The controller dispatches the subagent with this curated context to maintain clean separation of concerns while enforcing mandatory dispatch logging.

Dispatching isolated subagents does not require manual logging because the process enforces mandatory dispatch logging automatically. It records the full dispatch prompt and updates results to guarantee traceable execution and auditability.

Using a controller to dispatch isolated subagents requires a clearly defined directory scope and curated context for each task. Without strict include and exclude rules, the separation of concerns and auditability benefits are diminished.