{"version":"2.1.311","anchor":"ruby-f-no-longer-treated-as-a-value-taking-flag","canonical_anchor":"ruby-f-no-longer-treated-as-a-value-taking-flag","heading":"Ruby's -F option no longer read as taking a value when checking permissions","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/ruby-f-no-longer-treated-as-a-value-taking-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Ruby's -F option no longer read as taking a value when checking permissions\n\nWhen Claude Code checks a `ruby` command for permission, it no longer treats `-F` as an option that takes a value\n\n**Unclear.** It is not stated whether this makes `ruby` commands using `-F` more or less likely to need your approval.\n\n**What**\n\nBefore Claude Code runs a shell command, it reads the command to decide whether it needs to ask your permission. To do that it keeps a table of options for each language interpreter, recording which options take a value (the word that follows them).\n\nFor `ruby`, `-F` has been taken out of the list of options that take a value. The options still on that list are `-e`, `-r`, `--require`, `-I`, `-C` and `-E`.\n\n**Why**\n\nThis changes how `ruby` commands that use `-F` are read when Claude Code decides whether to ask before running them.\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"}