{"version":"2.1.275","anchor":"background-monitor-tool-description-clarifies-cwd-with-pro","canonical_anchor":"background-monitor-tool-description-clarifies-cwd-with-pro","heading":"Background monitor tool description clarifies cwd with --project-config-root","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/background-monitor-tool-description-clarifies-cwd-with-pro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Background monitor tool description clarifies cwd with --project-config-root\n\nBackground monitor tool docs now note that --project-config-root changes the working directory it reports\n\n**What**\n\nThe background-monitor tool's built-in description now explains that when a host application sets `--project-config-root`, that path becomes the effective working directory (the folder a command is considered to run in) for the session, instead of just saying the command runs in the session's working directory.\n\n**Why**\n\nThis is a documentation clarification for the tool itself, so anything reading that description (including Claude) understands where commands are actually running when a host has overridden the project root.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}