{"version":"2.1.267","anchor":"conversation-replace-all-now-marks-session-as-remote-origina","canonical_anchor":"conversation-replace-all-now-marks-session-as-remote-origina","heading":"Conversation replace-all now marks session as remote-originated","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/conversation-replace-all-now-marks-session-as-remote-origina","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Conversation replace-all now marks session as remote-originated\n\nReplacing all messages in a conversation now marks the session as remote-originated and transforms messages before storing them\n\n**Unclear.** The finding doesn't say what the Coe() transform does to the messages, so its exact effect on stored data is unclear.\n\n**What**\n\nWhen Claude Code replaces the entire set of messages in a conversation, it now marks the conversation as remote-originated (via `markConversationRemote`) and runs the messages through an additional transform step before saving them, rather than storing the raw list as before.\n\n**Why**\n\nThis helps Claude Code correctly track which conversations came from a remote source (such as a synced or delegated session), which matters for features that behave differently depending on where a conversation originated.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}