Build Watchers

Runaway process on your Mac? See which project started it.

Room Service lists long-running build and watch tools such as node, tsc, vite, webpack, xcodebuild, and gradle with the project they belong to, flags the ones under sustained CPU or RAM pressure, and stops them with one confirmed click.

Room Service lists long-running build and watch tools such as node, tsc, vite, webpack, xcodebuild, and gradle with the project they belong to, flags the ones under sustained CPU or RAM pressure, and stops them with one confirmed click.

Room Service lists long-running build and watch tools such as node, tsc, vite, webpack, xcodebuild, and gradle with the project they belong to, flags the ones under sustained CPU or RAM pressure, and stops them with one confirmed click.

Build Watchers in Room Service

The fan spins up, the laptop gets warm, and Activity Monitor shows node at 180 percent CPU. Or swift-frontend. There are six of them, and the only clue is a PID. One is the tsc --watch from a project you closed an hour ago. One is a Jest watcher that never settled. Which one do you kill, and which is the build you are waiting on?

Room Service answers “which runaway process on my Mac is this” with the project name. Build Watchers lists every build and watch tool started from a project folder, with how long it has run and what it is using, and marks the ones under sustained CPU or RAM pressure. One click opens the project, one confirmed click stops it.

Find the runaway process, with its project

Build tools, matched to a project. Build Watchers looks for the tools you actually run: xcodebuild, swift, swift-frontend, clang, tsc, webpack, vite, next, nuxt, rollup, esbuild, parcel, jest, vitest, tailwindcss, gradle, java, kotlinc, npm, yarn, pnpm, bun, node, cargo, go, and deno. For each one it reads the working directory and walks up to the nearest project marker (.git, package.json, Package.swift, Cargo.toml, go.mod, build.gradle, and similar). A row reads as storefront, not as node with a PID.

No port required. Dev servers that listen on a port live in Dev Ports. Build Watchers covers everything else: type checkers, bundler watchers, test runners, compilers, and Xcode or Gradle builds that never open a socket. Processes with no project behind them are left out, and so are editor and agent helpers such as MCP servers.

Pressure, measured over time. Every row carries a badge: Active for a tool running normally, High CPU or High RAM once it has been at 45 percent CPU or more (one busy core counts as 100) or holding 8 percent of your memory or more. The row shows the figure and how long the process has been observed, and flagged rows sort to the top.

It follows you. The same list lives on the Home dashboard, in the menu bar popover, in the Command Palette, as a count in the toolbar, and inside each project in the Projects workspace. Health Check reports “Build Watchers under pressure” when any row is flagged.

It tells you when to look, and when it is done. After two minutes under pressure, the Ops Feed records “Build watcher needs attention” and a macOS notification goes out, at most once every 30 minutes per watcher; the switch is in Settings > Alerts. Click the bell on a row and Room Service watches that process until it exits, then tells you how long it ran.

How to stop a stuck build process

  1. Find the row. Open Room Service, the menu bar popover, or the Command Palette and search “build watchers” or a tool name such as “tsc”. The project name and the High CPU or High RAM badge tell you which process it is.

  2. Decide. Open Project jumps to it in the Projects workspace; the Command Palette also offers Open in Terminal, Open in Finder, and Copy PID. If it is the one you need gone, click Quit Process.

  3. Confirm. Quit asks once, inline. Room Service then sends a normal stop (SIGTERM) and checks the process, four times over about a second.

  4. Done, or told why not. If the same process is still running, Room Service force quits it and checks again. If the PID now belongs to a different process, it stops and tells you instead of killing something it never showed you. A Stopped toast confirms the result.

What Quit will and will not do

  • Quit acts only on the row you clicked, by PID and process name, verifies the process is gone before it reports success, and never kills a process that took over the PID after you clicked.

  • A second click during verification does nothing; the row shows a stopping indicator.

  • Listing is read-only: nothing is stopped without a click, and macOS components and Room Service itself are never candidates.

  • Over MCP, an agent can call list_watchers (read-only) and, with “Quit processes and stop watchers” on in Settings > Agents, stop_watcher with a build: id. For an agent it sends SIGTERM only and never force quits: a survivor is reported back, and force_quit_process asks you for Allow. Agents are refused for their own process and the terminal they run in, and every agent stop lands in the Ops Feed with the agent’s name.

Free vs Pro

Seeing is free: the list everywhere it appears, Open Project, Open in Terminal, Open in Finder, Copy PID, the bell, the notifications, and list_watchers over MCP. Stopping a process needs Pro: Quit in the app and the menu bar, Quit Process in the Command Palette, and stop_watcher.

Frequently Asked Questions

Why is node using so much CPU on my Mac?

How do I find which project a runaway process belongs to?

Is Quit the same as `kill -9`?

Does it show my dev server too?

Why is a build I just started already listed as Active?

Why does my fan get loud while coding, and will this help?

Explore more of Room Service