Observability and cost intelligence for AI coding agents

See how your AI agents work. Understand what drives the cost.

Ottto reconciles local agent sessions with subscription, API, and cloud billing evidence—so you can connect agents, recurring work, repositories, models, and context to cost.

No model-call proxySources and estimates stay labeledRecommendations stay reviewable

Agent family Illustrative example
Family viewMap · Timeline · List
Workflow viewRecurring group
EvidenceSource + coverage
Trace a task from its root session through launched agents, with evidence and coverage in view.
Why Ottto

AI coding work no longer fits in one prompt—or one bill.

A root agent launches reviewers and testers. Scheduled jobs repeat. Skills and tool schemas consume context. Work crosses machines, repositories, models, subscriptions, APIs, and cloud accounts. Provider bills show totals; Ottto connects those totals back to the work.

↗

Agent lineage

Trace parent-to-child relationships backed by launcher evidence.

↻

Recurring work

Group repeated runs by supported schedule, template, or title evidence.

◫

Context footprint

Compare composition and posture across repositories and machines.

$

Mixed billing

Keep subscriptions, metered APIs, credits, and cloud costs distinct.

How Ottto works

Collect. Reconcile. Review.

Ottto observes alongside supported tools. It never sits in the model-call path.

01

Collect

Gather the evidence each connected source can provide: Local enriched activity, optional Live telemetry, integrations, and cloud billing.

02

Reconcile

Join supported sessions, accounts, machines, repositories, plans, usage, and bills while preserving source and billing basis.

03

Review

Turn reconciled evidence into reviewable recommendations with an impact basis, caveats, safeguards, and a clear next step.

Recurring work

Turn repeated runs into a workload you can inspect.

Ottto groups recurring work from supported schedule, template, and title evidence. See each group’s cadence, tokens, cost, models, machines, and run history—before the pattern disappears into a monthly total.

  • ✓

    Evidence defines the group. Repetition is a pattern; it is not proof that a run was automated.

  • ✓

    Runs remain inspectable. Open any group to review the sessions behind it.

  • ✓

    Unknown stays unknown. Missing origin is labeled “No automation evidence,” not guessed as “human.”

Runs  |  GroupsIllustrative example
Grouped runs12
Observed cadenceWeekdays
Group cost$18.42
↻
Release readinessSchedule definition · exact-title evidence
Open group →
Codex + Claude Code2 machinesRun history available
i

No automation evidence remains a separate, visible remainder whenever supported origin facts are absent.

Illustrative example based on the shipped recurring-groups evidence model.
Agent families

Trace cost across a delegated task’s recorded agent family.

Agent Families links a starting session to the agents it launched, showing each run’s cost and where lineage evidence is incomplete. Switch among Map, Timeline, List, and Details without losing your place.

MapTimelineListDetails

Each supported edge names its provider or launcher evidence. Missing or truncated lineage stays visible.

Selected family
Illustrative example
Root cost$6.10
+
Launched agents$12.32
=
Family cost$18.42
Illustrative costs. Actual views disclose lineage coverage and truncation.
Context intelligence

See what fills the context window.

See what enters context, how it persists across later turns, and how the footprint changes by repository and machine. Measurement boundaries distinguish what is observed, modeled, or unavailable.

Repository AContext composition
Illustrative example
Startup instructions 26% Shell output 22% Files & docs 19% Browser captures 12% Delegated agents 13% Other tools 8%
Counted at entryObserved or estimated onceResidency across turnsModeled persistence after entry
Illustrative composition. Actual views keep estimates, coverage, and measurement boundaries visible.
◫

Context composition

Break down startup instructions, file reads, tool output, browser captures, memory, and delegated-agent results.

⌁

Context posture

Compare startup, growth, measured peaks, pressure bands, and recorded compactions.

≣

Memory & tool footprint

Review repository memory files and configured MCP tool-schema context by supported agent and machine.

Cost intelligence

Connect how agents run to how you pay.

Break supported spend down by tool, model, session, repository, source, and billing path. Keep subscription fees, metered APIs, credits, quota windows, and cloud bills distinct so one total never hides different cost bases.

  • ✓

    Charges stay charges. Provider-reported overage stays separate from flat fees and what-if equivalents.

  • ✓

    Unknown limits stay unknown. Missing quota windows are omitted instead of shown as zero.

  • ✓

    Coverage stays visible. Partial, stale, unsupported, and still-learning states remain part of the answer.

ReconciliationIllustrative flow
Local enriched Live telemetry Integration connectors Cloud billing connectors
otoReconcilematch · price · label
SubscriptionPlan fee + quota evidenceAccount basis
Metered APIUsage at sourced ratesRate basis shown
CloudProvider billing dataFreshness shown
Illustrative flow. Each metric carries the availability and confidence supported by its sources.
Evidence and recommendations

Know what the number means before deciding what to do.

Use the Data Dictionary to check a metric’s definition, unit, source, availability, and calculation rules. Advisor recommendations pair each signal with supporting evidence, an impact basis, a next step, and a safeguard.

≣
Understand the metric

Data Dictionary

Check meaning, unit, source class, availability, and calculation rules.

Local enrichedLive telemetryCalculated by Ottto
Read the product docs →
✦
Evaluate the next step

Advisor recommendations

Review a signal alongside its evidence, impact basis, recommended next step, and quality safeguard.

SignalEvidenceRecommendation
Explore Advisor →
◎
Account for outside changes

Provider Changes

Review recent provider status, model, quota, policy, and pricing changes matched to active tools when supported.

Relevant to an active toolFreshness and source timing shown
Explore Provider Impact →
The surfaces

Every surface, one account.

Observe the work. Optimize how it runs. Manage how you pay. Verify the evidence behind every decision.

01

Observe

Trace individual runs, recurring work, and the agent families they form.

02

Optimize

Explain how models, effort, caching, tools, and context shape cost.

03

Manage money

Keep subscriptions, metered APIs, credits, and cloud billing on their actual bases.

04

Verify & review

Check how each number was produced, then review what to do next.

Start with current evidence

See the agents behind the spend.

Install Ottto, connect the sources you choose, and turn scattered agent activity and billing data into one evidence-backed view—then review what deserves attention.

Free to start · No credit card required · Apple silicon · macOS Sonoma or later