{"version":"2.1.239","anchor":"session-to-session-messages-refuse-to-send-to-a-record-imper","canonical_anchor":"session-to-session-messages-refuse-to-send-to-a-record-imper","heading":"Session-to-session messages refuse to send to a record impersonating the current session","tier":"notice","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/session-to-session-messages-refuse-to-send-to-a-record-imper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Session-to-session messages refuse to send to a record impersonating the current session\n\nMessages to another Claude session are refused if a local record impersonates your own session.\n\n**What**\n\nWhen sending a message to another Claude session, Claude Code now checks whether a session record on the machine claims the same identifying token this session advertises for itself. If so, the send is refused and the model is told the record is suspicious and to ask you.\n\n**Details**\n\n- Applies unconditionally on that send path.\n- The refusal text shown to the model is \"A record impersonating this session is suspicious: ask the user.\"\n\n**Evidence**\n\n`A record impersonating this session is suspicious: ask the user.`\n\n- Area: Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}