{"version":"2.1.247","anchor":"attaching-to-a-session-on-a-different-claude-code-version-fa","canonical_anchor":"attaching-to-a-session-on-a-different-claude-code-version-fa","heading":"Attaching to a session on a different Claude Code version falls back to older key handling","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/attaching-to-a-session-on-a-different-claude-code-version-fa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Attaching to a session on a different Claude Code version falls back to older key handling\n\nAttaching to a session running a different build now falls back to older keyboard handling.\n\n**What**\n\nWhen you attach to a running session, the acknowledgement now includes the worker's Claude Code version. If it differs from your build, the client switches to a legacy keyboard mode instead of assuming both ends speak the current key sequences.\n\n**Details**\n\n- Runs on every attach; there is no flag.\n\n**Evidence**\n\n`legacyKitty`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}