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

Oversized memory files are now surfaced instead of silently skipped

You'll notice
Useful3 Signal0
Memory

You now get told when a memory file is too big to sync to shared memory.

What

Files above the 102400-byte per-file limit were already skipped during team-memory multi-store sync, but only noted in an info log. They are now counted, logged at warn level, and reported to you in session.

Details
  • The sync collects skipped files into skippedOversizedPaths and derives an oversizedSkipped count in the result summary, alongside the existing secretsSkipped.
  • The tengu_team_mem_multistore_sync event reports an oversized_skipped total next to secrets_skipped.
  • A per-file in-session notice explains that the file is saved locally but not synced to shared memory, that its changes will be lost when the machine is recycled, and instructs Claude to tell the user.
  • Notices are de-duplicated per mount until the file drops off the oversized list; oversized paths are also passed to the post-pull handler.
Evidence

skippedOversizedPaths, oversizedSkipped: r.skippedOversizedPaths.length, oversized_skipped

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 →