Manage local-first telemetry — status, inspect, export, opt in/out, clear, or explicitly share a disclosed dataset. Use for /telemetry, 'turn off telemetry', or 'what data do you collect'.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Manage telemetry settings. Shows status by default.
User says: "/telemetry", "telemetry status", "turn off telemetry", "disable telemetry", "what data do you collect", "inspect/export/share my telemetry events", "clear telemetry buffer"
Not this: viewing telemetry across all registered orgs (internal, admin only) → /telemetry-admin
status (default) — show whether telemetry is enabled, buffer size, opt-out methodoff or disable — disable telemetry (sets telemetry: false in state file)on or enable — re-enable telemetryinspect [N] or legacy show [N] — show last N buffered events (default 10)export <path> — validate and copy the local JSONL dataset; never uploadsshare — disclose the exact local dataset and prepare a short-lived confirmation tokenshare --confirm <token> — send only the unchanged, previously disclosed dataset to the same targetclear — delete local telemetry bufferParse the argument (default to status if none given).
bash bin/telemetry.sh status
Show the output to the user.
bash bin/telemetry.sh disable
Confirm: "Telemetry disabled. No events will be collected until you run /telemetry on."
bash bin/telemetry.sh enable
Confirm: "Telemetry re-enabled."
Use {count} for the number after inspect or show in the command's arguments, or 10 when omitted, escaping embedded single quotes as '\'':
bash bin/telemetry.sh inspect '{count}'
Show the output. If empty, say "No buffered events."
bash bin/telemetry.sh export "<path>"
Report the resulting local path. Export validates the same content-free event envelope used by sharing. It does not grant permission to upload the file.
First prepare the proposal. This performs no network I/O:
bash bin/telemetry.sh share
Show the complete output: target, event count, bytes, dataset hash, field list, exclusions, expiry, and exact confirmation command. Then stop. Do not infer confirmation from the request to share, a prior share, notification consent, or any unattended workflow.
Only after the user freshly confirms this exact proposal, run the printed command containing its one-time token. A changed target, changed buffer, expired token, or bad token requires a new proposal. Local events remain after a successful share.
Local instances have no default outbound sink. They may export, name an
explicit endpoint, or explicitly opt into the legacy public relay with
--legacy-public-relay; never select that relay automatically.
bash bin/telemetry.sh clear
Confirm: "Local telemetry buffer cleared."
Structured identifiers and metrics: event/task/actor/org/session identifiers, timestamps, retrieval type, privacy-safe lexical/vector fingerprints when configured, returned/opened artifact identifiers, ranks/order, tool-call count, latency, token counts, writeback outcome, success/failure, and index-spec version. Metric strings are bounded identifiers/enums, not prose.
Raw prompts/queries, passages, file paths, file contents, code, env var values, secrets, conversation content, prose error messages, or command arguments that might contain user content.
/telemetry off — persistent opt-out via state fileEGREGORE_NO_TELEMETRY=1 in .env — env var opt-outDO_NOT_TRACK=1 — standard env var opt-outNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.
The English summary is being prepared. Showing the original description.
Draft, preview, and explicitly send an Egregore group announcement. Use for /announce, telling the team something, or notifying everyone—not a direct message or structured handoff.
The English summary is being prepared. Showing the original description.
Capture an effective prompting or steering technique as a reusable canonical pattern. Use when a prompt chain worked especially well; use /reflect for insight about the work and /note for a private thought.
The English summary is being prepared. Showing the original description.
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
The English summary is being prepared. Showing the original description.
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
The English summary is being prepared. Showing the original description.
Stage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
The English summary is being prepared. Showing the original description.