Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.117 ·

Session Resume Notification [Gradual Rollout]

Entry
JSON All of v2.1.117
EntryKind: in v2.1.117,
Bug FixesSection of the release
What

A notification system that would alert users when resuming a session after a period of inactivity.

Status

Feature-flagged behind tengu_gleaming_fair (defaults to !1 / false).

Details
  • Evaluates elapsed time since last activity to determine if a resume notification should appear
  • Also checks the CLAUDE_CODE_RESUME_SESSION environment variable
  • Infrastructure exists but the flag gates activation
Evidence

Feature gate (search for "tengu_gleaming_fair") — $s7 resume notification evaluator

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_gleaming_fair Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.117: no gate table built for this version

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.117. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_gleaming_fair, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_gleaming_fair, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.117 →

Feedback