{"version":"2.1.311","anchor":"ruby-f-flag-allowed-in-read-only-flag-check","canonical_anchor":"ruby-f-flag-allowed-in-read-only-flag-check","heading":"Ruby commands with -F can now count as safe without a prompt","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/ruby-f-flag-allowed-in-read-only-flag-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Ruby commands with `-F` can now count as safe without a prompt\n\nClaude Code's list of safe `ruby` flags now accepts any argument beginning with `-F`\n\n**What**\n\nClaude Code checks the flags on some commands to decide whether they are safe enough to run without asking you. For `ruby`, that check now also accepts flags that start with `-F`. Anything after `-F` is accepted, so any argument beginning with `-F` passes.\n\n**Why**\n\nThe list of what counts as safe is looser for `ruby`, so some Ruby commands may now run without a permission prompt that used to appear.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}