{"version":"2.1.248","anchor":"local-file-paths-and-error-text-withheld-from-remote-session","canonical_anchor":"local-file-paths-and-error-text-withheld-from-remote-session","heading":"Local file paths and error text withheld from remote sessions","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/local-file-paths-and-error-text-withheld-from-remote-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Local file paths and error text withheld from remote sessions\n\n\/heapdump and restart no longer send local paths or error text to remote sessions.\n\n**What**\n\nThe `\/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.\n\n**Details**\n\n- Selected by whether the session's transport keeps outbound frames or has a live remote bridge, not by any setting\n- Heap dump failures likewise report only that detail was withheld\n- Paths still appear in the local log line beginning \"heapdump written:\"\n\n**Evidence**\n\n`Failed to create heap dump (detail withheld on this connection)`, `Couldn't restart Claude Code (detail withheld on this connection).`\n\n- Area: Sessions\n- Names: `\/heapdump`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}