Bytes per interface per day, kept 90 days.
Live demo — click the tabs, the menu bar, or Clean up. Demo data.
Stat Space
The menu bar monitor for people who build things.
CPU, memory, network and sensors with 30 days of history, a volume slider for every app, and the answers you actually need: what’s on :3000 and who started it, what your AI agent left running, how much of your Claude Code limit is left, and why your Mac won’t sleep.
500+ developers downloaded
and trust Stat Space
Apple Silicon· macOS 14 Sonoma+· Free forever, no account
What’s on :3000? Who started it?
Every listening port, traced to its project folder and whatever launched it: a terminal, your editor, an AI agent, launchd or Docker. Servers reachable from your network get flagged by name, with what that means and a one-click fix.
- Process node · next dev pid 48211 · 640 MB
- Project acme-web ~/code/acme-web · Next.js 15
- Shell zsh pid 48190
- Launcher Claude Code session ended 6m ago left behind
- Process node · prisma studio pid 48377 · 210 MB
- Project acme-web ~/code/acme-web · Next.js 15
- Shell zsh pid 48190
- Launcher Claude Code session ended 6m ago left behind
- Process node · vite pid 51022 · 188 MB
- Project docs-site ~/code/docs-site · Vite 6
- Shell zsh pid 50998
- Launcher Terminal window 2, tab 1
- Process com.docker.backend pid 1882
- Container db image postgres:16 Pro
- Runtime OrbStack mapped 5432 → 5432
- Launcher Docker running 3d
http-server is open to your network. :8080 is listening on every interface, so other devices on your network can connect. Bind it to 127.0.0.1 to keep it on this Mac, or stop it from Needs attention.
- Process node · http-server pid 60417 · 54 MB
- Project demo ~/code/demo
- Shell zsh pid 60380
- Launcher Cursor integrated terminal
$ statspace ports PORT PROCESS PROJECT PID LAUNCHER UPTIME BIND :3000 next dev acme-web 48211 Claude Code 41m 127.0.0.1 :5173 vite docs-site 51022 Terminal 2h 127.0.0.1 :5432 postgres:16 db 1882 Docker 3d 127.0.0.1 :8080 http-server demo 60417 Cursor 6m 0.0.0.0 exposed 1 port is reachable from your network (bound to 0.0.0.0 or a LAN address). $ statspace kill 3000 Stop next dev (pid 48211) on :3000? [y/N] y Stopped next dev.
Your agent finished. Its servers didn’t.
Stat Space watches Claude Code, Codex and Cursor sessions: runtime, CPU, child processes and the ports they open. When a session ends, whatever it left running shows up, ready to clean up in one tap.
Your agent can ask too. statspace --mcp gives Claude Code, Codex and Cursor tools for ports, load, sessions and cleanup.
$ claude mcp add --scope user statspace -- \
/Applications/StatSpace.app/Contents/Helpers/statspace --mcp Know before you hit the limit.
How much of your Claude Code and Codex limits is left, per 5-hour and weekly window, when each resets, and whether you’re on pace. One line of it sits on the pinned Agents card too.
Off until you turn it on in Settings › Agents. Codex is read from its local session logs. Claude Code uses Anthropic’s usage endpoint with Claude Code’s own sign-in; the token stays in memory and is never stored or refreshed by Stat Space. It only refreshes while the Agents tab or card is on screen.
One row per app. Every process, on request.
Chrome’s twenty renderers count as Chrome. Helpers, XPC services and Electron renderers roll up into the app that owns them, so “what is using my memory?” has a one-line answer.
- Process inspector. Expand any process for its code signature and signer, Team ID, notarization, hardened runtime, sandbox, notable entitlements, Rosetta, parent, and its open files and sockets.
- A page per app. Live usage with 2-minute trends, every process with its launcher and project, network peers, ports, sleep assertions and 7-day totals.
- Quit, force-quit, and “not responding”. A banner when an app hangs, and “idle but heavy” apps you haven’t touched in an hour.
- Team ID
- EQHXZ8M8AV
- Parent
- Google Chrome (pid 812)
- Arch
- arm64
- CPU time
- 41m 12s
- Threads
- 19
socket · unix → Google Chromepipe ×6~/Library/Application Support/Google/Chrome/Default/… - Team ID
- EQHXZ8M8AV
- Parent
- Google Chrome (pid 812)
- Arch
- arm64
- CPU time
- 18m 03s
- Threads
- 27
IOSurface ×38socket · unix → Google Chromepipe ×4 - Team ID
- —
- Parent
- zsh (pid 48190) ← Terminal
- Arch
- arm64
- CPU time
- 2m 47s
- Threads
- 11
TCP 127.0.0.1:3000 · listening~/code/acme-web/.next/cache/…pipe ×3 Click a process to inspect it · demo data
A volume slider for every app.
Turn the meeting up and the music down without touching either app. Every app playing sound gets its own slider, 0 to 150 %, plus mute. No audio driver to install.
- Remembered per app. Set Slack to 40 % once and it stays there across launches. Mute all but one, or play an app through another output.
- “Mic in use by Zoom.” See which app has the microphone, read from Core Audio with no permission prompt.
- Devices and levels. Output and input pickers, master volume and balance, and live level meters you can turn on.
- Asks only when needed. Built on Core Audio process taps (macOS 14.2+). The System Audio Recording permission is requested the first time you move a slider, never just for opening the tab.
What happened while you weren’t looking.
Per-minute averages of CPU, memory, pressure, swap, paging, GPU, temperatures, fans, power, clocks, network and disk, kept for 30 days on your Mac. Every chart switches between 2 minutes, 1 hour, 24 hours, 7 days and 30 days.
Opt-in: one ping every 10 s, charted and kept in history. A VPN chip appears when a tunnel carries your traffic.
Average cluster and GPU clocks, plus page-ins/outs and swap-ins/outs per second.
Costs less than what it measures.
A monitor that shows up in its own top-apps list has failed. The menu bar is drawn with Core Graphics, the popover’s UI exists only while it’s open, and the sampling loop doesn’t allocate. Thirty days of history costs one wakeup a minute.
The budget on an M1 at 1 s sampling with the popover closed. A benchmark checks it on every build, and a regression doesn’t ship.
Samplers run only for what you can see: a menu bar item, an open tab, a pinned card, or an active rule. Everything else sleeps.
Its own CPU and memory sit in the popover footer, always. If it ever costs too much, you’ll be the first to know.
Everything Stats has. Plus what it doesn’t.
All the system stats you’d expect, free. Then the tools you’d otherwise open Activity Monitor, Terminal or three other apps for. See how it compares with Stats and iStat Menus →
Every metric, free
CPU with performance and efficiency cores, GPU, memory pressure and swap, disk, network, temperatures, voltages, power in watts for CPU, GPU and Neural Engine, fans, battery and a world clock. Everything Stats does, at no cost.
A Devices tab
Bluetooth with battery levels, the USB tree with speeds and bus power, Thunderbolt, what each port is doing, the charger’s negotiated watts, displays, audio devices and drives. Optional connect and disconnect notifications.
Battery, honestly
Live charge and power flow, a 24-hour and 7-day level chart, real capacity against design, cycles, condition, and energy by app right now.
Fan curves
Read fan speeds, set them by hand, or let a temperature curve drive them from the CPU, GPU or hottest sensor, with 3 °C of hysteresis so they don’t hunt. Control uses a small helper installed only when you turn it on.
Keep awake, with a reason
Timers, plus “until the download ends”, “while on the charger” and “until this task exits”. And a list of whatever else is holding your Mac awake.
A network toolkit
Speed test with a live chart, ping, traceroute and DNS lookup, Wi-Fi link details, a captive-portal check, and the devices on your network.
Disk, and developer junk
Usage per volume with eject (and who’s blocking it), read/write speed, top apps by I/O, SSD health, a large-folder scan, and rebuildable caches, deleted only when you confirm.
Shortcuts & backup
Global shortcuts for the popover or any tab, set to whatever keys you like. Export every preference to a file and import it later; your license and history stay out of it.
A Home you pin
Pin any tile or card (CPU cores, top apps, ports, agents, sensors, world clock) to Home, in your order. Samplers run only for what’s pinned or visible.
Alerts & widgets
Notifications when CPU, memory, disk, battery or temperature cross a line for longer than you allow, and desktop widgets for the main modules.
$ statspace ports :3000 next dev · acme-web $ statspace kill 3000 CLI + MCP, free
A statspace command and an MCP server over a local socket, so you and your agents can ask what’s running and clean up.
Free forever. Pro is one-time.
Free is everything above, no account, no trial. Pro is a single purchase for the questions no other monitor answers. Same deal as Lofi Space: no subscription, ever.
$0 · forever
- Every system metric, with 30 days of history
- A themeable menu bar, desktop widgets and global shortcuts
- Apps grouped, process inspector, ports traced, exposed-port warnings
- Agent watch, leftovers, orphan cleanup and Claude Code / Codex usage limits
- Per-app volume, a Devices tab, and fan curves
- Keep-awake timers and “why won’t it sleep”
- Speed test, ping, latency, data usage, storage cleanup
- A Mac health report you can send IT, with hands-on tests
-
statspaceCLI and MCP server for your agents
$9.99 · one-time
Only 30 left at the launch price, then $14.99 for good
70 of 100 launch licenses claimed
- Network by app: upload and download per app
- Keep-awake rules: while an app or port runs, the network is busy, on AC, on a schedule
- Docker mapping: ports to container and image
- “Why is my Mac slow?” in one tap, in plain English
- Trends: your busiest hours, hottest moments, memory pressure and data use, in plain words
- Spike rewind: the top 3 processes behind every spike
- Battery drain since unplug, per app
- App alerts and who’s phoning home
Powered by Polar · license key, no account · refundable within 14 days
For a team? $8 a seat, 5 seats minimum. One checkout and one invoice to expense; each person gets their own key. Stat Space for teams →
Rather build it yourself?
Get the whole prompt behind Stat Space and point your agent at it. Pay $9.99 for the app, or pay $4.99 and spend your weekend.
- About 25,000 words, ready to paste into Claude Code, Codex or Cursor.
- Every feature, the architecture, and the design tokens for the popover and menu bar.
- The hard parts already solved: recipes for per-app network, power, sensors, listening ports and the private frameworks, plus a gotcha index.
- Ship it, too: a phased build plan and a release checklist for signing, notarization and Sparkle updates.
- One-time, free updates. Your key opens the always-current prompt at
statspace.app/prompt.
- # Build your own Stat Space
- 0How to use this prompt
- 1Role and goal
- 2Non-negotiables · idle < 0.3% CPU, < 25 MB
- 3Architecture · scheduler, snapshot, ring buffers
- 4Feature spec · every tab
- 5Design tokens
- 6Recipes · per-app network, power, sensors, ports
- 7Phased build plan
- 8Release checklist · sign, notarize, Sparkle
- +Gotcha index
Quick answers.
Is Stat Space really free?
Yes. Every system metric with 30 days of history, the themeable menu bar and desktop widgets, app grouping and the process inspector, ports, agent watch and usage limits, orphan cleanup, per-app volume, the Devices tab, fan curves, keep-awake timers, the network and storage tools, and the CLI + MCP server are free forever. Pro is a one-time purchase ($9.99 for the first 100 buyers, only 30 of those left, then $14.99) for per-app network, keep-awake rules, Docker mapping and the rest. No subscription, no account.
Which Macs does it run on?
Apple Silicon Macs (M1 and later) on macOS 14 Sonoma or newer. It ships as an arm64-only binary: the sensors, power and per-core readings it uses are Apple Silicon specific. Intel Macs, macOS 12–13 and languages other than English aren’t supported yet. If you need one of them, email [email protected]: requests decide what comes next.
Why do I see several Stat Space icons in my menu bar?
Each stat gets its own menu bar item (CPU, memory, network, ports and so on), so one copy of the app can show several. If you use a menu bar manager like Ice or Bartender and it doesn’t have Screen Recording permission, it shows the app icon in place of each item’s graph, so they all look the same. Grant it the permission, or pick which items to show in Settings › Menu Bar. A Combined item can put several readings in one. If Activity Monitor shows two Stat Space processes, you’ve opened it from the disk image as well: quit both, eject the disk image and open it from Applications.
Can I hide the parts I don’t use?
Yes. In Settings › Tabs, untick any tab you don’t need (Volume, Awake, Time, …) and drag the rest into your order. Settings › Menu Bar picks which items sit in the menu bar. Hidden things cost nothing: Stat Space only samples what’s on screen or what an alert or rule needs.
Is Stat Space safe to install?
Yes. It’s signed with an Apple Developer ID, notarized by Apple and built with the hardened runtime, and updates are signature-checked before they install. It runs as you with no root access (only the opt-in fan helper needs it), has no analytics, and only stops your own processes after you confirm. statspace.app/security lists everything it can access and every network request it makes, plus how to verify your copy.
Why isn’t it on the Mac App Store?
Per-process stats, sensors, power and per-app network all need APIs the App Store sandbox doesn’t allow. Stat Space is a direct download, signed and notarized by Apple, and updates itself with Sparkle.
How does per-app volume work without a driver?
It uses Core Audio process taps, which Apple added in macOS 14.2, so there’s no audio driver or kernel extension to install. A tap runs only for an app whose volume isn’t 100 %, is muted or is routed elsewhere, and only while it plays. macOS asks for System Audio Recording permission the first time you move a slider, and shows its purple recording dot while a tap is active.
Which coding agents does it see?
Claude Code wherever it runs: in a terminal, in your editor, or in the Claude desktop app’s Code tab. Also Codex, Cursor, Aider, Gemini CLI and opencode. For each session you get its runtime, CPU, child processes and the ports it opened, and what it left running after it ended. Claude Code sessions also show status (including “Needs you”), context, burn rate and cost.
How do the Claude Code and Codex usage limits work?
They’re off until you turn them on in Settings › Agents. Codex limits are read from its own session logs on your Mac. For Claude Code, Stat Space asks Anthropic’s usage endpoint at most every 5 minutes using the sign-in Claude Code already stored in your Keychain, read the same way Claude Code reads it, so there’s no Keychain prompt. It’s read only when you open the Agents tab, never from Home or the menu bar. The token is kept in memory only, never written to disk or logged, and never refreshed by Stat Space. Nothing refreshes unless the Agents tab or the pinned Agents card is on screen. If the sign-in can’t be read, it says so and offers Try again; there’s no need to run claude in a terminal first.
What about ports held by root, like a launchd daemon?
Turn on Settings › General › System ports and the Ports tab gets a System section. Press Load, enter your password once, and Stat Space runs a read-only lsof to list listeners owned by root and other system users. It's a snapshot that never refreshes on its own, so there's no background cost. Apple's processes are view-only. A third-party launch daemon gets a Stop button that names exactly what happens, asks for your password and runs launchctl bootout; it never kills a root process directly or touches the plist.
Does keeping 30 days of history cost anything?
Very little. History is a per-minute average written to a local SQLite file, so it costs one wakeup a minute and never changes how often the live readouts sample. It stays on your Mac and is left out of settings exports.
Could a cleanup kill something important?
No. Orphan cleanup only looks at developer tools (node, python, vite, tsc and friends) that were left running after their terminal or agent session ended. It never touches system processes, and it always shows you the list and asks before stopping anything.
How do I connect it to Claude Code, Codex or Cursor?
Settings → CLI & MCP shows a ready-to-paste snippet for each. For Claude Code it’s one line: claude mcp add --scope user statspace -- /Applications/StatSpace.app/Contents/Helpers/statspace --mcp. Destructive tools like kill_port still ask before acting.
Does it send my data anywhere?
The app has no analytics and no account. It makes a few network requests of its own: your public IP from statspace.app, only when you tap Look up in the Network tab, license checks with Polar if you buy Pro, and the Sparkle update feed. Weather, while you use it, sends coordinates rounded to about 5 km to statspace.app, which asks Apple Weather. A speed test talks to Apple’s servers, and only when you start one. If you turn them on, the latency monitor pings a host every 10 seconds (1.1.1.1 unless you pick another) and Claude Code usage limits are read from Anthropic.
How do refunds work?
Purchases go through Polar, which offers a 14-day refund window. Email [email protected] and we'll sort it out.
Know what your Mac is doing, without adding to it.
Free, no account. Pro is $9.99 once, and only 30 launch-price licenses are left before it goes to $14.99.




