Unclear The finding doesn't say how a machine becomes "attached" or what triggers this remote routing in practice.
What
- A new session-channel version of the PowerShell tool wraps the real PowerShell tool, removes the
run_in_backgroundoption from its schema, and adds a field for selecting which machine to run on. This version is only advertised when the session is serving tools to an attached machine and that condition is met (e.servedTools.has(It) && !av()); if invoked directly it throws an error explaining that PowerShell only runs on the attached machine. - The underlying PowerShell tool definition gains a
remoteExecutioncapability flag and asuppressesAllPermissionUpdatesmethod. - Its input validation now also blocks bare sleep/wait-style commands specifically when the remote call's constraints don't forbid running in the background, in addition to its previous checks.
Why
This lets Claude Code run PowerShell commands on a separate, attached Windows machine rather than only locally, while still guarding against commands (like bare sleeps) that could stall a remote session.
tengu_cobalt_ridge Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.280: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.280. It isn't a statement about your account. What a flag value here can and cannot tell you
The finding doesn't say how a machine becomes "attached" or what triggers this remote routing in practice.