Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneesstack72

Relationships

#2831 Telemetry opt-out scope: one user-level setting that disables telemetry everywhere

Opened by keeb · 9/30/2026· Shipped 9/30/2026

Split out of swamp-club#2817 (verified by that issue's audit):

  • .swamp.yaml telemetryDisabled is honoured inside a repo but not for commands run outside it.
  • The user-level telemetry.yaml disabled setting is honoured outside repos but not inside them.
  • A repo-dir that does not resolve, and any command run outside the repo, fall back to the public default endpoint even when the repo's .swamp.yaml sets telemetryEndpoint or telemetryDisabled.

Proposal: a user-level opt-out wins everywhere; consider honouring DO_NOT_TRACK; document a supported local-only mode (for example telemetryEndpoint none: spool locally, never send). Document every opt-out and its scope (see swamp-club#1597).

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 8 MOREREVIEW+ 10 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

9/30/2026, 10:59:51 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack729/30/2026, 9:33:22 PM

Sign in to post a ripple.