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")andsample("after_throw"). Before, it calledprocess.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
includeSettledoption. - 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say who sets `waitForExitAfterKill` or what it changes when a command is stopped.