home
Telemetry
Usage telemetry helps improve chronicle. It does not include your code or repo metadata.
Collected
- + Command names, command success/failure, and duration
- + Commit and file counts for analyze/backfill events
- + Configured AI provider, model category, request type, cache hit, and latency
- + CLI version, OS type, and basic setup/config event metadata
Not Collected
- - Source code, diffs, or file contents
- - Commit messages, file paths, or repository URLs
- - API keys, credentials, or access tokens
- - Personal data sent through your repo or prompts
Note
During analyze and backfill, code and other text-like changes may be sent to your configured AI provider to generate commit plans and messages. That provider traffic is separate from Chronicle telemetry.
Opt-Out
chronicle config telemetry --opt-out
Or set CHRONICLE_TELEMETRY=false in your
shell.
Local telemetry state and pending events are stored at ~/.config/chronicle/telemetry.json and ~/.config/chronicle/telemetry-events.jsonl