Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

Usage report timeout advice now suggests filtering by actor IDs

When a usage report times out, the error now suggests narrowing it with actor_ids[] (up to 100 a call) instead of rbac_group_ids[]

You'll notice Improvements
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release

Unclear It is not clear whether rbac_group_ids[] is still accepted as a filter.

What

When a usage report request takes too long and fails with a timeout, the error message suggests ways to make it smaller. It now suggests asking for only some actor_ids[], up to 100 a call, or leaving out time_bucket_width. Before, it suggested asking for only some rbac_group_ids[].

Why

The advice suggests the report now filters by actor (the person or key that did the work) rather than by permission group, so that is the filter to reach for when a report is too big.

Read from
Names in the bundletime_bucket_width
What the documentation says
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether `rbac_group_ids[]` is still accepted as a filter.

See this entry in the whole of v2.1.318 →

Feedback