◉CLAUDE LABJP
●WATERMARK — Since 11/16, text from Opus 4.6, Sonnet 4.5 and other models carries a watermark; non-default temperature and similar settings may drop it●CC 2.1.325 — Claude Code is still on 2.1.325 (11/13), with no newer release yet●SONNET 4.5 — Retires on the Claude API on 11/30, 13 days left. Sweep model IDs in code and saved settings in one pass●AUTOMATION — A user reports recurring AI jobs set up without run counts or a spending cap, burning through a weekly allowance●CONNECTOR — If connectors vanish only in new sessions, compare the /mcp list against an older session first●NEW — Cowork Feels Worse? Run the Same Request in Three Fresh Sessions●WATERMARK — Since 11/16, text from Opus 4.6, Sonnet 4.5 and other models carries a watermark; non-default temperature and similar settings may drop it●CC 2.1.325 — Claude Code is still on 2.1.325 (11/13), with no newer release yet●SONNET 4.5 — Retires on the Claude API on 11/30, 13 days left. Sweep model IDs in code and saved settings in one pass●AUTOMATION — A user reports recurring AI jobs set up without run counts or a spending cap, burning through a weekly allowance●CONNECTOR — If connectors vanish only in new sessions, compare the /mcp list against an older session first●NEW — Cowork Feels Worse? Run the Same Request in Three Fresh Sessions
Articles/Cowork
◈ Cowork/2026-11-17Intermediate

78 Memory Files Outside the Index: Retiring Cowork Project Memory Without Deleting It, and Moving Decisions Into Docs

I had been keeping app-operations decisions in a Cowork project's memory, and 78 files had drifted out of the index. Three scripts (find, retire-and-restore, index lint) and the line I drew between memory and docs.

Cowork68Project MemoryMEMORY.mdDocumentationOperations25

✦ Premium Article

On September 13 I asked Claude, inside the Cowork project I use to run my wallpaper apps, to help me tidy the project memory. When it compared the memory index (MEMORY.md) with what was actually sitting in the folder, the two did not match at all.

78 memory files could not be reached from the index. I had never deleted any of them on purpose. Each time I "cleaned up", I had only removed the line from the index. I had quietly assumed that a shorter index meant a tidier memory, and that assumption was mine, not the tool's.

What follows is how I retired those files between mid-September and early October, and the three small scripts I keep around now. Every number comes from my own indie developer project. I reran the scripts on a dummy folder with the same layout and checked that the output matches what I describe.

What was left behind

I later copied the full text of the retired files into my app documentation folder as a backup. Recounting that backup (74 files are still readable there) gave this picture:

What I looked atCountWhat it tended to be
A date in the file name65 of 74Diagnoses, weekly checks, release plans: work that was finished once it reached a conclusion
Description saying "merged / retired"5Files whose content had already moved into another memory, but the file itself was still there
type: projectMost of themVery few feedback or reference entries; nearly all were snapshots of a situation
SizeMedian about 3.3KB, largest about 17.7KBThe largest was a plan that really belonged in a document

The first thing I want to say is that what had piled up was not "things to remember" but records of finished work. A dated diagnosis note mattered on the day I wrote it. Once it reached a conclusion, only the conclusion mattered, and the numbers and back-and-forth did not need to ride along with every new task.

The five stubs made me stop for a moment. When I merged them, I had rewritten their descriptions to say "content moved over there" and dropped them from the index, yet the files stayed in the folder. Removing something from the index and retiring it turned out to be two different jobs.

The mistake: thinking the index was the cleanup

Looking back, every tidy-up I had done amounted to deleting index lines. A shorter index felt like a weight off my shoulders. I never checked how files outside the index were treated afterwards in my setup, and I still have not verified it. Without that check, I had no grounds to say leftover files were harmless either.

There was also a practical wall. At the time, the memory folder was read-only from the session, so Claude could not move the files itself. We split the work: Claude wrote a shell script full of move commands, I read it, and I ran it in Terminal. That split ended up being the arrangement I trusted most.

The line I drew from this is simple.

Decisions live in documents; memory only keeps the way there.

Memory holds one line about what counts as the source of truth, plus the number or section of the canonical document. History, figures and half-formed hypotheses go into the document.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦You will be able to spot memory files that fell out of the index, and leftover merged stubs, in one list before stale decisions start leaking into your work
✦You can now tidy project memory with a paired retire script and restore script, without deleting a single file
✦You will be able to decide, for your own project, that decisions live in canonical docs and memory keeps only a one-line summary and a pointer
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

◈ Cowork2026-10-18
I Preloaded a Scheduled Task with head -150: 15.6 KB Read, 3.3 KB for Today
A scheduled task preloaded its daily notes with head -150, and line count turned out to be no budget at all. A date-block reader with a byte ceiling, and how to avoid dropping ideas nobody has used yet.
◈ Cowork2026-10-01
Before You Trim a Scheduled Task's Runbook, Count How Many Times It Gets Re-read
I cut 13 KB from a scheduled task's preloaded docs, and recounted by re-reads it was worth about 1.3 tool calls. Here is the ledger that counts re-reads, and a shell helper that records bytes during a run.
◈ Cowork2026-09-24
Will Your Cowork Scheduled Task Still Run Next Saturday?
A definition that runs once and stops, two fire times packed into one task, a weekday that quietly emptied after an edit. Cowork schedules can go missing without leaving a single log line. Here is a working audit that compares what you defined with what you meant.