The memory lint runs in memory-directory mode plus a second per-path condition whose implementation is absent from the bundle.
A 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.
- The feedback is attached as additional context on the tool result, not shown to you directly.
- The over-cap warning states that the write succeeded but that recall shows other sessions only the first portion of the file.
- Two telemetry events accompany the check.
- Memory-directory mode is the same condition that suppresses the older automatic-memory entry.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.