Claude Code and Codex, one OpenTelemetry config change, full visibility in minutes.

Your engineers use AI agents daily. Do you know the cost?
AI coding agents generate real spend, real risk, and real waste. Oodle surfaces all three without any instrumentation work.
Track spend by user, model, team, repository, and session. Identify top spenders and wasteful patterns before the bill arrives.
AI-powered insights on every session: context runaway, cache efficiency, model mismatch, vague prompts. Actionable, not just data.
Native OpenTelemetry from Claude Code and Codex. One env var or config file, no SDK, no code changes.
Cost. Sessions. Tools. Covered.
Full visibility into how your engineering team uses AI coding agents.
Slice spend by user, model, query source, agent, skill, team, and git repository. Know who spends what and why.

Every session gets automated analysis: context growth warnings, cache efficiency scores, model mismatch detection, and tool-heavy session flags.

Track every tool call: frequency, duration, result size. Spot MCP tool bloat, bash anti-patterns, and context pollution.

Monitor cache hit rates across users and models. Identify ghost cost from sessions that repeatedly re-prime cache after idle gaps.

Tie AI spend to engineering output. Compare cost per pull request, sessions with commits vs without, and cost per line of code.

Expand any session into a searchable turn-by-turn log: prompts, API calls, tool decisions, and tool results with raw JSON.

Link Claude Code OTEL traces directly to session context. Debug slow tools or failed API calls with full distributed trace waterfall.

How It Works
Three steps from zero to full AI agent visibility.
Add OTEL env vars to ~/.claude/settings.json or ~/.codex/config.toml. Oodle generates the config for you from the integration page.
Token usage, costs, tool calls, and prompts stream to Oodle via OTLP. No collector, no pipeline to maintain.
Pre-built dashboards, AI analysis, and cost alerts. Every session analyzed for waste, risk, and optimization opportunities.
See It With Your Team's Sessions
Book a call to see how Oodle tracks your AI agent usage, cost, and efficiency.
Frequently Asked Questions
~/.claude/settings.json. For Codex, add an [otel] block to ~/.codex/config.toml. No SDK, no code changes, no collector to maintain.OTEL_LOG_USER_PROMPTS. Tool detail logging is opt-in via OTEL_LOG_TOOL_DETAILS. You can also scope telemetry to specific teams and repositories using OTEL_RESOURCE_ATTRIBUTES.