Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Session logs get a place in the managed storage layer

Under the hood
Useful3 Signal4
Sessions

Session transcripts can be addressed through managed storage by project and date, and /debug reads them that way.

/debug
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, /debug falls 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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →