tidewake

Your coding agents leave things running. tidewake finds them, with proof.

Claude Code and Codex start servers, browsers, test runners and git worktrees. When a session ends or crashes, some of it keeps eating RAM and disk. tidewake shows you what, which session left it, and the exact command to clean it up. It never deletes anything itself.

_{From user reports: claude-code#11315, codex#12491, claude-code#17391. The last tile is one tidewake scan on the author's Mac.}

Install

brew install --cask berkkorkmaz/tap/tidewake        # macOS

On Linux, grab the .deb, .rpm, .apk or .tar.gz from releases, or go install github.com/berkkorkmaz/tidewake/cmd/tidewake@latest.

tidewake scan        # what agents left behind, and how to clean it
tidewake sessions    # live sessions: memory, CPU, which one is stuck
tidewake doctor      # known leaks in your Claude Code / Codex version

One scan, 30.5 GB

Proof on every row

leftover claude b7ec50d0   pid 77162   5d   tail -n +1 -f /private/tmp/claude-501/…/b4.output
         why:  runs in session b7ec50d0's scratch directory; no running Claude Code session has
               this id; no Claude Code process above it (parent: launchd)
         run:  kill -TERM 77162

Safe by design

• Never deletes. It prints commands; you decide.
• Won't guess. Anything serving a port, like a database, gets a note instead of a command.
• Protects your work. A worktree is kept if it has uncommitted changes, unpushed or reflog-only commits, or ignored files like .env. On one Mac it kept 24 that way.
• Stays local. No network, no telemetry, and no iCloud downloads triggered.

Every rule is in how it works.

Roadmap

tidewake clean with preview and undo · a context audit of what loads before you type

MIT licensed. macOS and Linux, on Apple Silicon/arm64 and Intel/amd64.