The jobs list says "open" for jobs already live in a terminal instead of "resume".
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.248: on
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The jobs list now knows which jobs are currently held open in a terminal, and the Enter action reads "open" instead of "resume" for those, so you are not offered to resume a session that is live elsewhere.
- The same held-in-terminal information is passed to the fleet layout alongside the existing job-id list, derived from a lookup of running sessions.
- The fleet peers tab this feeds remains behind a flag whose built-in fallback is off.
heldInTerminal, tengu_fleetview_peers
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Background job state and roster writes can route through the v5 storage backend
Both mention background
-
v2.1.223
Telemetry for transient background-job state read failures
Both mention background
-
v2.1.223
Roster orphan adoption reports itself
Both mention background