[FEATURE] Claude Desktop (Windows): document whether crash minidumps are uploaded (Crashpad minidumps on Windows include the process environment) and allow opting out on personal plans

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

On Windows, Crashpad always copies the crashed process's environment block into the minidump (https://github.com/chromium/crashpad/blob/ce308a86daa85e65df219ff5fb385095b0a1c467/snapshot/win/process_snapshot_win.cc#L439-L442). Judging from the Crashpad source, the dumps Claude Desktop writes on Windows should therefore contain anything a user keeps in User environment variables, such as API keys and tokens. I have not examined a Claude Desktop dump itself.

What I could confirm:

• The Windows MSIX package, version 2.9939.2.0, bundles @sentry/electron. In its main process, the default SentryMinidump integration "captures minidumps and sends them ... using a custom uploader" (https://docs.sentry.io/platforms/javascript/guides/electron/configuration/integrations/).
• The telemetry page for third-party deployments describes crash reports as "diagnostic metadata (app version, OS, error type, redacted stack frames)" sent to *.sentry.io, and does not mention minidumps. The only ways to turn this off that I found are for managed third-party deployments: the disableEssentialTelemetry key, or a switch in the Enterprise Admin Console (same page: https://claude.com/docs/third-party/claude-desktop/telemetry).
• #89525 reports that the previous crash report is deleted at the next app start while Crashpad's own upload flag stays off. Its reporter concluded that nothing was sent (as of the report in 2026-08; the issue was closed as completed on 2026-09-15).

What I infer but have not verified: that the app uploads the .dmp to Sentry at the next start. As I understand SentryMinidump, Crashpad's own upload is left off and the SDK sends the dump itself and then deletes it. If so, that would explain both observations in #89525: the upload flag being off and the dump disappearing. I have not seen what reaches Sentry.

Proposed Solution

1. Document whether Claude Desktop uploads minidumps, that on Windows they contain the environment variables, where they go, and how long they are kept.
2. Provide a setting that stops crash and minidump upload on personal (Free/Pro/Max) installs, not only through managed configuration.

Alternative Solutions

Exclude the environment block, or strip variables with secret-like names, before upload; or make minidump attachments opt-in.

Until then, users can keep long-lived secrets out of User environment variables and inject them only into the process that needs them.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

For comparison, a user report on OpenAI's Codex desktop app (also Electron with Sentry) shows the Sentry scope tag minidumpAttachmentUploadEnabled: false (openai/codex#46808). The Claude Code CLI does not appear to be affected: its documented error reports are messages and stack traces with known secret patterns redacted (https://code.claude.com/docs/en/data-usage).