Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
TelemetryArea: what it touches
In DevelopmentKind: in v2.1.257,
What probably matters to youSection of the release
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.
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 sinceAnthropic'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-usagesee the edit
Added sinceA 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/observabilitysee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesA small documentation edit on Observability with OpenTelemetry touched a line naming tool.output after this was published.
