I built a Chrome extension that shows which Git branch is serving each localhost port

지권 — Sat, 26 Sep 2026 12:33:16 +0000

I often run several Git worktrees at once, each with its own dev server. After a while, localhost:3000, 3001, and 5173 all look the same, and more than once I tested a fix in the wrong tab.

So I built Branchport, a Chrome extension that tells you which worktree and branch is behind every localhost page.

What it does

A label on every localhost page with the repo, worktree, and branch. Red means main, orange means uncommitted changes, blue means a feature branch.
Branch names in tab titles, and optional tab groups per worktree.
A popup with every local dev server: port, PID, uptime, CPU, and memory. Open a server in your editor, terminal, or file manager, or stop it safely.
A warning when the same worktree is running on more than one port.

How it works

A Chrome extension can't see local processes, so Branchport comes with a small helper that runs on 127.0.0.1:

It finds which process is listening on each port.
It reads that process's working directory.
It asks Git for the repo, branch, and status of that directory.

The helper only answers requests from the extension, and nothing leaves your machine. It works on macOS, Linux, and Windows.

Try it

Add Branchport from the Chrome Web Store.
Install the helper once:

npx branchport install

It's free and MIT licensed. The code is on GitHub.

If you juggle multiple worktrees or run several AI coding agents in parallel, I'd love to hear what you think.

DEV Community: 지권

I built a Chrome extension that shows which Git branch is serving each localhost port

What it does

How it works

Try it