Kossé ? Québécois for “what’s that?”
Every dev server on your Mac, traced to its repo.
You start dev servers from terminals, scripts and coding agents. A day later a dozen ports are taken, some by worktrees you forgot. Kossé sits in your menu bar and lists them by repo, worktree and branch. Nothing to register, and no change to how you start things.
brew install davidpp/tap/kossev0.3.1, macOS on Apple siliconOpen source on GitHub
What’s on :5175?
Search a port, inspect a service, stop one.
main~/code/storefront- Storefront APIKossé profile
nodeapps/api- HTTP 404
- details
:9229Inspector HTTP 400
up 2h 14mcpu 0.4%mem 96 MB
- node
apps/web- HTTP 200 · Storefront
up 2h 14mcpu 3.1%mem 182 MB
checkout-redesignworktreeof storefront…/worktrees/storefront-checkout- node
apps/web- HTTP 200 · Storefront
up 3d 2hcpu 0.0%mem 141 MB
main~/code/wiki- postgres
:5432not probed: non-HTTP port
up 40mcpu 0.1%mem 38 MB
- wiki
server- HTTP 200 · Wiki
up 40mcpu 0.2%mem 24 MB
What you get
Start things the way you do
Kossé reads every TCP listener on your Mac and the process behind it, every three seconds. A server an agent started three days ago shows up like the one you started this morning.
Two worktrees stay two projects
It walks from the process’s working directory up to its repo or worktree and reads the branch. Same repo, same package, two checkouts: two cards.
It says what it saw
A 404 is still a server that answered. A database is listening, not broken. Kossé reports the observation and leaves the verdict to you.
One link to open per service
Each service leads with the URL you’d open. Inspectors and internal ports stay on a quiet details line, and a database gets no Open link at all.
Stop exactly one process
It checks the PID and its start time again right before the signal, asks for a graceful stop first, and tells you what happened next. Forcing takes a second confirmation.
Nothing leaves your Mac
The dashboard answers on loopback only and refuses requests from other websites. Secret-looking values in command lines are hidden before anything shows them. No telemetry, no update checks.
Your coding agent can ask, too
One kosse call answers what runs in this worktree, on which port, and whether it’s up. No more lsof, ps and curl loops.
- It waits instead of sleeping
kosse wait --port 5173 --httpreturns once the server answers.- It can’t stop by name
kosse stop websignals nothing. It prints the command that would: the process identity and every port it holds.- It names your services
- Customize hands your agent a prompt. It reads the repo, then names each service and endpoint in Kossé’s own config. Your repository stays untouched.
kosse url 5173
http://localhost:5173/
kosse stop 3000
kosse: port or PID 3000 matches 1 process; stop takes the identity <pid>.<start> and --ports with every port it listens on, so nothing was signalled. To confirm one:
# node, /Users/sam/code/storefront
kosse stop 4907.1794571320 --ports 3000,9229
kosse agent skill --write ~/.claude/skillsHow it’s built
One Rust process scans, serves and draws the menu. Every view reads the same snapshot, and every stop goes through the same policy.
- Menu-bar menu
- Dashboard
- kosse list
Snapshot
Scannersockets · processes · git · profiles
- Binary
- One self-contained executable with the dashboard built in. No Bun or Node at runtime.
- Scan
- Every 3 seconds: listeners, the process behind each, its repo, worktree, branch and package, CPU and memory.
- Probes
- One bounded
GETevery 15 seconds, to loopback endpoints of your own project processes only. - Dashboard
- A web UI kept within 55 kB gzipped, in its own native window or any browser at
127.0.0.1:47831. - Footprint
- About 0.1% CPU and 12 MB of private memory with the window closed, measured on an M4 Pro.
- Tests
- Against real processes, the real server and real browsers. The tests only signal processes they started.
Questions
- Does it start or manage my servers?
- No. It only looks. It doesn’t start, restart, wrap or supervise anything, and it never cleans up on its own.
- Could it stop the wrong process?
- It’s built not to. You confirm the process and every port it holds, and Kossé checks the PID and start time again right before the signal. It never signals a parent, a process group, another user’s process or itself.
- Do I have to set up my projects?
- No. Projects come from each process’s working directory. A profile is optional, for friendlier names and links.
- Does anything leave my Mac?
- No. There’s no telemetry, no update check and no remote asset. Kossé never writes into your repositories either.
- Is it signed?
- No. It isn’t signed or notarized yet, so install it from the terminal: macOS refuses a copy downloaded with a browser.
- Does it run on Intel Macs, Linux or Windows?
- No. macOS on Apple silicon only.
Ask your Mac what’s running
Install it, run it, and the K in your menu bar has the answer.
- Install it with Homebrew.
brew install davidpp/tap/kosse kosseThe menu-bar app starts and the dashboard opens.kosse startup enableStart it at each login, if you want it always there.
Needs macOS on Apple silicon. No Homebrew? Use the installer script
Next
- A terminal UI,
kosse tui, with everything the dashboard does. - Hiding the listeners you never want to see.
- A signed and notarized build.