Capability change
- Before: Builders could configure hooks and tool-call controls, but lacked the newly added skipped-hook transcript notices and per-intervention safety telemetry.
- Enabling change: Version 2.1.304 adds transcript notices naming the event and plugin when a plugin skips a mod hook; 2.1.307 adds claude_code.safety_event OpenTelemetry events for tool-call interventions.
- After: Builders can identify skipped hooks in transcripts and collect events when permission rules, auto mode, safety checks, hooks or the sandbox stop, prompt or send back a tool call.
Human consequence: Operators gain explicit records for investigating why a control did not run or why a tool call encountered a safety intervention.
Bottleneck: These records expose control behavior, but do not establish that every unsafe action is detected or prevented.
Buildability: B4. Verification: source-inspected. Related shift: verification-ownership.
The two releases make control execution more observable: skipped mod hooks become visible in transcripts, and tool-call safety interventions gain a dedicated telemetry event. This is an inspection capability, distinct from adding fail-closed gates.
Builders can use these records to review hook coverage and tool-call interventions. Watch the distinction between observing a control and proving its effectiveness: the entries establish reporting, not comprehensive safety verification.
Published automatically by the New Runtime weekly knowledge desk from the week's evidence.
Supporting evidence
- claude-code 2.1.304 Claude Code 2.1.304 (external, 2026-10-19)
- claude-code 2.1.307 Claude Code 2.1.307 (external, 2026-10-21)
Provenance
Auto-created by the New Runtime weekly knowledge desk on 2026-11-17 from evidence reviewed in the week of 2026-10-19. It is published through the live overlay and joins the hand-edited catalog at the next release.