Your Mac is slow. Here is why, and what is safe to end.

Blame names the app eating your memory within two minutes — a runaway editor, a browser, or what Claude Code and Cursor left behind — and ends only what is safe, in one click.

macOS 26 · Universal · notarized · 4.8 MB · Free during the beta

The Blame window on Diagnosis: 6.0 GB you can free, a Free button, memory now and after quitting Chrome, the programs safe to end, the busy ones that ask first, and Chrome to quit when you are ready.
The Blame window. Blame 0.2.1 (then named MemWatch) on the founder’s Mac, 2 Oct 2026

Finds what these leave running

  • Claude Code
  • Cursor
  • OpenAI Codex
  • Ollama
  • Docker
  • Playwright
  • Chrome DevTools MCP

On the founder’s 16 GB M3, audit of 22 Sep 2026: Claude Code’s MCP servers held 3.4 GB across 3 sessions, and Docker’s VM held 8 GB.

The cause, not a graph of memory.

Every number comes with what holds it, why, and whether it is safe to end.

Names each cause in one sentence

How long it has run, what it holds, and one button.

  • Safe ones end together with Free
  • Busy ones ask first, one at a time
  • The i shows the evidence behind each
Cause cards: serve.py left running 9 h after its window closed, 16 MB, safe; a hidden browser window, 952 MB, asks first.

Answers from the menu bar

One click on the menu bar shows what you can free, without opening the window.

  • How much you can free right now
  • Free ends only what is safe
  • The biggest holders, one button each
The menu-bar panel: 5.3 GB you can free, a Free 34 MB button, Google Chrome, a hidden browser window and serve.py.

Shows what every AI session holds

Each Claude Code, Cursor or Codex session and everything it started.

Four Claude Code sessions holding 2,373, 1,188, 1,153 and 900 MB, each with an End session button.

Shows who holds your memory

Your 16 GB as a ring, and how much comes back if you quit. Past 16 GB, memory spills to disk, and your Mac slows. Here Chrome alone held 17.3 GB, so part of it sat on disk.

  • The inner ring is each app’s memory
  • Amber is what Free can end
  • Stripes come back when you quit the app
Memory ring: Google Chrome holds 17.3 GB, 8,638 MB can come back.

Blame 0.2.1 (then named MemWatch) on the founder’s Mac, 2 Oct 2026

It ends only what is safe to end.

Before anything ends, you see what will end and what stays. You confirm; Cancel is the default.

The confirmation: two programs will end, 31 MB; Google Chrome, a hidden browser window, the AI coding sessions and a database stay running. Cancel is the default.
  • Safe — ends with FreeLeft running after its window closed and doing nothing. Checked again just before it ends: same program, same start time.
  • Busy — asks firstWorking harder than 5% CPU, so it gets its own button and its own confirmation.
  • Never — no buttonDatabases, builds, installs, parts of macOS and other users’ programs keep running. Blame only advises.

Blame 0.2.4 (then named MemWatch) on the founder’s Mac, 3 Oct 2026

It learns your Mac, then keeps it fast. It asks first.

Autopilot watches what slows your Mac, scores every choice it would make, and only acts on rules that have proven themselves.

Autopilot scores each rule against a 5% line: pausing idle apps is 22% wrong and stays off; slowing busy background work is 3% and ready in 3 days.
  1. 1
    It learns

    For a week it decides what it would pause or slow, and checks an hour later whether that was wrong.

  2. 2
    It asks

    The panel suggests one action. You press Do it, or Not this, and it learns from both.

  3. 3
    It acts, only when proven

    A rule turns on only after a week under 5% wrong, and only with your approval.

Asks first

Nothing is paused or slowed without your click.

10-minute undo

Every action can be reversed for ten minutes.

Never your work

Not the app in front of you, terminals, editors or agent sessions.

Ends alone only if you say so

Only leftovers from AI tools, only once you switch it on, and only what passes the safety check.

Swipe the chart to see all of it. Each bar is how often a rule would have been wrong: a short bar is rarely wrong, “needs more data” is still collecting choices. Blame 0.2.1 (then named MemWatch) on the founder’s Mac, 2 Oct 2026

What changed on the founder’s 16 GB Mac.

Measured by Blame itself, with the date and the log each number came from.

BeforeAfterSource
Programs left running by AI tools1129 ended, 0 survivors. The 2 left are databases, kept on purpose. Log, 27 Sep
Memory spilled to diskPast 16 GB, apps spill to the much slower disk10.9 GB7.3 GBWithin an hour of quitting Chrome. Log, 27 Sep
Alerts a day701.5184 → 4 over 63 hours of log replay, after the alert fix
History: memory spilled to disk over eight days, falling from 10.9 to 7.3 GB within an hour of quitting Google Chrome on 27 September. One hour off the scale is marked peak 22.9 GB.

Swipe the chart to see all of it. Blame 0.2.4 (then named MemWatch) on the founder’s Mac, 3 Oct 2026

Free during the beta. $29 once at 1.0.

No subscription. Nothing leaves your Mac unless you switch on anonymous usage counts.

Now

Beta

$0

Everything unlocked during the public beta

  • Diagnosis and the menu-bar number
  • One-click fixes, safety-checked
  • Autopilot suggestions
  • Agent sessions, disk clean-up, history and alerts
Download the free beta

Recommended

Blame 1.0

$29 once

At 1.0 · no subscription · no date yet

Free forever

  • Diagnosis and the menu-bar number
  • Agent sessions, disk clean-up, history and alerts

With $29 once

  • One-click fixes, safety-checked
  • Autopilot, with a 10-minute undo
Tell me when 1.0 is out

Questions

Didn’t find your answer?
Write to the founder

Will it end something I need?

Only what passes the safety check ends. Databases are never ended from a button, a child doing protected work protects its whole tree, and every fix shows its list before you confirm.

Does Autopilot act on its own?

Not unless you switch it on. It suggests, and you choose Do it or Not this; Do it can be undone for 10 minutes. The one thing you can let it do alone is end leftovers from AI tools once they pass an age you set, and only what passes the safety check. That is off until you switch it on.

Activity Monitor is free. Why this?

Activity Monitor lists every process and its memory. It does not say which session left a program running, whether it is safe to end, or what slows your Mac right now, and it force-quits one process at a time. Blame names the cause and ends the whole tree after checking it is still the same program.

Stray and Node Killer are free. Why pay?

They find orphaned processes, and so does Blame. They do not diagnose a slow Mac, show what each AI session holds, or learn with Autopilot. Diagnosis stays free at 1.0; you pay only for fixes and Autopilot.

Why not just restart?

A restart clears memory once and closes everything you had open. The leftovers come back with your next agent session. Blame ends only those, and keeps your work running.

What does it cost?

Nothing during the public beta. At 1.0, diagnosis stays free; fixes and Autopilot are $29 once. There is no subscription.

Does anything leave my Mac?

Not unless you switch on anonymous usage counts in Settings: one report a day of counts only, never a program name, a path or a command. Logs stay on your Mac for 14 days and are never sent.

How heavy is it?

About 31 MB of memory and 1% CPU — measured on the 0.2.3 release build over 43 hours, 1–3 Oct 2026.

Which Macs does it run on?

It is a universal build, tested on Apple silicon with macOS 26 Tahoe. Intel Macs and macOS 14 and 15 are not yet tested.

Why not the Mac App Store?

Its sandbox forbids signalling other processes, so Blame could not end anything. It is a direct download, signed with a Developer ID and notarized by Apple.

Find what is slowing your Mac.
Free during the beta.

Blame 0.3.0 · macOS 26 Tahoe · notarized