{"version":"2.1.294","anchor":"the-monitor-tool-description-was-rewritten","canonical_anchor":"the-monitor-tool-description-was-rewritten","heading":"Claude's instructions for the Monitor tool were rewritten","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.294\/e\/the-monitor-tool-description-was-rewritten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.294","markdown":"### Claude's instructions for the Monitor tool were rewritten\n\nThe instructions Claude gets for the Monitor tool were rewritten, and now say the script runs in the same shell environment as Bash\n\n**What**\n\nThe Monitor tool watches the output of a command. The written instructions Claude receives for it have been rewritten. The new text includes the line \"The script runs in the same shell environment as Bash.\" The rewrite covers the guidance on watching for every occurrence of something indefinitely. That guidance used to point to never-ending commands such as `tail -f`, `inotifywait -m` or `while true`.\n\nThis change was seen under certain account settings. Some other model configurations got a different edit to the same instructions, so the wording you get may depend on the model in use.\n\n**Why**\n\nClaude follows these instructions, so a rewrite can change how it sets up and runs Monitor. What the new wording changes in practice has not been measured.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}