trinity_dispatch_auto
Automatically select the appropriate agent for a task using the local route table, create a durable task, and run one worker cycle. Use when manual agent selection is not desired.
Instructions
Resolve the best Trinity agent with the local route table, create a durable task, and run one worker cycle. Use this when the caller has a task but should not pick the agent manually; use trinity_dispatch for an explicit target. This writes route evidence and task state to the local database and may execute the selected agent command; the result includes compact task and route metadata.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | Working directory passed to the selected agent; defaults to the user's home directory. | |
| task | Yes | Task prompt used for route selection and delivery. | |
| wait | No | If true, block until the routed task reaches a terminal state or wait_timeout expires. | |
| task_type | No | Optional task type hint that can override or narrow route matching. | |
| source_agent | No | Originating agent id recorded on the task; defaults to mcp. | |
| wait_timeout | No | Maximum seconds to wait when wait=true; defaults to the server wait timeout. | |
| previous_agent | No | Agent id to avoid when resolving opposite-review or retry routes. |