Forty worktrees. Twelve running.
Three you actually need.
Clueprint keeps the whole sprawl on one screen — and tells you which part is safe to let go.
Everything running, in one list
Grouped by project and branch, with live CPU and memory per stack. Click a port pill and you're on the site that worktree is serving.
Lives in your menu bar
The full picture is one click away — running counts, CPU, memory, and every stack, without opening a window.
It knows when it's not your fault
Fans spinning? Clueprint compares your worktrees against the whole machine and names the real culprits — so you stop killing dev servers that were never the problem.
Archiving moves the whole project into a sibling _archived folder — every file, including dirty work, stays intact on disk. Nothing is deleted.
Cleanup that can't hurt you
Every action re-verifies against a fresh scan. Dirty or unpushed worktrees are never removed — and abandoned projects get archived, moved aside with every file intact.
“I had fourteen dev servers running for branches I merged in March.”— every developer, eventually
Clickable port links
Jump straight to laravel.test, :5173, wherever a worktree is serving.
Agent sessions
Sees which branches still have a Claude or Codex chat attached.
Hand-off cleanup
Send a messy worktree back to your agent — CLI or app.
wp-env decoding
Those md5 container names? Mapped back to their real projects.
Menu bar readout
CPU, memory, or running count — pick your glanceable.
Archive, never delete
Abandoned projects move aside with every file intact.
Every branch, every project, every agent chat
Filter your worktrees by running, dirty, merged, abandoned — or by which ones still have a Claude or Codex session attached. Then hand the messy ones straight back to your agent.
