OpenTelemetry
It uses the same harness and extension system as your other agents, so you can replace or disable tools, override skills, and add your own instructions.
To name a few, we were able to cut out 25k lines of code, cut our AI costs in half, and improved runtime by 66%.Chris Fleissner Copy link to headingShare agent capabilities with extensions Since the preview, we've added extensions so teams can share tools, skills, instructions, connections, channels, schedules, hooks, and subagents without copying files between agents.
They need extra storage writes for inputs above the payload size limit, so sending less session data helps keep turn times consistent as sessions grow.
If you host eve yourself, you can export them to an OpenTelemetry backend, including one you run yourself.
What's changed - Added auto mode for Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry and Claude apps gateway; interactive sessions with no permission mode start in it - Added "onFailure": "block" for mcp_tool hooks, as for command and HTTP hooks: a hook whose call fails blocks the action - Added a warning when a message from a session that skips permission prompts may be held and dropped by a cloud session - Added a notice in /status and claude doctor when an OpenTelemetry exporter has no endpoint and its data would likely be lost - Added CLAUDE_CODE_DISABLE_DEFERRED_TOOL_RESUME, which lets a host stop claude