Pine/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases 1 Wiki Activity

docs(agent-notes): frame telemetry default-off as public beta transition

Browse Source 
Problem now explains that DSH is entering public beta and default-off is
the appropriate stance for that phase — consistent with internal testing
having default-on for diagnostics. Update Consequences to match.
This commit is contained in:
Chinesezjc
2026-08-11 11:12:46 +08:00
parent e6eb44ed2a
commit cc455c4f5a
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/notes/implemented/feature/2026-08-10-telemetry-default-off.md
+2 -2
View File
@@ -6,7 +6,7 @@ English | [中文](2026-08-10-telemetry-default-off.zh.md)
## Problem
DeepSeek Harness has two outbound telemetry feeds. The session OTel backend could export complete session content, tool data, prompts, and workspace paths when its mode was omitted, while the dsh-sdk launcher feed reported by default. A fresh installation therefore permitted outbound reporting without a positive deployment choice.
DeepSeek Harness is entering its public beta phase. During internal testing, telemetry was enabled by default — the session OTel backend and the dsh-sdk launcher both reported without a positive deployment choice — to help diagnose reported issues. For public beta, outbound reporting must require an explicit opt-in from the deployment.
## Decision
@@ -28,4 +28,4 @@ The versioned Web welcome notice states that Session Log upload is off by defaul
## Consequences
Fresh profiles and projects make no telemetry network request. Internal deployments select one mode for both feeds: `FEEDBACK_ONLY` permits only feedback-triggered Session Log sharing, while `FULL` also enables launcher reporting. The existing hard opt-out remains effective, and uploading modes retain their endpoint validation, redaction responsibility, batching, and shutdown behavior.
All public beta profiles and projects make no telemetry network request by default — a break from the internal-testing default of reporting when configured. Internal deployments that still need reporting select one mode for both feeds: `FEEDBACK_ONLY` permits only feedback-triggered Session Log sharing, while `FULL` also enables launcher reporting. The existing hard opt-out remains effective, and uploading modes retain their endpoint validation, redaction responsibility, batching, and shutdown behavior.