{"version":"2.1.311","anchor":"monitor-tool-prompt-stderr-wording-now-one-fixed-sentence","canonical_anchor":"monitor-tool-prompt-stderr-wording-now-one-fixed-sentence","heading":"Monitor tool now has one fixed sentence about error output","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/monitor-tool-prompt-stderr-wording-now-one-fixed-sentence","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Monitor tool now has one fixed sentence about error output\n\nThe Monitor tool's instructions now always say error output goes to the output file but does not trigger notifications\n\n**What**\n\nThe Monitor tool's instructions to Claude used to pick one of two sentences about stderr (the error output stream of a command) depending on a setting checked while running. They now always say: Stderr goes to the output file (readable via Read) but does not trigger notifications. The alternative wording is gone.\n\nThe stock description of the Monitor tool, captured under this release, is unchanged in size since v2.1.310.\n\n**Why**\n\nIn practice Claude is told one consistent thing: errors from a monitored command can be read from the output file, but they will not alert it on their own.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}