Process probe · native macOS
What is running on your machine right now — and since when.
See which Claude Code sessions are alive on your Mac, across every account — and it says "I don't know" instead of guessing.
Launch price · −50%Final price €58
290 licences left at the launch price
The problem
A next dev you started three hours ago, an MCP server left running since yesterday, a port held by a process you no longer recognize. Checking by hand means ps, lsof, kill — and a guess: if a process with that PID exists, you assume it's today's, even though PIDs get recycled.
A probe that can't rule out recycling and answers "alive" anyway isn't measuring anything — it's guessing, with confidence.
The verdict
The colors below are exactly the ones in the app — "unknown" carries its own color, never the one for "stale".
The process exists and procStart matches what was recorded — PID reuse is ruled out.
No process with that PID, or one with a different procStart: the PID was recycled by another process.
The process exists, but reuse can't be ruled out — no baseline, or ps couldn't be read. It never becomes a guessed "alive".
What's in the window today
Shows Claude Code sessions across every configured account on the machine, not just the default one
A ternary verdict per session — alive, stale, or unknown — never a guessed yes/no
Catches PID reuse by comparing the process's real start time to the one recorded, not just whether a process with that number exists
A menu bar icon, for a glance without opening the window
A local, append-only history of each session's identity — no account, no cloud
An MCP server that reads straight from disk and answers even with the app closed
Where the line is today
A tested mechanism is not the same thing as a shipped feature. Here is exactly where one ends and the other begins.
The "Watched targets" screen in the sidebar watches any port, command, or PID (port:3000, cmd:postgres, pid:1234) with the same ternary verdict, including a "reoccupied" event that says "port 3000 is a different process than this morning." Without a licence the screen only says the feature is paid; the Claude Code session roll call stays free, in full.
A target is checked when you add it and when you press "Scan". There is no loop yet that re-probes them on its own, in the background.
vitals-tool watch pid:<pid> / cmd:<pattern> / port:<port> returns a verdict once, on request.
Nothing in this section is a promise of port supervision as a feature of the interface — today, it isn't one.
Why you can trust it
Each describes exactly how the app behaves, including when it says “I don't know”.
Both "couldn't measure" branches in the verdict function return .unknown — not a guessed "alive" the way they did before 4 Sep 2026.
procStart is compared as a date, not a string — a fix that repaired a false "stale" verdict reported 21 days out of every 30, on days 1-9 of the month.
Account enumeration finds every configured Claude Code account on the machine, with the source of each — alias, environment variable, or orphaned directory. It also finds an account named only by a shell alias, one that has no folder on disk yet.
The MCP pod reads straight from disk, not through a socket to the app — it answers even if the Vitals window isn't open.
Because sometimes it genuinely cannot confirm whether the process running now is the one that started — no baseline, or ps couldn't be read. A guessed verdict would be more reassuring and more false. "Unknown" never turns into "stale", and it never hides as "0 sessions".
Yes, with a licence: the "Watched targets" screen watches any port, command, or PID. Targets are checked when you add them and when you press "Scan" — not yet automatically, in the background. Without a licence, the app shows Claude Code sessions, for free.
Your data stays on the Mac: the store is local, SQLite, append-only, and the MCP server reads straight from disk. The free tier makes no connection at all. With a key, the app contacts me-digital.ro at activation, at release and at launch (the key, a machine identifier and, at activation, the Mac's name), and updates are checked only when you ask.
It requires macOS 14 or later — the package's own declared requirement.
Yes. The app checks a licence, and the build you download is signed with a Developer ID and notarised by Apple — Gatekeeper accepts it on first launch, with no warning.
Status
The app is signed with a Developer ID and notarised by Apple, and it checks your licence itself. It opens on an ordinary double-click, the first time.
+ VAT, calculated at checkout for your country
290 licences left at the launch price
Open the app, select “Licence” in the sidebar, paste the key from the email and press Activate.