Reference
Storage & memory
See what Claude, Codex, Cursor and OpenCode keep on your disk and hold in memory, and reclaim it without losing your history.
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 Performance page what they are holding in memory 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 ⌘2. 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:
| Kind | What it is | Reclaim | Ticked at first |
|---|---|---|---|
| Rebuildable | Caches, logs, shell snapshots and abandoned worktrees | Deletes it; the tool rebuilds it when it needs it | Yes |
| Generated | Images you generated with Codex | Deletes it, and nothing can re-create it | No |
| History | Transcripts and databases, including the usage Codz reads | Compacts Claude Code’s and Codex’s transcripts; never deletes | No |
| Installed | Plugins and extensions | Nothing. They are listed so the totals add up and can’t be ticked. | No |
These are the locations Codz knows about. It reads only these places in your home folder and leaves anything else to Finder:
| Provider | Rebuildable | Generated | History | Installed |
|---|---|---|---|---|
| Claude | Simulator builds, Desktop app cache, Desktop code cache, Shell snapshots, Telemetry spool | Session transcripts | Plugins | |
| Codex | Debug log database, Log database rotations, Cache, Shell snapshots, Abandoned worktrees | Generated images | Rollout transcripts | Plugins |
| Cursor | Cached data, Logs, Web cache, Abandoned worktrees | Workspace state database | Extensions | |
| OpenCode | Logs | Message database |
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
- Open Storage (⌘2).
- Tick the locations you want to reclaim, and untick any you want to keep.
- If you ticked a transcript, click Measure ledgers and wait for the estimate.
- Click Reclaim, which shows the total, and read the confirmation. It lists what will be deleted and what will be compacted.
- 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
What your agents hold in memory is on the Performance page: press ⌃⌘P, or click Performance in the menu bar. Its Agents filter lists your agent sessions, the helpers and MCP servers they started, and Codz’s own chats, with what each holds. Tick the idle ones and click Reclaim to get the memory back; each says what ending it means, and orphaned helpers, whose session has ended, start ticked. See Reclaim your agents’ memory.
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.
How often are these read? Storage measures when the page first opens and after each reclaim. Performance reads memory every second while its page is open, and every 15 seconds otherwise.