Storage & memory

Coding agents leave a lot behind: caches, logs, transcripts, worktrees and processes that outlive the chat that started them. The Storage page shows what they keep on this Mac’s disk and the Memory page what they are holding in RAM right now. Both say what you would lose before you remove anything, and neither acts without your confirmation.

Storage

Open Storage from the account menu under your name, or press ⌘9. Codz measures when the page first opens, and again after each reclaim.

The top of the page shows how much your agents hold, how much space is free on the disk, and how that splits into four kinds of data. Below it, each provider has a card with its locations, largest provider first, and each location says what removing it costs.

What Reclaim does

The kind of a location decides what Reclaim may do with it, whatever you tick:

These are the locations Codz knows about. It reads only these places in your home folder and leaves anything else to Finder:

Cursor’s workspace state database and OpenCode’s message database are never changed, even if you tick them.

Compacting transcripts

Claude Code’s session transcripts and Codex’s rollout transcripts hold every conversation in full, and they are usually the largest thing on the page. Compacting one keeps every record Codz reads from it, so your usage history and run timings are unchanged, and removes the conversation text.

Codz can’t know what compacting will return without reading the transcripts through, so when you tick one, the button becomes Measure ledgers. Once measured, each transcript says how much compacting would save.

Reclaim space

1. Open Storage (⌘9).
2. Tick the locations you want to reclaim, and untick any you want to keep.
3. If you ticked a transcript, click Measure ledgers and wait for the estimate.
4. Click Reclaim, which shows the total, and read the confirmation. It lists what will be deleted and what will be compacted.
5. Click Reclaim to confirm.

While it works, the page shows which location it is on and a progress bar, and Stop cancels. When it finishes, the page says how much it reclaimed, and names any location it couldn’t clean.

Memory

Open Memory from the account menu, press ⌘0, or click Agent memory in the menu bar. It shows what Claude, Codex, Cursor and OpenCode are holding in RAM right now, and refreshes while you watch.

The top of the page leads with how much memory you could reclaim, then the total your agents hold and how much memory the Mac has, and splits the total by provider. Below it, the processes are grouped:

Each row counts a process together with everything it started. A shell under an agent, and whatever you run from it, such as a dev server, isn’t counted.

A row can carry a note: orphaned — its harness is gone for a helper whose session has ended, working now for a session in the middle of a turn, or the peak it reached when that was much higher than now.

Reclaim memory

Only orphaned helpers are ticked at first, since nothing is lost but the memory. Tick anything else you want back, then click Reclaim and confirm. The confirmation names each row and what ending it means.

• Codz asks each process to stop and never forces it. Anything still running at the next sample stayed running.
• A session that is working can’t be ticked. Codz won’t end a run in progress.
• An app can’t be ticked either. Quit… asks the app to quit, and it may prompt you to save; the confirmation lists the sessions running under it, which end too.

Memory alerts

When your agents together pass 8 GB, Codz posts one notification, “Agents are holding a lot of memory”, with how much is idle enough to reclaim. It won’t notify again until the total has come back under. Turn it off with Settings ▸ Notifications ▸ Agent memory pressure.

The Agent memory row in the menu bar shows the same reading at any time: how much is in use and how much is reclaimable. The plain-text output of codz status ends with it too.

Questions

Storage says “Nothing found.” Codz reads these locations in your home folder, and macOS may be blocking it. Turn Codz on in System Settings ▸ Privacy & Security ▸ Full Disk Access, then open Storage again.

Why doesn’t Reclaim delete my transcripts? History is compacted, never deleted, because it is where your usage and run history come from.

A process is still listed after Reclaim. It didn’t stop when asked. Quit it from the app or terminal that owns it.

How often are these read? Storage measures when the page first opens and after each reclaim. Memory is sampled with usage, which Settings ▸ Data & refresh lists at 15 seconds or less.