Terminal tabs are the default way to run a local stack: one tab per server, started by hand. Rig is a desktop app that starts, watches and restarts the same processes from one window. Keep tabs for one or two servers and one-off commands; use Rig when you start five processes every day.
Last updated:
The short answer
Keep the terminal for one-off commands. Use Rig when the day is the same stack of processes and you want state, logs, ports and MCP without rebuilding the ritual every morning.
Side by side
Where the terminal wins, it says so
Swipe sideways to see Rig vs the terminal
FeatureRigTerminal tabs
Primary jobNamed projects with process controlShell sessions you manage by hand
Start the whole stackScripts and a Procfile work; status and recall do notYesPartial
Unified live logsYou can split panes; Rig merges, colours and filtersYesPartial
Restart after a crashRig retries with backoff and pauses after 5 attempts by defaultYesNo
Port ownership and reclaimIn a terminal you run lsof or netstat yourselfYesNo
MCP for Claude Code, Cursor, CodexYesNo
Remembers the stack across rebootsYesNo
Zero new appsIf you never want another window, stay in the shellNoYes
PriceFree on your computerFree
When to choose Terminal tabs
Stay with terminal tabs when the stack is small or short-lived. Two servers for an afternoon need nothing more than two tabs: there is nothing to install, nothing to configure, and every command behaves exactly as you typed it. Tabs are also the right place for one-off work such as migrations, package installs, test runs and git, and Rig does not try to replace them for that. If you like building your own setup, tmux with a layout script, or a Procfile runner, gives you detach and attach, named windows and a single start command while staying entirely in the terminal. Developers who prefer the keyboard and dislike desktop apps on principle lose nothing by staying there. The cost only shows up when the same stack is rebuilt by hand every day.
When to choose Rig
Choose Rig when you rebuild the same stack every morning. Rig reads your package.json scripts, a Procfile and a Compose file, gives each process a name, and starts a project group in a health-aware order. One merged log keeps every line, coloured by process, across restarts. When something dies, Rig can restart it with exponential backoff, freeing a stuck port first, and the attention board shows crash loops and failed health checks. Port ownership is visible, so EADDRINUSE becomes a one-click fix instead of an lsof hunt. The local MCP hub lets Claude Code, Cursor or Codex read the same logs and restart one process with scoped tools. Your terminal stays for everything else, and Rig is free on your computer.
Choose Rig if
You restart the same five processes every morning
You lose track of which tab owns which port
You want agents on live project state without pasting logs
Stay with the terminal if
Your work is mostly one-off commands
You only ever run one or two servers
You are happy scripting everything yourself
Fair. Rig is for the stack you repeat every day, not every shell session.
Running both
The terminal keeps
git, installs and migrationsOne-off scripts and test runsAnything you run once and forget
Rig takes
The dev servers and workers you start every dayMerged logs, ports and restarts after a crashMCP so your coding agent sees the same processes
Rig does not replace your shell. It takes the long-running processes off your tabs, so the terminal goes back to being a place for commands.
Questions
Do I stop using the terminal with Rig?
No. Keep it for git, installs, migrations and one-off commands. Rig is for the long-running processes you start every day.
What happens when a process crashes in Rig?
Rig can restart it with exponential backoff, capped at 30 seconds, and by default pauses after 5 attempts. It frees an EADDRINUSE port before restarting.
Is tmux a good alternative?
Yes, for a terminal-first workflow. tmux gives you detach and attach and a scripted layout; Rig adds merged logs, port reclaim, health checks and MCP in a window.
Trade tabs for one window
Free forever on your computer. Your terminal stays for everything else.