Claude Code v2.1.223 ·
Memory-API entry schema accepts size_bytes and updated_at
Memory entries with size and update-time fields from newer servers no longer break parsing.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
MemoryArea: what it touches
Internal ChangesKind: in v2.1.223,
Internal ChangesSection of the release
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 →
