Sync

Opt-in telemetry export to an OTLP endpoint you control.

Nothing Leaves Your Machine By Default

Every other CodeBurn command reads local files and writes local output. sync is the only command that sends anything anywhere, and it does nothing until you run sync setupagainst an endpoint and complete a browser login. It sends token counts, costs, models, and projects — never prompts or code. This feature is in preview and the protocol may change between releases.

Setup

codeburn sync setup https://otel.example.com

Setup fetches a discovery document from the endpoint to learn its OIDC issuer, client ID, and traces path, then runs an authorization-code login with PKCE in your browser against that issuer. The refresh token is stored in the OS keychain where one is available (macOS Keychain, secret-tool, Windows DPAPI), falling back to a0600 file. Non-secret configuration is written to ~/.config/codeburn/sync.json.

Pushing

codeburn sync push                       # last 7 days
codeburn sync push --since 30d           # a larger window
codeburn sync push --dry-run             # show what would be sent
codeburn sync push --attribution         # also send git attribution spans

Calls are converted to OTLP spans and posted in batches to the traces path from the discovery document. A local sent-ledger means a repeated push only sends what has not already been accepted, and a push that is rate limited or interrupted resumes on the next run. An incomplete push exits non-zero so cron jobs can detect it.

Status and Teardown

codeburn sync status             # endpoint, issuer, auth state, last sync
codeburn sync logout             # revoke the token and remove credentials
codeburn sync reset --confirm    # clear the sent-ledger

logout revokes the token at the identity provider when it advertises a revocation endpoint, then deletes the stored credential and the sync config. reset clears the sent-ledger, so the next push re-sends everything in the window; --confirm is required.