Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

Tools that run code now carry an enablesCodeExecution marker

Bash, REPL and cloud trigger tools now carry a marker saying they execute code.

Under the hood Internal Changes
JSON All of v2.1.248
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.248,
Internal ChangesSection of the release
What

Tool descriptors gained a new capability flag that marks a tool as one that executes code, so other logic can key permission or classification decisions off the descriptor instead of matching tool names. The Bash tool, the REPL tool and the cloud trigger tool all set it, and downstream filtering uses it to pick out the code-executing set.

Details
  • The flag is enablesCodeExecution, set unconditionally to true on each of the three tool definitions, with no setting, environment variable or feature gate to turn it off.
  • Tools without the marker are treated as not executing code, which is the behaviour everything had before this build.
  • Nothing user-visible changes here: the marker is only read by internal filtering and classification, and no permission prompt, message or default is altered by it in this release.
Evidence

enablesCodeExecution: !0,, enablesCodeExecution: !0

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.248 →

Feedback