{"version":"2.1.248","anchor":"resume-conflicts-say-when-the-session-is-open-interactively","canonical_anchor":"resume-conflicts-say-when-the-session-is-open-interactively","heading":"Resume conflicts say when the session is open interactively","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/resume-conflicts-say-when-the-session-is-open-interactively","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Resume conflicts say when the session is open interactively\n\nResume now tells you when the conversation is already open in another running session.\n\n**What**\n\nIf you try to resume a conversation that another process already holds, Claude Code now checks every holder rather than one, prefers an interactive one, and shows a message naming that case: the conversation is already open in another running Claude session, so use that one or close it. Failures also return an explicit `resume_session_live_elsewhere` code.\n\n**Details**\n\n- The conflict telemetry event gained a `holder_kind` field.\n- Non-interactive holders still get the generic message.\n\n**Evidence**\n\n`This conversation is already open in another running Claude session \\u2014 use that one, or close it and try again`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}