Why this exists
I kept losing track of the things I'd started.
A dev server here, a database there, a tunnel for some experiment
— half of them still running days later, none of them stopped, all
of them quietly using CPU and battery I didn't have to spare.
macOS doesn't tell you about this. Activity Monitor will list the
processes if you go looking, but it won't connect
node to the dev server I started last week.
The problem got worse when I started building with AI coding tools
— Cursor, Claude Code, VS Code, the whole crowd. They're great at
spinning up dev servers; they're not always great at stopping the
previous one before starting the next. Sometimes the agent is
smart enough to free the port it needs — sometimes it just walks
to the next available one. After a few hours of iteration you can
end up with six copies of the same Vite server competing for
memory, the laptop running hot, the battery draining fast, and
nothing in macOS surfacing any of it.
You know roughly what you run — you just lose track of what's
still running. The fan spins up, the battery drops, and nothing in
macOS connects it back to that dev server, worker, or model you
started days ago and forgot about.
Switchboard is the thing I wanted: one place where every local
service shows up, every forgotten process gets surfaced, every
port flood gets named with its actual cause, and every AI tool I
use can read the local context before it acts. The OS won't tell
you. The AI tools won't ask. This will.
Switchboard is built by Abdullah Alzuwayed, an independent
developer. I keep it local-first because it is the tool I wanted
on my own Mac. You can verify the builder on
LinkedIn.