Reference
Performance
See what is using your Mac’s memory and CPU, reclaim what idle agents hold, and stop what you no longer need without losing your history.
Agents start sessions, helpers, dev servers and builds, and a busy afternoon leaves a lot running. The Performance page shows what your Mac is going through and what is responsible: every process, grouped by what it belongs to, with the memory and CPU it uses. It is also where your agents’ memory is, and where you hand it back. Codz never stops anything without your confirmation, and never forces a process to quit.
Open Performance
Open Performance from the account menu under your name, or press ⌘0. ⌃⌘P opens it too. The page has four tabs, Overview, Processes, Automation and Activity, and ⌃Tab moves between them.
The switch at the top right shows This Mac or your Codz Cloud workspace. Codz Cloud’s readings appear while the workspace is awake, and nothing there can be stopped from the Mac.
The Performance row in the menu bar and the agent memory notification open the page at the place they are about.
Overview
The top of the page says in one sentence what the Mac is going through, such as memory pressure, heat or a busy CPU, and which process is most responsible. Below it, four numbers:
| Number | What it shows |
|---|---|
| CPU | The share of the whole Mac in use, and how many of its cores are busy |
| Memory | Memory in use, macOS’s memory pressure (Normal, Warning or Critical), and swap |
| GPU | How busy the GPU is, where macOS reports it |
| Reclaimable | What your idle agent processes hold, which you can get back from Processes |
Resources draws CPU, memory in use and GPU over the last 15 minutes, hour or 24 hours. Each point is an average with the range around it shaded, and a gap means Codz wasn’t reading, for example while the Mac slept. The Pressure and Thermal lanes above the chart mark when memory was under pressure or the Mac ran hot. Click a series in the legend to hide it, and point at the chart for the values at a moment.
Needs attention lists what Codz noticed, most serious first: memory pressure, a process that keeps growing, one that has used a lot of CPU for a while, helpers whose session has ended, idle agents holding memory, and heat. Each comes with what you can do about it, such as Show, Stop… or Reclaim….
Agents’ memory shows what your agent sessions, their helpers and Codz’s own chats hold, by provider, beside how much memory the Mac has, and how much of it you could reclaim. Review opens Processes on the rows you could reclaim.
Top memory and Top CPU list the five biggest of each. Click one to open it in Processes.
What “memory” means here
A process’s memory is its footprint, the figure Activity Monitor shows in its Memory column. It counts compressed memory the process still owns, so your agents’ total can be more than what macOS calls in use, and Codz states it beside the memory your Mac has rather than as a share of it.
Processes
Every workload on the Mac gets one row: a dev server together with its workers, an app with its helpers, an agent session, a build. Each row says what it is, its project, who started it (Codz, an agent, you outside Codz, or macOS), how many processes it has, how long it has been running and its ports. The columns show its memory and the last ten minutes of it, how much it grew over the last hour, its CPU as a share of the Mac with the cores it uses, and its status, such as Working, Idle 12 min or Orphaned.
- Search finds a name, project, port or process ID, and ⌘F jumps to it.
- The filters show All, Agents, Dev servers, Builds, Models, Apps, macOS or Other, and Reclaimable narrows any of them to what you could reclaim.
- Click a column heading to sort by it. Rows hold still while the pointer is over the list, so the one you are reaching for doesn’t move away.
- Click a row, or press Return, to open its details beside the list: its memory and CPU over the last hour, its process IDs, ports, project, who started it and what stopping it would lose, with Copy PID and Activity Monitor.
| Key | Action |
|---|---|
| ↑ / ↓ | Move between rows |
| Space | Tick or untick a row you can reclaim |
| Return or ⌘I | Open the row’s details |
| ⌫ | Stop… the row |
| ⌘A | Tick every row you can reclaim |
| Esc | Close the details, then clear the ticks |
Stop or quit a process
Stop… is in a row’s … menu, in its details and on a finding. Codz asks first, and the confirmation says what you would lose:
- A process you started, such as a dev server: Codz asks it to stop. Anything it hasn’t saved is lost; start it again from its project.
- An app: Quit… asks the app to quit, and it may ask you to save first. The agent sessions it launched end too, and the confirmation names them.
- A Codz chat: End Chat Process… ends the process behind the chat. The chat stays in your sidebar with its history, and its next message starts a new process.
- An agent session started outside Codz: Codz asks it to stop. Its transcript is on disk, and the row says how to resume it, such as
claude --resume <id>.
Codz never forces a process to quit. One that ignores the request keeps running, and the page says so.
Some rows can’t be stopped here, and say why: Codz itself, parts of macOS, anything that is working (a session in the middle of a turn, and what runs under it), terminal shells (close their window or tab), the helpers of a Codz chat (end the chat’s process instead), work Codz started from the Run panel (stop it there), and anything you have protected.
Reclaim your agents’ memory
The Agents filter shows what your agents hold: their sessions, the helpers and MCP servers they started, and Codz’s own chats. A row you could end without interrupting anything has a checkbox: sessions, helpers and chats that aren’t working.
Orphaned helpers, whose session has ended, are ticked as they appear, since nothing is lost but the memory. Untick one and it stays unticked. Tick what else you want back, then click Reclaim in the bar at the bottom and confirm. The confirmation lists each row and what ending it means, and leaves out any that started working since you ticked them.
A provider’s desktop app can’t be ticked; Quit… it instead.
Protect a process
Protect from Automatic Actions in a row’s … menu, or Protect in its details, keeps rules and Reclaim away from it. Only something that keeps its identity when it restarts can be protected: an app, a Codz chat, an agent session and its helpers, or a server or model Codz runs. A protection on something not seen for 90 days lapses.
Automation
Rules let Codz act on its own when the Mac needs headroom. Each reads as a sentence, with a switch and what it is doing now: Watching, Active · holding 2 requests, Cooling down · 3 min or Off.
Four come with Codz, all off at first. They hold new background work while memory is under pressure, while the Mac runs hot, while the CPU is above 85% for 30 seconds, or while the GPU is above 90% for 30 seconds. Holding means new background agent turns, builds and dev-server starts wait; whatever you start yourself, and whatever is already running, carries on. Held work starts once things have been back to normal for 30 seconds.
Templates add the idle clean-ups: unload a model Codz started when it’s idle, stop an idle dev server Codz started, and stop an orphaned helper. They act only on work Codz started and can verify, only when it is idle, and wait between actions on the same one.
New rule… opens an editor that builds the same sentence and offers only choices that make sense together. The pencil on a rule edits it, and the bin deletes it after asking.
AI assistance
Off unless you turn it on, and rules never need it. Explain findings with AI adds an explanation of what Codz noticed to Needs attention, using your OpenRouter account within a daily budget you choose. Only sizes and counts are sent, never the names, paths or commands of your processes.
Activity
Activity is a timeline, a day at a time: what you stopped or quit and how much it released, what rules did, and stretches of memory pressure or heat. Filter it to Your actions, Automatic or Pressure & thermal. When a rule stopped a model or server that Codz can start again, its entry has Restore.
Agent memory alerts
When your agents’ own processes, their sessions, helpers and Codz’s chats but not their desktop apps, pass the size set in Settings ▸ Notifications ▸ Alert at (8 GB at first), Codz posts one notification, “Agents are holding a lot of memory”, with how much of it is idle enough to reclaim. Click it to open Processes with those rows ticked. It won’t notify again until the total has come back under 90% of that size. Turn it off with Settings ▸ Notifications ▸ Agent memory.
The plain-text output of codz status ends with your agents’ memory too.
Questions
Why is my agents’ memory more than what is in use? A footprint counts compressed memory a process still owns, which macOS doesn’t count as in use. Activity Monitor’s Memory column shows the same figure.
Why can’t I tick a session? It is working. Codz won’t end a run in progress.
A process is still listed after Stop. It didn’t stop when asked. Quit it from the app or terminal that owns it.
How often does Codz read the Mac? Every second while Performance is open, every 5 seconds while a rule is on, and every 15 seconds otherwise. Settings ▸ Data & refresh lists it with the other collectors.