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

Claude Code v2.1.265 ·

Resuming a session can reuse a precomputed compaction summary instead of recompacting

Session resume can now skip recomputing a conversation summary by reusing one precomputed ahead of time (feature-gated)

Group of 4 You'll notice No documentation found Internal Changes
JSON All of v2.1.265
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.265,
ImprovementsSection of the release

Unclear The finding doesn't say when or how a precomputed summary gets produced, or what user-visible effect it has.

What

  • A new path lets the agent loop reuse a previously precomputed compaction summary, built ahead of time and cached by session id, model, and boundary, instead of running compaction fresh.
  • The cached summary is validated before use: its age, model match, and token growth are checked, with rejection reasons including session_mismatch, model_mismatch, bad_timestamp, too_old, grew_too_much, shrank_too_much, and preserve_uuid_missing. A successful reuse emits tengu_precomputed_compact_rehydrated.
  • The session-resume warning dialog now shows a "Resume from summary (instant, recommended)" label instead of the usual "Resume from summary (recommended)" when a precomputed summary is available (hasPrecomputedSummary).
  • The resume flow, gated by tengu_gleaming_fair_reuse (extending tengu_gleaming_fair), can skip recomputation entirely, or detect that a precomputed summary has gone stale.

Why Recomputing a full conversation summary on every resume is slow; reusing a precomputed one when it's still valid should make resuming a session noticeably faster. The feature is currently gated off.

Read from
Names in the bundlehasPrecomputedSummary
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 doesn't say when or how a precomputed summary gets produced, or what user-visible effect it has.

See this entry in the whole of v2.1.265 →

Feedback