tengu_session_stable_address

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.267, including the newest one read.

Releases whose published page names tengu_session_stable_address.

1. v2.1.267 9 Sep 2026
   Session ID derivation can now use a stable address scheme, behind tengu_session_stable_address

   A new stable-address scheme for session IDs is gated behind tengu_session_stable_address

   gate cited by this entry, found in this entry's text, named in this entry

2. v2.1.267 9 Sep 2026
   Own-endpoint-shadowed detection for /list-agents, gated by tengu_session_stable_address

   /list-agents can now detect when another process is already using this session's own address

   gate cited by this entry, found in this entry's text

3. v2.1.267 9 Sep 2026
   Session pin/rename detection: sending to a renamed session no longer silently fails

   Sending a message to a session that was renamed now reports the rename instead of just failing

   gate cited by this entry

No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.

The earliest release whose published evidence quoted tengu_session_stable_address was v2.1.267, 9 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.