{"version":"2.1.208","anchor":"monitor-tool-description-adapts-to-interactive-vs-non-intera","canonical_anchor":"monitor-tool-description-adapts-to-interactive-vs-non-intera","heading":"Monitor tool description adapts to interactive vs non-interactive context","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208\/e\/monitor-tool-description-adapts-to-interactive-vs-non-intera","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208","markdown":"### Monitor tool description adapts to interactive vs non-interactive context\n\n**What**\n\nThe Monitor tool's guidance text now varies based on whether the session is interactive. In interactive sessions (where the user is present at a terminal), Claude is now told to use a foreground Bash `until` loop for single-notification \"tell me when ready\" cases. In non-interactive\/background sessions, the previous `run_in_background` recommendation is kept.\n\n**Details**\n\n- For single-notification use cases in interactive sessions: \"run the command in the foreground with Bash, exiting when the condition is true\"\n- For single-notification use cases in non-interactive sessions: \"use Bash with `run_in_background`\"\n- The \"don't use unbounded command for a single notification\" warning likewise adapts its phrasing to the context\n\n**Evidence**\n\nMonitor tool description function (search for `\"run the command in the **foreground with Bash**\"`)"}