session-observability changedmanaged-agents/session-observability
Nearest release: v2.1.300, published 2 hours after 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+2added
Lines−2removed
From line
10
where the diff opens
First seen
8 Oct 2026
this site's first read of the page
Recorded edits7to this page, all time
The whole hunk
from line 10, old and new numbered
/
from line 10
1010 betaHeader: managed-agents-2026-04-01
1111---
1212
13Use the session viewer in the Claude Console to inspect what an agent did in a session, without writing any code. Use the session's `usage` (java, php; csharp, go: `Usage`) totals to see what that work consumed.
13Use the session viewer in the Claude Console to inspect what an agent did in a session, without writing any code. Use the session's `usage` (csharp, go: `Usage`) totals to see what that work consumed.
1414
1515## Inspect a session in the Console
1616
from line 83
8383
8484### Read usage from the stream
8585
86You don't have to poll the session to observe these totals. The `session.usage` event carries the same cumulative snapshot on the session stream and in the event history. The snapshot holds the `usage` (java, php; csharp, go: `Usage`) object plus the session's `budget` (java, php; csharp, go: `Budget`), which is `null` when the session has none.
86You don't have to poll the session to observe these totals. The `session.usage` event carries the same cumulative snapshot on the session stream and in the event history. The snapshot holds the `usage` (csharp, go: `Usage`) object, plus the session's `budget` (csharp, go: `Budget`) if the session has one.
8787
8888The event is emitted on idle transitions rather than on a timer:
8989
No line in this hunk matches that.