Download

Find what slows your Mac.

Blame sits in the menu bar, names what is eating your memory, and ends only what is safe.

Download the free beta See pricing

Free during the beta. macOS 14 or later, notarized by Apple.

On one 16 GB Mac, AI tools had left 11.4 GB running.

3.4 GBClaude Code’s MCP servers, across 3 sessions
8 GBDocker’s VM
4.6 GBleft for everything else on the Mac
The founder’s 16 GB M3, audit of 22 Sep 2026. One cell is 1 GB.

Blame finds what these leave running

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

Every slowdown, named.

What holds your memory, why, and whether it is safe to end.

Names what is slowing your Mac

One bar of your memory, each cause a row, and one button: Free or Quit.

Diagnosis: 5.4 GB you can free, one bar of memory by app, then rows: a hidden browser window and Google Chrome marked safe, five AI coding sessions as a tip, postgres left alone.

Shows what every AI session holds

Each Claude Code, Cursor or Codex session, how long it has run, and End session.

Agent sessions: 5.5 GB used by five Claude Code sessions, each with its age, memory and an End session button; postgres, left running after its window closed, is left alone.

Clears what tools leave on disk

Caches, old Playwright browsers and stale build folders, moved to the Trash.

Disk: 27 GB free of 471.5 GB, and what a scan clears: caches over 50 MB, old Playwright browsers, Claude Code transcripts and build folders.

Shows what changed

Memory spilled to disk, hour by hour, with every fix marked.

History: eight days of memory spilled to disk, 9.8 to 8.5 GB within an hour of Free, with each fix marked as a dotted line.

Autopilot learns, then asks

A rule turns on only after a week under 5% wrong, and only when you approve it.

Autopilot: 12% wrong so far, still learning; each rule against the 5% line, every one switched off, and ending AI-tool leftovers on its own is off until you switch it on.

Answers from the menu bar

Its dot is green when stable, yellow when something needs attention, red when critical.

The Blame mark in the menu bar with a yellow dot and 5.3 GB.
The menu-bar panel after a fix: 5.3 GB you can free, a Free 510 MB button, and Ended serve.py and http.server, 31 MB back.

It ends only what is safe to end.

You see what will end and what stays. Cancel is the default.

  • SafeEnds with Free, after one more check.
  • BusyGets its own button and asks first.
  • NeverDatabases, builds and parts of macOS keep running.
The confirmation: End 1 program? The hidden browser window will end; Google Chrome, the AI coding sessions and postgres stay running. Cancel is the default button.

What changed on the founder’s 16 GB Mac.

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

Programs left running by AI toolsBefore: 11After: 29 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 diskBefore: 10.9 GBAfter: 7.3 GBWithin an hour of quitting Chrome. Log, 27 Sep
Alerts a dayBefore: 70After: 1.5184 → 4 over 63 hours of log replay, after the alert fix

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 about your processes leaves your Mac.

Now, everything unlocked

$0beta

  • Diagnosis and the menu-bar number
  • One-click fixes, safety-checked
  • Autopilot suggestions
Download the free beta

At 1.0, no date yet Recommended

$29once

  • Diagnosis and the menu-bar number, free forever
  • One-click fixes, safety-checked
  • Autopilot, with a 10-minute undo
See Blame Pro

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.

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. 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?

Nothing about your processes. Blame checks getblame.app for updates once a day; switch that off in Settings › About. Anonymous usage counts are sent only if you switch them on: one report a day of counts, never a program name, a path or a command. Logs stay on your Mac for 14 days and Blame never sends them. Privacy has the details.

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?

macOS 14 or later. It is a universal build, so it runs on Apple silicon and Intel Macs.

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.

Next time your Mac slows down, you’ll know why.

Blame stays in the menu bar. One click shows what is holding your memory and ends only what is safe.

Download the free beta Read the FAQ
  • Free during the beta
  • $29 once at 1.0, no subscription
  • macOS 14 or later · notarized