{"version":"2.1.311","anchor":"gcloud-compute-ssh-short-flags-before-flagged","canonical_anchor":"gcloud-compute-ssh-short-flags-before-flagged","heading":"Safety check flags short options before -- in gcloud compute ssh","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/gcloud-compute-ssh-short-flags-before-flagged","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Safety check flags short options before `--` in `gcloud compute ssh`\n\nClaude Code now flags a `gcloud compute ssh` command with a short option other than `-q` or `-h` placed before `--`\n\n**Unclear.** Whether a flagged command asks for permission or is blocked outright is not clear.\n\n**What**\n\nClaude Code checks shell commands before running them. It now flags a `gcloud compute ssh` command that has a short option, one like `-x`, other than `-q` or `-h` before any `--`. In that position gcloud accepts only its own options, and anything meant for ssh has to come after a literal `--`. Before, only options such as `--flags-file` were checked here.\n\n**Why**\n\nIt closes a way to slip ssh options through gcloud past the command safety check. If you write these commands yourself, put ssh options after `--`.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}