{"version":"2.1.280","anchor":"attached-machine-tool-guidance-now-supports-powershell-not","canonical_anchor":"attached-machine-tool-guidance-now-supports-powershell-not","heading":"Attached-machine tool guidance now supports PowerShell, not just Bash","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/attached-machine-tool-guidance-now-supports-powershell-not","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Attached-machine tool guidance now supports PowerShell, not just Bash\n\nGuidance shown for machines attached to a session now covers PowerShell, not just Bash\n\n**What**\n\nWhen another machine is attached to a Claude Code session, Claude Code shows internal guidance describing how to run commands remotely on it. This guidance now recognizes PowerShell (Microsoft's command-line shell, run as `pwsh`) as an option alongside Bash, and adjusts its wording depending on which shell or shells the attached machine actually supports. For PowerShell specifically, it points to commands like `Get-Content` (read a file), `Select-String` (search text), and `Set-Content` (write a file) as the equivalents of familiar Bash tools.\n\nSeparately, the guidance now also describes a 'coordinator' framing for cases where the session can spawn Task workers (sub-agents that handle pieces of a job).\n\n**Why**\n\nThis makes remote execution guidance accurate for Windows machines running PowerShell, rather than assuming Bash is always available on an attached machine.\n\n- Area: Remote Control\n- Names: `pwsh`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}