{"version":"2.1.271","anchor":"repl-bridge-account-reattach-flow-internal-refactor-with-a","canonical_anchor":"repl-bridge-account-reattach-flow-internal-refactor-with-a","heading":"REPL bridge account-reattach flow: internal refactor with a widened inbound-message callback","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/repl-bridge-account-reattach-flow-internal-refactor-with-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### REPL bridge account-reattach flow: internal refactor with a widened inbound-message callback\n\nREPL bridge reattach logic renamed internally, and its inbound-message callback now takes two arguments\n\n**Unclear.** What the second argument to `onInboundMessage` carries or is used for is not stated.\n\n**What**\n\nThe logic in Claude Code's REPL bridge that handles automatically reattaching an account after an identity mismatch (around ownership of a stashed session) was heavily renamed internally. Its `onInboundMessage` callback, which handles incoming messages, now receives two arguments instead of one.\n\n**Why**\n\nThis is mostly internal cleanup, but the widened callback signature means the reattach flow now has access to more information when handling an inbound message.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}