{"version":"2.1.232","anchor":"a-vetoed-sdk-reattach-no-longer-overwrites-the-stored-sessio","canonical_anchor":"a-vetoed-sdk-reattach-no-longer-overwrites-the-stored-sessio","heading":"A vetoed SDK reattach no longer overwrites the stored session","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/a-vetoed-sdk-reattach-no-longer-overwrites-the-stored-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### A vetoed SDK reattach no longer overwrites the stored session\n\nA rejected SDK reattach no longer overwrites your existing session transcript.\n\n**What**\n\nWhen an SDK session tries to reattach and the attempt is rejected because the owner identity does not match, Claude Code now skips persisting and leaves the existing transcript record intact.\n\n**Details**\n\n- Logged as `[bridge:sdk] Reattach was vetoed on owner identity`. The same veto already applied to interactive sessions; this extends it to the SDK path.\n\n**Evidence**\n\n`[bridge:sdk] Reattach was vetoed on owner identity`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}