{"version":"2.1.311","anchor":"idle-observation-fence-for-peer-activity-messages","canonical_anchor":"idle-observation-fence-for-peer-activity-messages","heading":"Activity notes from other sessions can be marked as not instructions","tier":"use","area":"Peer Messages","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/idle-observation-fence-for-peer-activity-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Activity notes from other sessions can be marked as not instructions\n\nWith `idleObservationFence` on, activity notes from peer sessions are fenced off as content rather than instructions\n\n**Unclear.** How `idleObservationFence` is set to true is not stated.\n\n**What**\n\nSome messages come from a peer, meaning another session, and report activity it observed. When the configuration value `idleObservationFence` is true, these messages are wrapped and marked as content that is not instructions. When it is false, which is the default, the record of where the message came from is cleared instead.\n\nA new notice also reads: Docs of this project were read for this chat.\n\n**Why**\n\nFencing the text off makes it harder for words in a peer's message to be treated by Claude as commands.\n\n- Area: Peer Messages\n- Names: `idleObservationFence`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}