task_run
Create a task on a team's wall with priority, horizon, tags, and dependencies so agents can pick it up and report progress; it adds the task but does not execute it.
Instructions
Put a task on a team's wall. Nothing executes it — an Agent has to pick it up.
The name is historical: there was once a worker pool that would "run" the task. That pool is retired; this tool only creates the row. Dispatch is yours to do (Agent(...) / SendMessage), and the sub-agent then writes progress back with task_memo_add.
Priority and horizon drive the task wall's ordering, so set them here — the old docstring told callers to "set priority and horizon" while the signature had no such parameters, and any value passed was silently dropped (fixed 2026-07-27).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"team_id": "<team_id>",
"description": "<description>"
},
"name": "task_run"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Free-form tags for filtering the wall | |
| model | No | Specify model to use (optional, metadata only) | |
| title | No | Task title (optional) | |
| horizon | No | "short" (default) / "mid" / "long" | |
| team_id | Yes | Team ID or name | |
| priority | No | "critical" / "high" / "medium" (default) / "low" | |
| depends_on | No | Dependency task IDs — task auto-unlocks when they complete | |
| assigned_to | No | Agent name/id this task is meant for (optional) | |
| description | Yes | Task description |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||