ci: set DO_NOT_TRACK to keep CI out of the telemetry stream - #77
Open
sizeak wants to merge 1 commit into
Open
Conversation
claude-commander-core bakes a telemetry ingest credential into every build, and its `cfg!(test)` opt-out only suppresses core's own test runs — not ours as a downstream consumer. No CI job runs the Rust backend today (clippy only compiles, the .iwft layer simulates Tauri, tauri-action only builds), so nothing is emitted. This is a defensive guard: the day a job builds a CommanderService or launches the bundle, DO_NOT_TRACK keeps those runs out of the live usage stream. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
claude-commander-corebakes a telemetry ingest credential into every build (BAKED_CREDENTIAL_RAW), and itscfg!(test)opt-out only suppresses core's own test runs — it does not extend to us as a downstream consumer. So CC-GUI builds ship with live telemetry armed; the only thing keeping CI quiet today is that no job actually runs the Rust backend.I audited this against the live usage stream: all
cc-guitelemetry comes from real macOS developer machines (stable install_ids over days, genuine interactive features), and there are zero linux/x86_64 events — i.e. the ubuntu CI runners emit nothing. CI is not leaking today.What this changes
Adds a workflow-level
env: DO_NOT_TRACK: "1"toci.yml,tests.yml, andrelease.ymlas a defensive guard. It's a no-op right now, but the day someone adds acargo testjob that constructs aCommanderService, or an e2e job that launches the packaged app, this keeps those runs out of the livecommander_usagestream without anyone having to remember to do it.No behavioural change to the app or its builds.
🤖 Generated with Claude Code