Ports, crashes, and reclaim
See who owns a port
Reclaim safely
Crashes and last exit
Agent fix loop
The classic local-dev failure mode: something still holds port 3000 from yesterday, or a process exits and the reason is buried in a terminal you closed. Rig surfaces both.
Reclaim asks Rig to stop the process holding that port. Prefer reclaiming via Rig over blind kill -9 so the right project state updates. If the owner is another app (Docker Desktop, Valet, etc.), Rig will say so — stop that service instead of force-killing randomly.
For some crashes Rig can suggest a fix path (prompt / deep link into your AI editor via MCP). Confirm what the agent will restart — MCP tools are scoped, not a raw shell.
- Open the project (or Attention / flight board) when a start fails on bind.
- Rig shows the owning process when it can — not just “EADDRINUSE”.
- Use ⌘K and search reclaim / the port number for a quick action.
- Status pills show running vs crashed.
- Last exit / crash parse surfaces a readable reason when possible.
- Restart from the same control; logs keep context across restarts.
- Native notifications are branded as Rig (not “Electron”).
port in use EADDRINUSE reclaim kill process crash exit code SIGTERM logs restart autopilot
Related guides
This article is part of the Rig knowledge base at userig.app/docs. Rig is a local-first Mac app that runs, watches, and restarts development processes with unified logs, ports, and a scoped MCP hub for AI coding agents. Your source code stays on your Mac.