{"version":"2.1.304","anchor":"monitor-guidance-text-for-sessions-where-monitors-may-stop-a","canonical_anchor":"monitor-guidance-text-for-sessions-where-monitors-may-stop-a","heading":"New guidance for Claude when a monitor may stop after it replies","tier":"internal","area":"Monitor Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/monitor-guidance-text-for-sessions-where-monitors-may-stop-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### New guidance for Claude when a monitor may stop after it replies\n\nNew instructions tell Claude that in some sessions a monitor only works while Claude is busy, so it should wait directly or tell you what to check\n\n**Unclear.** Which sessions get these instructions is not known.\n\n**What**\n\nClaude Code has new instructions for the model for sessions where a monitor can only be relied on while Claude is working. They tell Claude to:\n\n- Use a command that runs while it waits, when it needs to wait for one thing\n\n- Otherwise tell you what to check and when\n\n**Why**\n\nThis changes how Claude handles waiting on monitors. In these sessions it may hand the follow-up to you instead of promising to keep watching.\n\n- Area: Monitor Tool\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}