/heapdump and restart no longer send local paths or error text to remote sessions.
What's wrong with this entry?
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.
- 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:"
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.