Nothing to try yet Notable
A tool.output telemetry event can carry file contents, diffs and bash commands after a successful tool call, behind a gate.
After a successful Write, Edit, Read, or Bash tool call, Claude Code can now assemble a tool.output telemetry event carrying details like file_path, content, and a diff for edits, or bash_command/output for Bash calls. A gating check function runs before any field is included.
Names in the bundletool.output
Documented inclaude-code/agent-sdk/observability
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up tool.output, on Monitoring.
| `OTEL_LOG_TOOL_CONTENT` | Enable logging of tool content in the [`tool.output` span event](#tool-output-span-event) (default: disabled). Span attributes carry tool content under [their own gates](#new-context-gates). Requires [tracing](#…monitoring-usage see the edit
Added since
A small documentation edit on Observability with OpenTelemetry touched a line naming tool.output after this was published.
| `OTEL_LOG_TOOL_CONTENT=1` | A [`tool.output` span event](/docs/en/monitoring-usage#tool-output-span-event) on `claude_code.tool` with file contents and Bash output, truncated at 60 KB by default, configurable via `CLAUDE_CODE_OTEL_CONTEN…agent-sdk/observability see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Observability with OpenTelemetry touched a line naming tool.output after this was published.