Your dev servers and open ports, by project.

Vitals shows what is running on your Mac by the project it came from, and every port in use with what holds it and who can reach it. The dev server you forgot on Tuesday is pointed out, with what stopping it frees. Nothing stops until you say so.

Memory by Type
82%
in use
App 22.15 GB
Wired 5.67 GB
Compressed 24.54 GB
Cached 10.32 GB
Free 1.32 GB
Memory by App
59.25 GB
all apps
Google Chrome 21.23 GB
VS Code 8.17 GB
Terminal 3.86 GB
Safari 2.69 GB
Other 23.30 GB
Power by App
1.7 W
all apps
GitHub Desktop 427 mW
Google Chrome 367 mW
Zoom 145 mW
Terminal 86 mW
Other 650 mW
Now
27 %
Average today36%
Load3.41
User
19%
Your apps
System
8%
macOS
Cores
12
8 P4 E
Top App
Google Chrome
18.2%
AppCPU
Google Chrome
96 processes
–
Terminal
49 processes
–
Safari
16 processes
–
Docker
9 processes
–
Visual Studio Code
63 processes
–
Slack
13 processes
–
Figma
14 processes
–
Zoom
8 processes
–
In use of 64 GB
52.63 GB
Normal
Free11.37 GB
Swap0 MB
App
23.43 GB
Wired
5.37 GB
Compressed
23.82 GB
Top App
Google Chrome
20.59 GB
AppMemory
Google Chrome
96 processes
–
Visual Studio Code
63 processes
–
Terminal
49 processes
–
Safari
16 processes
–
Docker
9 processes
–
Slack
13 processes
–
Figma
14 processes
–
Zoom
8 processes
–
Free of 994.66 GB
479.72 GB
Used514.94 GB
Written today38.9 GB
Reading
737 kB/s
Writing
195 kB/s
Volumes
2
Macintosh HDBackup
Top App
Photos
121 kB/s
AppWriting
Photos
6 processes
–
Google Chrome
96 processes
–
Docker
9 processes
–
Visual Studio Code
63 processes
–
Xcode
22 processes
–
Mail
4 processes
–
Slack
13 processes
–
Music
5 processes
–
Downloading
12 kB/s
Today4.4 GB
Last 30 days212 GB
Uploading
419 kB/s
Last 7 Days
48.3 GB
Interface
Wi-Fi
en0
Top App
Safari
8 kB/s
AppDownloading
Safari
16 processes
–
Google Chrome
96 processes
–
Slack
13 processes
–
Zoom
8 processes
–
Music
5 processes
–
Mail
4 processes
–
Docker
9 processes
–
Notion
6 processes
–
Apple M2 Max
60 %
Average32%
Peak95%
Memory
1.69 GB
Average
32%
Peak
95%
Top App
Figma
35%
AppGPU
Figma
14 processes
–
Google Chrome
96 processes
–
Safari
16 processes
–
Zoom
8 processes
–
Visual Studio Code
63 processes
–
Xcode
22 processes
–
Slack
13 processes
–
Notion
6 processes
–
16-core Neural Engine
2 %
Average3%
Peak16%
Memory Traffic
79.9 MB/s
Average
3%
Peak
16%
Top App
Photos
3 connections
AppNeural Engine
Photos
6 processes
–
Xcode
22 processes
–
Safari
16 processes
–
Zoom
8 processes
–
Mail
4 processes
–
Notion
6 processes
–
Google Chrome
96 processes
–
On battery
64 %
Remaining2h 46m
Cycles412
Power Draw
12.6 W
Health
76%
Temperature
31°
Top App
Google Chrome
4.3 W
AppPower
Google Chrome
96 processes
–
Zoom
8 processes
–
Figma
14 processes
–
Slack
13 processes
–
Safari
16 processes
–
Visual Studio Code
63 processes
–
Docker
9 processes
–
Music
5 processes
–
CPU
54°
GPU
47°
Hottest
58°
Fan
1,200rpm
Curve
Fans
Fan
Follows the CPU
1,200rpm
FollowsCPU
Full speed6.4k1.2k40°60°80°100°54°
Rules
Quiet on BatteryThe fans follow Quiet while the Mac runs on battery.
Cool While Apps Work HardWhen one of these apps keeps the Mac busy, the fans follow Cool until it has been quiet for a minute. Add App
XcodeNot running
Set every two seconds while Vitals is open Full speed above 95 °C Given back when Vitals quits
Working the Hardest
XcodeCPU 51.4%
8 Sensors
CPU Performance Core54°
CPU Efficiency Core49°
GPU47°
SSD41°
Wi-Fi39°
Battery33°
Airflow Left31°
Airflow Right32°
Last 24 Hours CPU Hottest
80°40°
6 PM12 AM6 AM12 PM
Fastest Fan
6k2k
6 PM12 AM6 AM12 PM
Output
MacBook Pro Speakers
64%
AppStatusVolumeLevel
Music Playing 100%
Zoom Playing 80%
Google Chrome Playing 35%
Slack Silent Muted
Safari Silent 100%
Figma Silent 100%
Notion Silent 100%
Mail Silent 100%
3 connected
Lowest battery: AirPods Pro, left, 42%. Beats Fit Pro is paired but away.
42% Bluetooth Settings
DeviceKindBatteryLevel
AirPods Pro Headphones
Left 42%
Right 58%
Case 80%
Magic Trackpad Trackpad 67%
Magic Keyboard Keyboard 91%
11projects running
Memory
3.25GB
most in storefront
CPU
41.3%
across every project
Processes
30
servers, watchers, editors
Open Ports
10
300043214322+7
4 dev servers are running but idle
Stopping them frees 1.37 GB and ports 3000, 4321, 4322, 8000.
Stop All…
storefront
Claude · 9 processes
working
1.18 GB
storefront-web
Terminal · node
4322 up 3 days, barely used
458 MB
scraper-api
Codex · python
8000 up 4 days, barely used
412 MB
marketing-site
Visual Studio Code · node
4321 idle 2 hours
296 MB
billing-api
Terminal · node
30009229 idle 45 min
204 MB
docs
Cursor · node
5173
188 MB
ml-notebooks
Terminal · python
8888
164 MB
design-tokens
Visual Studio Code · node
6006 idle 20 min
121 MB
infra
Terminal · 3 processes
96 MB
auth-service
Terminal · go
8080
74 MB
email-templates
Cursor · node
3030 idle 3 hours
58 MB
0%
Claude
This week
On pace · 10% to spare
0%
Codex
5-hour session
Resets in 3h 12m
0%
GitHub Copilot
Premium requests
Runs out in 4d at this rate
0%
Cursor
This billing cycle
Resets in 12d 5h
Checkout flow tests Working Waiting for you
Claude Code · storefront · running 48 min
410 MB
Started · 4 Quit Session…
vitest command · 61% CPU 520 MB
node server · port 3,001 240 MB
Google Chrome for Testing browser 310 MB
mcp-server-fetch tool server 64 MB
Codex idle 48 min
docs · in Terminal · Nothing started
290 MB

The numbers are simulated: a web page cannot read your Mac, and should not.

01Projects

Grouped by the folder it runs in, not by the command.

Three things called node become storefront, api and docs. Everything started from a project folder is one row, named after the folder, with the app that started it, its memory and CPU, and every port it listens on.

  • One row per project, named after its folder
  • The app that started it: Terminal, Cursor, Claude
  • Memory and CPU for the whole project
  • Compose containers under their project too
storefront1.8 GB · 41%
next dev:3000412 MB
postgres:5432 · container1.4 GB
api96 MB · 0%Idle 3 daysStop
uvicorn:808096 MB
docs210 MB · 2%
astro dev:4321210 MB
Named by its folder Every port, beside its process
02Ports

What is on port 3000, without a terminal.

Ports lists every port in use on the Mac, sorted by whose it is: your projects, idle dev servers, containers, Homebrew services, then other apps and macOS. Press ⌘F, type 3000, and the process holding it is named, with Quit beside it. No lsof, no kill.

  • Every listening port, grouped by whose it is
  • ⌘F a number and it is found
  • Open in Browser, or Quit, on each row
  • How long each has been running
3000⌘F
:3000next devstorefrontYoursStop
:5432postgresstorefrontA container
:7000ControlCentermacOSThe system's
The port, the process, the project Whose it is
03Network

Which ports your network can reach.

Each port says who can connect: only this Mac, or other devices on your network. The ones open to the network are counted at the top, so a dev server that anyone on a café's Wi-Fi could reach is easy to spot.

  • Only this Mac, or open to the network
  • Open ports counted at the top
  • macOS's own named: AirPlay Receiver, Screen Sharing
  • An iPhone on a cable told apart from the network
32ports in use4 open to your network
pythonscraper-api:8000Network
nodestorefront-web:4322This Mac
postgresql@17Homebrew:5432This Mac
ControlCentermacOS’s AirPlay Receiver:5000 :7000Network
Who can connect The open ones, counted
04Idle

The server you forgot, pointed out with how long.

A dev server that has done nothing for days carries a note saying how long, and an offer to stop it with what that frees: the memory and the port. Stop one, stop them all, or quit a whole project. Vitals asks first.

  • Idle for days, pointed out
  • What stopping frees: memory and ports
  • Stop one, or Stop All
  • Quit a whole project at once
Stop api?
uvicorn on :8080 has done nothing for 3 days. Stopping it frees 96 MB.
KeepStop
Idle for days, pointed out Nothing stops until you say
05Dropdown

Check a project or a port from the menu bar.

The dropdown has the same Developer tab, with Projects, Ports and Containers. An idle dev server carries a moon and how long, the ports open to your network come first, and a click opens the window on that section.

  • Projects, Ports and Containers in the dropdown
  • A moon on an idle server, with how long
  • Ports open to your network come first
  • A click opens it in the window
OverviewCPUMemoryDeveloperAgents
ProjectsPortsContainers
storefrontTerminal:3000
apiCursoridle 3 d:8080
docsClaude:4321
A click from the menu bar A click opens it in the window
Why it matters

Dev servers and ports, before and after

Every project leaves things running. A dev server from Tuesday, a database you forgot was local, a test watcher in a tab you closed. In Activity Monitor they are a dozen rows called node and python, and the port each one holds is not shown at all; for that you open a terminal, type lsof -i :3000, and kill a number.

So the second project on port 3000 fails to start, the Mac is warm for no reason you can name, and the fix is a guess.

Vitals' Developer tab answers both. Projects groups what is running by the folder it runs in, with the memory, CPU and ports of each. Ports lists every port in use, with what holds it and whether your network can reach it. The dev server that has done nothing for days is pointed out and offered to stop, and Vitals asks before anything closes.

How to use it

Where it is in Vitals

The tab, the menu bar item and the setting, in the order you would reach for them.

  1. 01

    Open the Developer tab

    Projects is its first section: one row per project, named after its folder, with its memory, CPU and ports. Open a row to see each process.

  2. 02

    Find what is on a port

    Choose Ports, press ⌘F and type the number. The process holding it is named, with its project.

  3. 03

    Check what your network can reach

    Each port says whether only this Mac can connect or other devices can. The number open to your network is at the top.

  4. 04

    Stop the forgotten one

    An idle server says how long it has done nothing. Stop it, quit its whole project, or Force Quit one process that will not answer. Vitals asks first and says what will close.

  5. 05

    Ask from your assistant

    Over MCP: what is on port 8080, which projects have a dev server going. For a project folder you trust, safe requests can be quit without asking; add the folder in Settings → Integrations.

Compared

Dev servers and ports: Activity Monitor and Vitals

The whole comparison is row by row. These are the rows about dev servers and ports.

Activity Monitor Vitals
By project
Activity MonitorNo
VitalsGrouped by the folder they run in
Ports
Activity MonitorNot shown; lsof in Terminal
VitalsEvery port in use, beside the process that holds it
Who can connect
Activity MonitorNot shown
VitalsOnly this Mac, or open to your network
Idle servers
Activity MonitorNothing
VitalsPointed out, with how long
Stopping
Activity Monitorkill by number
VitalsStop, or quit the whole project, after a confirmation
Containers
Activity MonitorProcesses only
VitalsCompose containers under their project

The words behind it

What the numbers mean, from the Activity Monitor glossary.

Questions

The ones people ask about dev servers and ports before they buy.

How does Vitals know which project a process belongs to?

By the folder it was started from. Processes started from the same project folder are grouped under it, with the folder's name.

Will Vitals stop a dev server by itself?

No. It points out the ones that have been idle for days and offers to stop them. Nothing stops until you confirm.

Does it show ports held by apps that are not mine?

Yes. The Ports section lists every listening port on the Mac: your projects' first, then idle dev servers, containers, Homebrew services, and other apps and macOS's own. The system's are named in plain words, such as macOS's AirPlay Receiver on 5000 and 7000.

Can other devices on my network reach my dev server?

The Ports section says so for every port: only this Mac can connect, or other devices on your network can. Ports open to the network are counted at the top and marked, so a server listening on every address is easy to spot.

Does it work with Docker?

Yes. Containers are a section of the same Developer tab, with their ports. A container started by docker compose from a project folder shows under that project too, and its published ports are in the Ports section.

What counts as a project?

The folder a process was started from. Everything started from the same folder is one project, named after it.

Can I quit a whole project at once?

Yes. Quit the project and every process in it closes, after a confirmation. Force Quit is there for one that will not answer.

Why does my port say it is already in use?

Another process is listening on it, usually a server from an earlier session. The Ports section names it, with the project it belongs to, and offers to quit it.

Read on

Guides that use this, and how Vitals compares with the apps people buy for it.

More of Vitals

All features

Lifetime for $19 while the launch price lasts

at this price. Then $49, or $12 for a year of updates. One payment, 14-day refund.

Get Vitals for $19