{"version":"2.1.223","anchor":"oversized-memory-files-are-now-surfaced-instead-of-silently-","canonical_anchor":"oversized-memory-files-are-now-surfaced-instead-of-silently-","heading":"Oversized memory files are now surfaced instead of silently skipped","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/oversized-memory-files-are-now-surfaced-instead-of-silently-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Oversized memory files are now surfaced instead of silently skipped\n\nYou now get told when a memory file is too big to sync to shared memory.\n\n**What**\n\nFiles 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.\n\n**Details**\n\n- The sync collects skipped files into `skippedOversizedPaths` and derives an `oversizedSkipped` count in the result summary, alongside the existing `secretsSkipped`.\n- The `tengu_team_mem_multistore_sync` event reports an `oversized_skipped` total next to `secrets_skipped`.\n- 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.\n- Notices are de-duplicated per mount until the file drops off the oversized list; oversized paths are also passed to the post-pull handler.\n\n**Evidence**\n\n`skippedOversizedPaths`, `oversizedSkipped: r.skippedOversizedPaths.length`, `oversized_skipped`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}