What
The /heapdump command and the restart path no longer send on-disk paths or raw exception text to a session running over a remote or bridged connection. Heap dump locations are written to the local log instead, and a failed restart reports that the detail was withheld. Local sessions are unaffected.
Details
- Selected by whether the session's transport keeps outbound frames or has a live remote bridge, not by any setting
- Heap dump failures likewise report only that detail was withheld
- Paths still appear in the local log line beginning "heapdump written:"
Evidence
Failed to create heap dump (detail withheld on this connection), Couldn't restart Claude Code (detail withheld on this connection).
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/heapdump
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up /heapdump, on Claude Code changelog.
* Fixed `/heapdump` summary saying most memory is native when it is in the JS heap snapshotchangelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /heapdump, on Claude Code changelog.