DocumentationCoding agents

Usage telemetry and collection

Understand Claude Code and Codex telemetry installed alongside hooks and its reporting limits.

Updated 2026-09-22 Read as Markdown
On this page

What setup changes

Claude Code and Codex hook installation configures usage telemetry by default. Organization settings manage its posture. Inspect the local wiring with:

kastra-edge telemetry status

The status command reports the wiring; it is not an enable/disable command. Do not invent telemetry off or config set telemetry commands. Coordinate organization-level changes in the console and recheck the device configuration.

What the data means

Claude Code and Codex reported usage arrive as client-reported OTLP events. It is distinct from traffic metered through Kastra’s proxy. A device may be governed while reporting no usage, and missing telemetry does not mean zero activity or zero spend.

The fleet usage view includes reporting coverage and provenance. Cost amounts can be priced or estimated and may still need provider-invoice reconciliation. Reported usage is not the input used to enforce proxy spend caps.

Agent hooks send action context for evaluation and recording. Recon separately reads supported history and uploads redacted candidates after its consent flow. Data handling explains masking and recorded-payload boundaries.

Verify

Check telemetry status, the workspace selected by device login, recent supported activity, and the console’s reporting coverage. Investigate missing or partial reporting before using a cost view for decisions.

Codex setup and privacy

Run kastra-edge install-codex after login, then restart Codex to load its exporter. Updating Edge alone does not rewrite an existing Codex configuration. Setup preserves unrelated settings and refuses a conflicting foreign telemetry configuration. It disables user-prompt logging; diagnostic events can still carry tool details to the intake, which stores only recognized usage metadata.

Codex token usage is reportable, but its per-request cost is unavailable. Partial or unavailable cost must not be shown as free usage. Telemetry configuration and a recent login do not prove successful delivery.