Claude adds OpenTelemetry tracing: why AI agent observability belongs in your software brief

Anthropic put OpenTelemetry tracing into public beta on 14 October 2026, covering Claude Managed Agents, the Messages API and the SDK. For anyone commissioning AI software, it makes AI agent monitoring a reasonable thing to ask for.

On 14 October 2026 Anthropic released OpenTelemetry tracing in public beta across the Claude platform. It covers Claude Managed Agents, the Messages API and the Claude SDK. The search term to watch is “AI agent observability”, which is moving from engineering jargon to a line on buyer checklists.

What it actually does

Every step an AI agent takes can now be recorded as a trace: how long each call took, how many tokens it used, which model ran, which tools were called and whether they succeeded. A single trace can follow a request from your own application code, through the model, into the tools the agent used and out to any connected services. An optional full-content mode also records the prompts and responses themselves.

Traces use the standard OpenTelemetry format, so they can be sent to monitoring tools teams already use, such as Grafana Cloud, Sentry, Splunk or New Relic. No new monitoring stack is needed. It is a public beta, so the data format and configuration may still change.

Why this matters if you are not an engineer

AI features fail differently from normal software. A normal bug throws an error. An AI agent can quietly give a wrong answer, loop on a task, or run up a bill. Without tracing, the first you hear about it is a customer complaint or an invoice. With tracing, someone can see which step went wrong and reproduce it.

The same applies to cost. Token counts per step are exactly the data you need to answer “why did our AI bill double?” without guessing.

One caution

Full-content tracing stores prompts and responses. If those contain customer, patient or financial data, that is personal data you now hold somewhere else. Decide what gets logged, where it is stored and for how long before switching it on, particularly in regulated work.

So what

If you are commissioning an AI product, add three questions to your brief: how will we see what the agent did, who watches the cost per task, and what is logged about our users. A supplier who cannot answer clearly is building a demo, not a product.

Observability is part of how we build AI products and run AI-assisted development at BuildApps. If you are scoping an AI feature and want monitoring designed in from day one, start a project.

← All research

More research.

GitHub's Copilot metrics now count OpenCode and Claude Code traffic: who really uses which AI coding tool

On 23 October 2026 GitHub added a per-tool breakdown to the Copilot usage metrics API, so tools such as OpenCode and Claude Code are counted even without editor telemetry. It shows how mixed the AI coding tool stack inside software teams has become.

Read ›

GitHub Copilot retires Claude Opus 5 and GPT-5.6 Terra on 16 November: the model-churn bill for buyers

GitHub has announced that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra leave every Copilot experience on 16 November 2026. For anyone commissioning AI-assisted development, model retirement is now a monthly event to plan around.

Read ›

GitHub Copilot now benchmarks how 'agent-first' your developers are against your industry

On 22 October 2026 GitHub added opt-in industry comparisons to its Copilot impact dashboard, ranking firms by share of agent-first developers and by the merge rate of agentic pull requests. Here is how to read the numbers when you are buying software.

Read ›

Apple's new bait-and-switch rule 2.5.19: what it means for AI-built and fast-shipped apps

On 16 October 2026 Apple updated its App Review Guidelines: apps that change after approval can be removed from the App Store and the Developer Program, and AI-generated intimate imagery is now explicitly covered. Here is what founders commissioning an iOS app should check.

Read ›

GitHub Copilot agentic autofix is generally available: AI now fixes security alerts, and bills for it

GitHub made agentic autofix for code scanning alerts generally available on 15 October 2026. Copilot can now fix up to 25 security alerts in one pull request, using AI credits your supplier or your team pays for.

Read ›

GitHub AI Scan for pull requests goes GA: AI security checks for PHP, Terraform and Dockerfiles

GitHub's AI Scan for pull requests became generally available on 15 October 2026, checking languages the standard scanner misses. Findings are advisory and cannot block a merge, which matters when you buy software.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work