What
Session transcripts can now be addressed through Claude Code's managed storage layer, keyed by project, date and log name, and /debug reads its log that way when that storage layer is available.
Details
- The key is built from a project key, a year/month/day triple that is validated, and a log name that must match the session log's own name.
- The scope is listable, so logs under a project and date can be enumerated.
- Without the storage backend,
/debugfalls back to reading the log file directly.
Evidence
sessionLog
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/debug
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 /debug, on Hooks reference.
Hook execution details are written to the debug log file. Start Claude Code with `claude --debug-file <path>` to write the log to a known location, or run `claude --debug` and read the log at `~/.claude/debug/<session-id>.txt`. The `--debu…hooks see the edit
Added since
A small documentation edit on Channels reference touched a line naming /debug after this was published.
* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de…channels-reference 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 Channels reference touched a line naming /debug after this was published.