Process probe · native macOS

Vitals

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

€29+ VAT at checkoutLicence agreement

290 licences left at the launch price

sessions probed now
claude · sessionpid + procStart matchalive
cron · watcherPID reused sincestale
mcp-serverps unreadableunknown
claude · sessionpid + procStart matchalive
scroll

The problem

Guessing with confidence isn't a measurement

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

Three states, never a boolean

The colors below are exactly the ones in the app — "unknown" carries its own color, never the one for "stale".

Alive

The process exists and procStart matches what was recorded — PID reuse is ruled out.

Stale

No process with that PID, or one with a different procStart: the PID was recycled by another process.

Unknown

The process exists, but reuse can't be ruled out — no baseline, or ps couldn't be read. It never becomes a guessed "alive".

// screens

The app's screens

Each Claude Code session gets a verdict, Alive, Stale or Unknown, never a simple yes or no.
Vitals shows every Claude Code session on your Mac from each account it can find: the default one, any ~/.claude-* folder, and any shell alias that sets a config directory.
It compares the real start time of the process with the one it recorded, so a recycled PID shows up as Stale.
When it cannot rule out PID reuse, Vitals says Unknown instead of guessing Alive.
// screen tour

What each screen shows

  1. 01 / 04

    One account's sessions, each with its verdict

    • Every session gets one of three verdicts: alive (green dot), stale (grey circled x) or unknown (orange question mark).
    • Next to the verdict is the method that produced it, such as “kill(pid,0) + procStart”, so you can see how sure it is.
    • When a verdict is not a confirmed alive, the card states the cause in orange: a recycled PID, with both times, or a missing baseline.
    • Identity history stays: a renamed session shows its old name and the rename, with the same reference.
  2. 02 / 04

    Every account, at a glance

    • The sidebar lists every Claude Code account found on the Mac, with its session count; the default one is marked “default”.
    • An account that is configured but has no folder on disk yet shows up too, as “no directory” and “configured, never used”.
    • The overview also says what the list does not cover: a config directory not named “.claude-*” shows up only if CLAUDE_CONFIG_DIR or a shell alias names it.
    • The same sidebar holds “Licence” and “Watched targets”, the screen that watches any port, command or PID and needs a licence.
  3. 03 / 04

    A reused PID, caught by its start time

    • Vitals compares the start time recorded for the session (procStart) with the one ps -o lstart reports now.
    • Here the times differ: the PID has been taken by another process, so the session is marked stale, with both times in the diagnostic.
    • The times are compared as moments, not as text: that is how a false stale verdict on days 1-9 of the month was fixed.
  4. 04 / 04

    When it can't confirm, it says unknown

    • The process exists, but the session has no recorded start time, so PID reuse cannot be ruled out.
    • The verdict is unknown, in its own colour, orange: not a guessed alive, and not stale either.
    • The diagnostic says why: no baseline, or ps could not be read.

What's in the window today

Six things the app actually does

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

What's tested, and what's in the window

A tested mechanism is not the same thing as a shipped feature. Here is exactly where one ends and the other begins.

The generic target is in the window, as a paid screen

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.

Targets are scanned on request

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.

Also from the CLI, one shot

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

Four things you can rely on

Each describes exactly how the app behaves, including when it says “I don't know”.

"Unknown" is a real verdict, not just an icon

Both "couldn't measure" branches in the verdict function return .unknown — not a guessed "alive" the way they did before 4 Sep 2026.

PID reuse, caught at the source

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.

Not just the default account

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.

An MCP server that answers with the app closed

The MCP pod reads straight from disk, not through a socket to the app — it answers even if the Vitals window isn't open.

Requirements

System
macOS 14.0 or later
Network
None in the free tier; with a key, only the licence (and updates, on request) — the store is local, SQLite
Account
None — it reads the Claude Code accounts already configured

Questions

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

Available to buy

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.

Swift 6SwiftUISQLiteMCP (stdio)
Launch price · −50%Final price €58
€29

+ VAT, calculated at checkout for your country

290 licences left at the launch price

Licence agreement

Activation

How to activate your licence

Download the app

Download version 1.1.1

2.9 MB

Open the app, select “Licence” in the sidebar, paste the key from the email and press Activate.