Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Ruby's -F option no longer read as taking a value when checking permissions

When Claude Code checks a ruby command for permission, it no longer treats -F as an option that takes a value

You'll notice Bug Fixes
JSON All of v2.1.311
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Bash SafetyArea: what it touches
Bug FixesKind: in v2.1.311,
Bug FixesSection of the release

Unclear It is not stated whether this makes ruby commands using -F more or less likely to need your approval.

What

Before 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).

For 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.

Why

This changes how ruby commands that use -F are read when Claude Code decides whether to ask before running them.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not stated whether this makes `ruby` commands using `-F` more or less likely to need your approval.

See this entry in the whole of v2.1.311 →

Feedback