Fleet view refuses to open a session another terminal already has running.
What's wrong with this entry?
Opening a job from the fleet view now checks whether another terminal already holds that session and shows "Can't open — this session is running in another terminal" instead of attaching. No flag guards it.
- The roster of live sessions is consulted before attaching; a holder means the open is refused outright rather than respawning.
- The same message was already used by the peer-backend path; it now covers the local path too.
Can't open \u2014 this session is running in another terminal
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.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task