telemetry

name	telemetry
description	Manage your own telemetry settings — check status, opt in/out, view or clear the buffered events. Use for /telemetry, 'turn off telemetry', or 'what data do you collect'.

Manage telemetry settings. Shows status by default.

When to invoke

User says: "/telemetry", "telemetry status", "turn off telemetry", "disable telemetry", "what data do you collect", "show my telemetry events", "clear telemetry buffer" Not this: viewing telemetry across all registered orgs (internal, admin only) → /telemetry-admin

Arguments

• status (default) — show whether telemetry is enabled, buffer size, opt-out method
• off or disable — disable telemetry (sets telemetry: false in state file)
• on or enable — re-enable telemetry
• show [N] — show last N buffered events (default 10)
• clear — delete local telemetry buffer

What to do

Parse the argument (default to status if none given).

status (default)

bash bin/telemetry.sh status

Show the output to the user.

off / disable

bash bin/telemetry.sh disable

Confirm: "Telemetry disabled. No events will be collected until you run /telemetry on."

on / enable

bash bin/telemetry.sh enable

Confirm: "Telemetry re-enabled."

show [N]

bash bin/telemetry.sh show ${N:-10}

Show the output. If empty, say "No buffered events."

clear

bash bin/telemetry.sh clear

Confirm: "Local telemetry buffer cleared."

What is collected

Only: command names, timestamps, session durations, error codes, branch names, query latencies.

What is NEVER collected

File paths, file contents, code, env var values, conversation content, command arguments that might contain user content.

Opt-out methods

1. /telemetry off — persistent opt-out via state file
2. EGREGORE_NO_TELEMETRY=1 in .env — env var opt-out
3. DO_NOT_TRACK=1 — standard env var opt-out