DeepSeek Harness Telemetry & Privacy
Official CLI behavior says session telemetry is local and disabled by default. Explicit FULL or FEEDBACK_ONLY modes can export message text, tool arguments/results and workspace paths, while DSH_TELEMETRY_DISABLED is the hard opt-out. This page separates verified behavior from community reports and marks the release-candidate context so you can act without mistaking an observation for a permanent guarantee.
What is verified now
Official CLI behavior says session telemetry is local and disabled by default. Explicit FULL or FEEDBACK_ONLY modes can export message text, tool arguments/results and workspace paths, while DSH_TELEMETRY_DISABLED is the hard opt-out.
Evidence basis: Official CLI/deployment reference. The status was checked on 14 August 2026; re-check the linked source after any dsh release.
Safe workflow
Use the smallest reversible workflow first. Do not add community plugins or paste credentials while validating the base behavior.
- Keep telemetry disabled unless there is an explicit operational reason.
- Inspect payload scope and collector URL before enabling export.
- Never include secrets or unnecessary workspace content in feedback.
Verify before moving on
A successful result should be observable: a version string, reachable local URL, valid provider response, loaded configuration, or disappearance of the exact error. If the result differs, stop and capture sanitized evidence rather than stacking unrelated fixes.
- Record the exact dsh, Node or Python version.
- State the operating system and installation method.
- Link the first-party source and include only sanitized logs.
First-party sources
Open the original source before acting on a changed version or unresolved community report.