Peer discovery in fleet view needs both tengu_fleetview_peers and cross-session messaging, both off by default.
The fleet view refresh folds in other concurrent interactive sessions found in the local process registry, so sessions started outside its own bookkeeping appear. Needs both the tengu_fleetview_peers gate (in-source fallback false) and the cross-session messaging gate.
- A registry entry qualifies if it is a different pid, has a session id, reports a peer protocol version at or above a minimum, and was seen within the last 24 hours.
- Synthesised entries are keyed off the other process's pid; a locally known newer name or intent wins over the registry copy.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_fleetview_peers Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.224: 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.224. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_fleetview_peers