Skip to main content
Trace Claude Managed Agents sessions and Atomic Agents apps in Phoenix, and test Gemini 4 Argon and Meta Muse Wonder 1.0 in the playground. Self-hosted deployments can also send the Phoenix server’s own logs to an OpenTelemetry collector.

​
Tracing for Claude Managed Agents and Atomic Agents

October 15 to 16, 2026 New integration guides; no Phoenix upgrade required Two more agent stacks can send traces to Phoenix.
  • Claude Managed Agents. Add an Arize Phoenix destination in the Claude Console to export agent turns, model requests, and sandbox tool calls with no code changes. Phoenix converts the OpenTelemetry GenAI spans to OpenInference when they arrive. Trace the Claude SDK from your application too, and each session nests inside your own trace.
  • Atomic Agents. Version 2.11.0+ ships its own OpenInference instrumentor, which emits an AGENT span per agent run and a TOOL span per tool call. register(auto_instrument=True) picks it up automatically.
Phoenix trace view of a fibonacci-agent trace with status OK. The trace tree shows the fibonacci-agent root span, Sessions API request spans, an anthropic.session.turn span, anthropic.model_request spans, and an anthropic.tool_use bash span.

Session turns, model requests, and sandbox tool calls arrive in Phoenix as one trace

Claude Managed Agents

Export spans from the Claude Console and the Claude SDK

Atomic Agents

Trace agents and tools with the built-in instrumentor

​
Gemini 4 Argon and Meta Muse Wonder 1.0

October 15, 2026 Available in arize-phoenix 20.22.0+ You can pick both models in the playground, and Phoenix prices their spans from its built-in model price list.
  • Gemini 4 Argon (gemini-4-argon) appears under the Google provider.
  • Muse Wonder 1.0 (muse-wonder-1.0) appears under the Meta provider.

Using the Playground

Pick a model and compare prompts side by side

Cost Tracking

How Phoenix prices tokens on your spans

​
Export Phoenix Server Logs over OTLP

October 16, 2026 Available in arize-phoenix 20.23.0+ Send the Phoenix server’s own logs to an OpenTelemetry collector, next to the server traces you may already export. Set PHOENIX_SERVER_INSTRUMENTATION_OTLP_LOG_COLLECTOR_HTTP_ENDPOINT or PHOENIX_SERVER_INSTRUMENTATION_OTLP_LOG_COLLECTOR_GRPC_ENDPOINT to turn it on.
  • Logs carry trace and span IDs, so your observability backend can link each log line to the server request that produced it.
  • Endpoints follow the trace collector variables. HTTP endpoints get /v1/logs appended. gRPC endpoints without a scheme connect over TLS, so prefix a plaintext collector with http://.

Configuration

All server environment variables

​
Additional Improvements

October 14 to 16, 2026 Available in arize-phoenix 20.21.4–20.23.0
  • OAuth2 sign-in completes on the first try when an identity provider login happens in the middle of an authorization flow, because Phoenix keeps its SameSite=Strict session cookies.
  • Bedrock tool results reach the model as text in the playground, so tool output that is not valid JSON no longer fails the request.
  • Pressing Escape keeps prompt and dataset labels instead of removing every label from the item.
  • Dataset labels no longer need a description when you create them.
  • Sorting projects by last updated shows the newest projects first on the first click.