{"version":"2.1.248","anchor":"fleet-view-refuses-to-open-a-session-another-terminal-is-run","canonical_anchor":"fleet-view-refuses-to-open-a-session-another-terminal-is-run","heading":"Fleet view refuses to open a session another terminal is running","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/fleet-view-refuses-to-open-a-session-another-terminal-is-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Fleet view refuses to open a session another terminal is running\n\nFleet view refuses to open a session another terminal already has running.\n\n**What**\n\nOpening a job from the fleet view now checks whether another terminal already holds that session and shows \"Can't open \u2014 this session is running in another terminal\" instead of attaching. No flag guards it.\n\n**Details**\n\n- The roster of live sessions is consulted before attaching; a holder means the open is refused outright rather than respawning.\n- The same message was already used by the peer-backend path; it now covers the local path too.\n\n**Evidence**\n\n`Can't open \\u2014 this session is running in another terminal`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}