{"version":"2.1.247","anchor":"memory-files-can-be-checked-for-size-and-frontmatter-after-a","canonical_anchor":"memory-files-can-be-checked-for-size-and-frontmatter-after-a","heading":"Memory files can be checked for size and frontmatter after a write","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/memory-files-can-be-checked-for-size-and-frontmatter-after-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Memory files can be checked for size and frontmatter after a write\n\nMemory files can be checked after a write for oversize, split files and bad descriptions.\n\n**What**\n\nA new check runs after a Write or Edit on a file in the memory directory and can hand Claude up to three kinds of feedback: a warning that the file is at or over the size that recall reads, a note that a `name-2.md` continuation file sits next to an existing `name.md`, and a complaint that the frontmatter `description` is missing or longer than 300 characters. It runs only in memory-directory mode plus a second per-path condition whose implementation is not present in the shipped bundle, so whether the lint path ever fires is decided elsewhere.\n\n**Details**\n\n- The feedback is attached as additional context on the tool result, not shown to you directly.\n- The over-cap warning states that the write succeeded but that recall shows other sessions only the first portion of the file.\n- Two telemetry events accompany the check.\n- Memory-directory mode is the same condition that suppresses the older automatic-memory entry.\n\n**Evidence**\n\n`tengu_memdir_file_lint`\n\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}