session-threads changedmanaged-agents/session-threads
Nearest release: v2.1.301, published 5 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+4added
Lines−5removed
From line
695
where the diff opens
First seen
9 Oct 2026
this site's first read of the page
Recorded edits11to this page, all time
The whole hunk
from line 695, old and new numbered
/
from line 695
695695
696696The following example goes inside the event loop of the [tool confirmation handler](https://platform.claude.com/docs/en/managed-agents/events-and-streaming#tool-confirmation). For each ID in `stop_reason.event_ids`, it sends a `user.tool_confirmation` that allows the call. The same pattern applies to `user.custom_tool_result`, which you can also send as soon as its `agent.custom_tool_use` event arrives.
697697
698<CodeGroup>
698<CodeGroup exclude="shell:CLI">
699699 ```bash cURL
700700 while IFS= read -r event_id; do
701701 jq -n --arg id "$event_id" \
from line 709
709709 done < <(jq -r '.stop_reason.event_ids[]' <<<"$data")
710710 ```
711711
712 ```bash CLI
713 # This workflow does not translate well to a one-off shell command.
714 # Use one of the SDK examples in this code group instead.
715 ```
712 <CodeGroupItem language="CLI">
713 This workflow needs more logic than a single shell command. Use the [Claude SDK](https://platform.claude.com/docs/en/cli-sdks-libraries/overview) to run it.
714 </CodeGroupItem>
716715
717716 ```python Python
718717 for event_id in stop.event_ids:
No line in this hunk matches that.