Source Intelligence

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

Storage layout reserves a place for per-day session logs

Not switched on
Useful1 Signal4
Internals

Storage keys now reserve space for per-day session logs that nothing reads or writes.

A project/year/month/day session-log storage area exists only in the key builder and validators.

What

The storage key scheme adds a session-log area addressed by project, year, month, day and a log name, with validation on both the key and its scope. Nothing in this build reads or writes it; it exists only in the key builder and the validators.

Details
  • Validation requires a four-digit year and two-digit month and day, a month only alongside a year, and a day only alongside a month.
  • The log name must be a short session id of up to eight word characters, optionally followed by a hyphenated lower-case title slug, and cannot be a bare device name.
Evidence

must be the session-log stem <sessionId8>[-<title-slug>]: up to eight word characters, then lower-case a-z / 0-9 runs joined by single hyphens; not a bare device name, namespace: "sessionLog", must be the session-log stem <sessionId8>[-<title-slug>]

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.232 →