TL;DR: Claude got quieter (reasoning + tool traces). Devs lost breadcrumbs (“what did it touch?”).
Fix: Add receipts. AGENTS.md + a hook that logs
git diff --name-onlyandgit status --porcelain.(Ctrl+O to expand the context — Ctrl+O = Claude Code “expand details”, not your browser.)
The Squeeze: Two Kinds of Quiet
1. The Thinking Got Summarized
Feb 2025: Anthropic shipped Claude 3.7 Sonnet with visible extended thinking. You could watch raw reasoning in real-time—the model giving “itself more time” to reach an answer.
2026: Newer Claude generations summarize long thought processes. The chain-of-thought is still there. You just get the digest by default.
Anthropic noted the tradeoff early: visible thinking may not reflect “what’s going on in the model’s mind.” Safety concerns followed—chains could be exploited for jailbreaks.
2. The Tools Got Collapsed
Claude Code used to stream every file read:
Read: src/auth/handlers.ts (234 lines)
Read: src/auth/types.ts (45 lines)
Glob: **/*.config.ts (3 matches)
Now you get:
Read 3 files [Details: Ctrl+O]
Same information. One more keystroke. Multiply by a hundred tool calls per session.
HN user yoshiyosh captured the dev frustration:
“I don’t want verbose mode. I want Claude to tell me what it’s reading in the first 3 seconds, so I can switch gears without fear it’s going to the wrong part of the codebase.”
Boris from the Claude Code team responded: as agents run longer (“minutes, hours, days”), output overwhelms. Progressive disclosure works for most. But they “missed the mark for a subset.”
War Stories
The wrong search: Agent searched billing but never touched invoice. With visible search patterns, you catch this in 10 seconds. Without them, you find out after the refactor.
The wrong directory: Agent read packages/api/ when the fix needed apps/web/. File paths in the stream = drift you can redirect early.
The sensitive touch: Agent touched .env.example. You need to know now, not in the git diff later.
Without breadcrumbs, you’re supervising blind.
Fair Version
Terminal noise is real. A busy session generates hundreds of tool calls.
Progressive disclosure isn’t evil—it’s a legitimate UX tradeoff.
Anthropic’s post framed the tradeoff: visible thinking helps trust research, but poses “safety concerns.” Future releases would weigh the “pros and cons” of transparency.
The quieter UI wasn’t a conspiracy. It was a weighted decision.
The Fix: Audit Ledger (AGENTS.md)
If you’re new to AGENTS.md, start with the practical guide first. This pattern extends that foundation.
One file. Three parts. Run ledger + provenance + audit trail in one system.
Part 1: The Ledger Section
Add to your AGENTS.md:
| |
Part 2: The Hook (Read-Only, Strict)
Read-only hook: runs git status/diff and appends to AGENTS.md. Strict mode prevents partial writes. No-op in non-git dirs. Always logs—even “(none)” or “(clean)"—so you know the agent ran.
| |
Save to ~/.claude/hooks/audit-ledger.sh, make executable, enable via /hooks in Claude Code. See Hooks Guide for event types and configuration.
Part 3: One Prompt Rule
Add to your CLAUDE.md:
| |
Done. You’ve rebuilt observability without fighting the UI.
Spoke-and-Wheel: Where This Fits
Hub: /agents/agents-md/ — Templates and conventions for agent guidance files
Spokes:
- This article — The transparency problem + Audit Ledger fix
- /posts/agents-md-practical-guide/ — What actually works with AGENTS.md (evidence-based)
- /compare/codex-vs-claude-vs-cursor/ — Tool comparison including transparency tradeoffs
Operational context: This site’s own AGENTS.md defines content taxonomy and conventions. The Audit Ledger pattern extends that foundation with runtime observability.
Related Links
- /agents/agents-md/ — Practical guide with templates
- /posts/agents-md-practical-guide/ — Evidence-based deep dive on AGENTS.md patterns
- /compare/codex-vs-claude-vs-cursor/ — Tool comparison including transparency features
- /agents/ — AI agent ecosystem overview
- /AGENTS.md — This site’s agent guidance (operational file)
Last reviewed: 2026-02-17 Evidence level: High (vendor documentation, community reports, tested hook script)