Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One capture · api

One read of Claude Developer Platformapi-20261112T160709Z

52 pages moved out of 904 read.

Pages moved 52 significant first
Pages read 904 in this capture
Captured 16:07 UTC
Corpus hash 0908a26ac580 corpus-hash

What this read moved

51-52 of 52, page 3 of 3

This capture is too large to show at once. Changes 51-52 of 52 are below, significant first; the rest are on the following screens.

managed-agents/multiagent-orchestration Changed · +1 / -1 lines

from line 1317
131713174. `session.thread_status_idle` (`stop_reason: end_turn`)
131813185. `session.thread_status_terminated`
13191319 
1320No `agent.tool_use` events are emitted for a consultation, and no `agent.thread_message_sent` event appears on the session’s event stream, because the consultation input is composed by the platform rather than sent by the agent. If you list the advisor thread’s own events, the advice also appears there as an `agent.thread_message_sent` event. The advice delivery (event 3) is not guaranteed to arrive before the advisor thread’s idle and terminated events, so don’t treat those as a signal that the advice has already been delivered.
1320A consultation emits no `agent.tool_use` events, and no `agent.thread_message_sent` event appears on the session’s event stream. The platform composes the consultation input, so the agent doesn’t send it. If you list the advisor thread’s own events, the advice also appears there as an `agent.thread_message_sent` event. The advice delivery (event 3) is not guaranteed to arrive before the advisor thread’s idle and terminated events, so don’t treat those as a signal that the advice has already been delivered.
13211321 
13221322Whether your client can read the advice is the advisor model’s policy. It mirrors the [result variants](https://platform.claude.com/docs/en/agents-and-tools/tool-use/advisor-tool#result-variants) split on the Messages API advisor tool. An advisor model that returns plaintext results there delivers readable text here. One that returns redacted results delivers a `[{"type": "redacted"}]` placeholder on every client surface, while the agent still reads the full advice server-side. The preceding example uses the newest Opus model available to you as the advisor. It returns redacted results, so your client sees only the placeholder. To read the advice on the event stream, use an advisor that returns plaintext, such as Claude Opus 4.8. A model’s policy can change with no change to the API, so handle both `text` and `redacted` blocks. Some agent models pair only with redacted-result advisors; see the advisor tool’s [Model compatibility](https://platform.claude.com/docs/en/agents-and-tools/tool-use/advisor-tool#model-compatibility) section. Advisor thinking is never surfaced. Clients cannot send `redacted` blocks themselves; an event containing one is rejected with a 400 validation error.
13231323 

models/fable-5-2/overview Changed · +1 / -1 lines

from line 107
107107 </Card>
108108 
109109 <Card title="Preserved thinking" icon="brain" href="https://platform.claude.com/docs/en/build-with-claude/preserved-thinking">
110 Editing earlier turns invalidates thinking blocks, for every account.
110 Editing earlier turns invalidates thinking blocks.
111111 </Card>
112112 
113113 <Card title="Adaptive thinking" icon="brain" href="https://platform.claude.com/docs/en/build-with-claude/thinking">
Feedback