v2.7.5

Shell tools that run their commands on another machine, such as a plugin tool backed by adb shell or ssh, can now be declared so their commands are analyzed instead of going unchecked.

Added

• Added --no-cwd-arg to cc-safety-net rule tool add, and the equivalent { "name": "phone_shell", "cwd": false } form in command_tools, for declaring a shell tool whose working directory is not on this machine. Commands from such a tool are analyzed like a built-in shell command, no working-directory argument is read, and a relative path is judged against the session directory. (#331, #330)
• Added an error when cc-safety-net rule tool add is given both --cwd-arg and --no-cwd-arg.

Changed

• Changed the OpenCode and Cursor adapters to ignore the workdir and working_directory arguments for a tool declared with cwd: false, so a remote working directory that does not exist locally no longer makes the call unusable.
• Changed the DeepSeek Harness notice about an undeclared shell tool to recommend rule tool add <name> --no-cwd-arg when the tool runs its commands on a remote host or the location cannot be determined, instead of advising against declaring it at all.
• Changed cc-safety-net rule tool list to report Cwd argument: none for a tool declared with cwd: false.
• Changed the published JSON Schema (assets/cc-safety-net.schema.json) to accept false for a command_tools entry's cwd, and the rule.json validation message for an invalid cwd now states that false is allowed.