{"version":"2.1.317","anchor":"safe-command-check-for-sshrsyncgcloud-hosts","canonical_anchor":"safe-command-check-for-sshrsyncgcloud-hosts","heading":"Stricter safety check for ssh, rsync and similar remote commands","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/safe-command-check-for-sshrsyncgcloud-hosts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Stricter safety check for ssh, rsync and similar remote commands\n\nClaude Code now refuses to auto-approve rsync, ssh, scp, sftp and gcloud compute ssh when a value could slip text into a shell command\n\n**Unclear.** Whether this check is switched on depends on remote settings whose state is unknown.\n\n**What**\n\nSome shell commands can be approved automatically, without asking you. Claude Code now refuses to do that for these commands when a value in them could make ssh paste text into a shell command:\n\n- `rsync`\n\n- `ssh`\n\n- `scp` and `sftp`\n\n- `gcloud compute ssh`\n\nThe values covered include `RSYNC_RSH`, jump hosts, paths given with `-F`, user names and option names. The refusal says the command \"cannot be shown not to be git\" and explains how to get it through.\n\n**Why**\n\nRemote-shell commands are classified more strictly, so you may be asked to approve some of them that used to pass on their own.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}