Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SessionsArea: what it touches
In DevelopmentKind: in v2.1.267,
In DevelopmentSection of the release
Unclear Nothing has been read yet about whether the tengu_session_stable_address flag that controls this is on or off by default.
What
A new check detects when another live process on the same machine is already listening on the socket that represents this session's "stable address" (its identity), even though it's a different process. When that happens, the /list-agents (also /peers) output changes which address token it displays for this session's own entry, to reflect that its usual address is shadowed by the other process.
Why
Without this, a session could display an address for itself that's actually claimed by a different, unrelated process, making it confusing or unreliable for another session to message it correctly.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up /list-agents, on Tools reference.| `ListAgents` | Lists the agents Claude can message with `SendMessage`: subagents in the session, [agent team](/docs/en/agent-teams) teammates, your other local Claude Code sessions, and, while this session is connected to [Remote Control…tools-referencesee the edit
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 doubtNothing has been read yet about whether the `tengu_session_stable_address` flag that controls this is on or off by default.
Anthropic's documentation agreesAnthropic's documentation has since written up /list-agents, on Tools reference.
The name it cites is new in this buildNew in this build: tengu_session_stable_address
