REPLUME / TELEMETRY

CLI telemetry

Published 0.2.5 has no CLI telemetry. The pending telemetry build will turn it on by default after showing a notice at init. No account or key is needed. It sends counts to https://replume.dev/t, which forwards accepted events to PostHog (US). A random install ID is stored at ~/.replume/telemetry.json. It is separate from website analytics.

Controls in the telemetry build

replume telemetry status
replume telemetry show
replume telemetry on
replume telemetry off

show prints the next payload. REPLUME_TELEMETRY=0 or DO_NOT_TRACK=1 disables sending. Telemetry is disabled in CI and from a source checkout. The local queue keeps unsent counts for up to seven days.

What is sent

The CLI sends one JSON array per request, with up to 50 events accepted by this endpoint. The endpoint allows two requests per install ID per UTC day. Each event is checked independently; unexpected fields are dropped with that event.

• schema, install_id, event (ping, installed, uninstalled, session_end), ts.
• cli_version, os, arch, node, agent, runner, isolation, review.
• sessions; verdicts counts for pass, fail, incomplete and no_changes.
• interventions counts by rule and warn, block or recovered; incomplete_reasons counts by reason code.
• done_gate_ms_median, test_runs, repo_bucket (small, medium or large).

The dashboard uses session_end only for sessions and verdicts. A ping repeats accumulated counts, so counting it as another session would be wrong.

What stays on your machine

Code, diff, prompt, task text, test output, paths, repository name, commit messages, email and tokens are never sent in this telemetry. The server rejects unexpected fields. Private rate-limit slots hold no event content.