Tools like btop and glances show you every number and leave the diagnosis to you. I wanted the opposite: run one command and get a verdict, worst cause first. $ lagdoc lagdoc · studio · macOS 15.7.9 · up 3d 4h SLOW 2 causes found ✖ memory █████████░ 92% under heavy pressure └ Google Chrome (23 processes) 4.1 GB └ swap in use 6.2 GB ▲ disk █████████░ 94% getting full └ / 14.0 GB free of 250 GB ✓ cpu ██░░░░░░░░ 23% mostly idle ✓ network dns 12 ms → run lagdoc fix to see what can be done What it does: - **`lagdoc`**: checks memory, disk, CPU and network and gives a verdict. On macOS it uses the kernel's memory pressure, not "used RAM", which is always high there. App helper processes are counted together, so Chrome is one line, not 23. - **`lagdoc changes`**: what's different since an earlier run: new startup items, apps installed or updated, disks filling up, apps that got heavy. Slowness often starts with something new. - **`lagdoc fix`**: shows each fix and asks before doing it. It only asks apps to quit normally and runs tools' own cache cleanups (`go clean -cache`, `brew cleanup`…). It never deletes your files and never uses sudo. - **`lagdoc top` / `lagdoc watch`**: live views. `watch` records *when* each check changed, so you can see when the machine got slow. - **`lagdoc mcp`**: an MCP server, so an AI assistant (Claude Code and others) can ask lagdoc instead of guessing. It's one static Go binary for macOS, Linux and Windows. There's no daemon, no account and no telemetry. History stays on your machine. It's free and MIT-licensed. I built it with Claude Code. I set the direction and the safety rules (preview every fix, never delete files, no admin rights) and reviewed every pull request. Claude Code wrote the code and the tests. Every change went through a PR with CI on macOS, Linux and Windows. Honest limits: the macOS binaries aren't notarised yet, so the first run needs `xattr -d com.apple.quarantine`. It's also young and has mostly been tested on my own machines. Repo: https://github.com/ag3ntsc4rn/lagdoc I'd love feedback, especially from anyone whose machine is slow right now. Did the verdict match what you'd expect, and what did it miss?   submitted by   /u/_sportsfreak_ [link]   [comments]