Follow Discord
Sweep 09 Oct 2026 · 17:27Z Build v2.1.296 517 read Stable v2.1.287 Latest v2.1.296 Next v2.1.296 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.296 ·

Remote sessions gain a still-here check for silent streams

Remote sessions can send still-here pings and probe a stream that has gone quiet for about 8 seconds, behind tengu_violin_pernambuco

Group of 3 Nothing to try yet In Development
JSON All of v2.1.296
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SessionsArea: what it touches
In DevelopmentKind: in v2.1.296,
In DevelopmentSection of the release

What

New code helps remote and cloud sessions tell a quiet connection from a dead one:

  • A silence watcher probes the session after about 8 seconds without traffic (silentBeforeProbeMs: 8000) and can give up on the stream after repeated missed probes.
  • The session client now fires an onStreamSilent callback when its liveness timer runs out.
  • The remote-tools announcer gains a sayStillHere method that posts a rate-limited announce carrying the capability says_still_here. A failed post is handled separately.
  • The receiving side accepts a still-here ping only when the host lists that capability, and only from the client that holds the machine. Otherwise it answers invalid_announce: only the client that holds a machine can say it is still here. Accepted pings are noted in the machine registry.
  • The watcher runs only when the host advertises says_still_here, and the announce handling also depends on stillHereOn().
  • New still-here constants and a still-here notice are added to the remote-control event list.

The watcher is tied to the tengu_violin_pernambuco flag. The flag server returned off for this site's account and for an anonymous baseline, but no reading has been taken under this release.

Why

If enabled, a remote session whose stream silently stops could be detected and recovered instead of hanging. One finding describes it as machinery with no direct user effect.

Read from
Feature flag
tengu_violin_pernambuco Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.296: off

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.296. 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 on for tengu_violin_pernambuco, 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 off for tengu_violin_pernambuco, 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 on for tengu_violin_pernambuco, 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 off for tengu_violin_pernambuco, 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 on for tengu_violin_pernambuco, 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 →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_violin_pernambuco

See this entry in the whole of v2.1.296 →

Feedback