Skip to content

telemetry.md

Latest commit

聽

History

History
100 lines (78 loc) 路 5.24 KB

telemetry.md

File metadata and controls

100 lines (78 loc) 路 5.24 KB
Raw

Telemetry controls

CLI opt-outs live in the Nix telemetry module. It renders shell exports and BB's variable list from one declaration.

flowchart TD
    A[Nix telemetry declaration] --> B[Shell exports]
    B --> C[.zshenv]
    A --> D[BB variable list]
    D --> E[telemetry-bb-sync]
    E --> F[BB agents and commands]
    A --> G[macOS login agent]
    G --> H[launchd environment]
Loading

Shells and BB

.zshenv loads ~/.config/telemetry/environment.sh for interactive and non-interactive zsh. Home Manager installs the rendered files during activation.

  1. Apply Nix configuration with drs on macOS or hms on Linux.
  2. Run telemetry-bb-sync to copy the declared variables into BB's global environment.
  3. Start fresh shells and provider sessions to check the effective variables.

The sync command updates declared names only. It does not delete other BB variables. Removed declarations need an explicit bb machine env unset NAME when retiring their BB overrides. BB project variables and provider contributions can override global values. Cached provider processes can retain their launch environment.

Targeted installations protect their Nix outputs with indirect garbage-collection roots under ~/.local/state/telemetry/nix-roots.

BB discovers the shell's PATH; its shell discovery does not copy other exports. Use bb machine env to manage agent variables. BB's own telemetry switch lives in its native settings.

The macOS login agent sets the declared variables in the user launchd environment. Existing applications retain their launch environment. Check environment-only desktop controls after relaunch; a shell export alone does not prove GUI coverage.

cspy removes DISABLE_TELEMETRY and DO_NOT_TRACK for its Claude process. It refreshes cached feature flags. Claude's native settings do not duplicate these opt-outs, so the explicit exception remains effective.

Grok CLI

Mise owns Grok Build and pins its release in config.toml. Its self-updater stays disabled. Grok's native configuration disables product telemetry, feedback, session-trace uploads, external OpenTelemetry exports, and workspace snapshots. The shell's DISABLE_ERROR_REPORTING=1 disables error uploads.

Run grok login to sign in with the SuperGrok account, then run grok. Authentication files, logs and session state stay untracked.

The opt-outs do not stop prompts and tool results reaching the inference service. The official configuration reference defines the native controls.

Desktop settings

Application Persistent control Verification
Zed Native settings disable metrics and diagnostics Inspect effective settings
VS Code Native settings disable telemetry Relaunch after changing settings
Firefox Profile preferences disable uploads, studies and automatic crash uploads Relaunch each profile
BB Native telemetryEnabled=false setting bb settings show --json
Chrome Native usage-reporting preference Inspect browser settings
Brave Nix activation disables analytics, usage-ping and crash reporting Three native preferences verified false
Discord Account-level improvement-data switch Inspect Data & Privacy
Android Studio Native Data Sharing consent Inspect application settings
T3 Code Launch environment variables Inspect the desktop server's environment after relaunch

The desktop Nix module links VS Code's native settings path to its tracked file. Its Firefox activation links existing profiles to the tracked user.js. An existing conflicting user.js stops activation rather than losing its preferences. New Firefox profiles receive the link on the next activation.

Brave activation merges three opt-outs into its existing Local State. It preserves other preferences and refuses to write while Brave runs. Firefox controls passed a disposable headless-profile check. VS Code runtime verification needs an installed editor. Discord and Android Studio remain manual checks.

Browser profiles and application databases stay untracked. Account settings need manual checks where applications expose no supported declarative control.

Sources

Amp and Droid opt-outs remain unverified. Droid's customer-exporter settings do not disable its vendor collector.