{"version":"2.1.232","anchor":"remote-sessions-can-be-told-that-activity-was-observed-in-th","canonical_anchor":"remote-sessions-can-be-told-that-activity-was-observed-in-th","heading":"Remote sessions can be told that activity was observed in the bound conversation","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-sessions-can-be-told-that-activity-was-observed-in-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote sessions can be told that activity was observed in the bound conversation\n\nRemote sessions can be told activity happened in a linked conversation, flagged as not your instruction and never an approval.\n\n**What**\n\nMessages arriving over the remote bridge may now carry an activity observation, for things like an edit or a reaction on the linked conversation. The message is wrapped with a preamble saying activity was observed, plus a guard telling the model this was not typed by you, is never an approval, and must not be re-processed as a fresh request.\n\n**Details**\n\n- Only applies when the inbound message comes from a recognised origin; previously the only extra inbound field handled was a receiver grouping id.\n- The guard exists specifically so an observed edit or reaction cannot be read as consent for a pending action.\n\n**Evidence**\n\n`Activity was observed in the bound conversation`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5"}