Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Internal changes to tool execution: memory sampling and a waitForExitAfterKill option

Tool calls now sample memory through a sampler, and the command runner gains a waitForExitAfterKill option, plus small internal tweaks

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

What

Several internal changes to how Claude Code runs tools (the actions Claude takes, such as running a command or editing a file) and shell commands:

  • Memory use around each tool call is now taken from a sampler, with sample("before_call"), sample("after_call") and sample("after_throw"). Before, it called process.memoryUsage() and computed rss, heap and external memory changes. The usage reports for tool success and error use the sampler's fields. Success reports also get fields describing the shape of the tool's result.
  • The helper that runs processes has a new option, waitForExitAfterKill, which is off by default. The exec wrapper passes it through.
  • The updater for background jobs still in progress gains an includeSettled option.
  • The parser for artifact conflict records no longer rejects records for one extra condition.
  • The bridge and CCR heartbeat gates are unchanged apart from renamed internals.

Why

These are mostly internal. Memory is no longer measured directly on every tool call. waitForExitAfterKill may help avoid stray output after a command that was stopped for taking too long.

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 doubtThe finding does not say who sets `waitForExitAfterKill` or what it changes when a command is stopped.

See this entry in the whole of v2.1.281 →

Feedback