Introducing Vitals for developers: ports, open files and Homebrew 🧑‍💻

Vitals 1.11 is out. The Projects tab is now a Developer tab, with five sections along the top: Projects, Ports, Open Files, Containers, and Homebrew.

A day of work leaves a lot running. Dev servers from three projects, a database Homebrew started at login, the tool servers a coding agent brought up and never closed. Each holds a port and some memory, and most are called node or python. The Developer tab says what each one is and where it came from.

Ports

Every port something on your Mac is listening on, with what holds it: one of your projects, an app, a Homebrew service or macOS. Each row says who can reach it, only this Mac or other devices on your network. Open in Browser and Quit are on each row, and a dev server left idle is pointed out.

Open Files

macOS says a disk is in use and not by what. Open Files shows every disk with the apps that have files open on it. Click Eject on a disk that is in use, and Vitals names the apps it would quit and asks first. Say yes, and it quits them the way ⌘Q does and ejects the disk.

Homebrew

Every package with its size and when it last ran. Not Seen Running lists the ones you installed and never used. Updates, Clean Up, and every service with Start, Stop and Restart. Vitals runs a brew command only when you click one.

Also in 1.11

- Each project names the app that started it, such as Terminal or Codex

- A coding agent's command that has done nothing for ten minutes is marked stuck, with Quit beside it

- Terminal windows idle for an hour are listed, with End on each

- Memory Report, a folder for an app's developer with its memory over time

- Export on every tab

- vitals ports, vitals files and vitals homebrew in Terminal, and the same answers for Claude, Codex and Cursor

The update is free for everyone who has Vitals. It's $29 once for one Mac, with a 3-day free trial.

https://vitalsmac.com/changelog/1.11

What would you want the Developer tab to show next?