You'll notice
Background monitor tool docs now note that --project-config-root changes the working directory it reports
What
The 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.
Why
This 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.