Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Context-usage reports carry a compact-boundary id, stripped for some sessions

Context-usage reports can now name the compaction point they were measured after, except in some sessions

Entry
JSON All of v2.1.281
EntryKind: in v2.1.281,
ChangesSection of the release
What

Claude Code reports how full the context window is, meaning how much of the model's working memory the conversation uses. That report can now include after_boundary, the ID of the compact-boundary message at the start of the conversation. A compact boundary marks where an earlier part of the conversation was replaced by a summary.

  • An estimate taken after a boundary is skipped until a measured value has been written
  • The context meter uses an estimate only if it belongs to the same boundary as the measured value, and keeps the measured value's other fields
  • after_boundary is left out for sessions with noHistoryBackfill or foreign set
Why

The context meter is less likely to mix a figure from before a compaction with one from after it.

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 doubtThe finding does not say what a `foreign` or `noHistoryBackfill` session is from a user's point of view.

See this entry in the whole of v2.1.281 →

Feedback