TaskOutput tool description
SDK-CLI Agent SDK, print mode, v2.1.250. The text the model is given for this tool, line by line, with each line marked against the previous capture taken the same way. One model string produces this prompt.
As described in the system reminder: hook pretool block request, not the ordinary one.
The description, rendered
This renders the markdown inside the description, so it isn’t quite the description itself.The raw view and the plain text are the bytes as they were sent.
DEPRECATED: Background tasks return their output file path in the tool result, and you receive a <task-notification> with the same path when the task completes.
-
For bash tasks: prefer using the Read tool on that output file path — it contains stdout/stderr.
-
For local_agent tasks: use the Agent tool result directly. Do NOT Read the .output file — it is a symlink to the full subagent conversation transcript (JSONL) and will overflow your context window.
-
For remote_agent tasks: prefer using the Read tool on the output file path — it contains the streamed remote session output (same as bash).
-
Retrieves output from a running or completed task (background shell, agent, or remote session)
-
Takes a task_id parameter identifying the task
-
Returns the task output along with status information
-
Use block=true (default) to wait for task completion
-
Use block=false for non-blocking check of current status
-
Task IDs can be found using the /tasks command
-
Works with all task types: background shells, async agents, and remote sessions
What it accepts
3 parameters The JSON parameter schema sent beside this description, 532 characters of it. Name, type, then whether the client marked it required.block
boolean
required
Whether to wait for completion
task_id
string
required
The task ID to get output from
timeout
number
required
Max wait time in ms
sha256 fd31873a9493 · the schema as the client sent it: