Local enriched
The Ottto app reads local transcript metadata and sends usage-only session rollups.
Best for trusted totals, costs, project context, machine attribution, and drift checks. Raw transcripts stay on the machine.
Ottto brings local usage, live events, connected accounts, cloud billing, and calculated metrics into one cost view. Each number keeps a clear source label so engineering and finance can trust the same dashboard.
Ottto keeps these labels separate because they answer different questions. Local enriched is the default accounting path, Live telemetry is the opt-in liveness path, and connectors pull evidence from services outside the local machine.
The Ottto app reads local transcript metadata and sends usage-only session rollups.
Best for trusted totals, costs, project context, machine attribution, and drift checks. Raw transcripts stay on the machine.
Supported agents can stream live events while they run, giving Ottto a real-time pulse.
Use it for the Activity Feed, live connection state, and per-request records. It adds detail; it does not replace local accounting.
Ottto pulls usage from tools and services that do not have a local transcript path.
Cursor and future hosted IDE sources belong here unless they explicitly emit live events.
AWS, GCP, and similar billing pulls are a focused kind of integration connector.
They help compare coding-agent sessions with provider bills without describing cloud billing as telemetry.
Ottto turns source evidence into totals, estimates, rollups, and reconciliation states.
The Data Dictionary names which values are direct evidence and which values are calculated.
For Claude Code and Codex, start with the Ottto app. It gives Sessions and Costs the richest accounting data with low setup friction. Turn on Live telemetry when your team needs real-time activity and request-level records. Connectors stay separate, so Cursor, AWS, GCP, and future services can be added without changing local agent configuration.