Why I built WorkerDock.

Too many tabs

At Webtions I build sites and apps on Cloudflare: Workers, Pages, Astro, EmDash, with D1 and R2 behind them. Locally, every one of those projects is a wrangler dev process in its own terminal tab, holding its own port.

With three or four projects open, I kept asking the same questions. Which port was that one on? Is it still running? Which database does it write to? Answering them meant clicking through tabs and opening config files.

Processes that outlive their tab

The worse problem was what happened after. Close the tab, or end an AI agent session, and the workerd process behind a project can keep running. It holds the port, uses memory and fails the next start with "address already in use". Cloudflare's own issue tracker has reports of it.

One window

So I built the tool I wanted: a native Mac app that scans your folders, lists every Wrangler, Pages, Astro and EmDash project, and shows each one's status, port, logs and bindings. Stop a project and its workerd process stops with it.

I made it read-only toward your project folders and kept it on your machine. It does not upload your code or data, and variable values are never displayed. It is free to download.

What comes next

The first version covers the everyday loop: find, start, stop, read logs, check bindings. Local D1 migrations and a .dev.vars editor are planned, and a few other ideas are on the roadmap. If something is missing, tell me on X.