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.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

Memory-API entry schema accepts size_bytes and updated_at

Under the hood
Useful2 Signal0
Memory

Memory entries with size and update-time fields from newer servers no longer break parsing.

What

Memory entry payloads from newer servers parse without error.

Details
  • The schema gained an optional non-negative integer size_bytes alongside the existing content_size_bytes.
  • It also gained an optional updated_at string that falls back to undefined via .catch(void 0) rather than failing the parse.
Evidence

size_bytes: w.number().int().nonnegative().optional(),

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.223 →