Morning boot without six tabs
If you start the same five processes every morning, that is a product. It should not live in a sticky note and a Procfile you only remember on the studio Mac. Rig's morning boot is: open the app, start the group, read one log, fix what is red.
Terminal stays for one-off commands. iTerm is still good. The failure mode is treating tabs as state. Tabs do not survive a restart, a different machine, or an agent that needs to know which pid is Vite.
A checklist that is actually the software
- Install Rig (download, macOS 13+, Apple Silicon or Intel).
- Add the project folder. Confirm scripts or a Procfile.
- Start the main group. Skim unified logs.
- Optional: link Cursor via MCP. Optional: sign in for catalog sync.
That is also your first 10 minutes. If something fails, Setup diagnose, then Support with a diagnostics bundle — not a screenshot of six tabs.
Compared with "just a Procfile"
A Procfile starts things. It does not tell you they died. It does not own the port. It does not answer an editor. Rig vs that workflow: terminal tabs.
Free in beta. If the ritual is already muscle memory and you like it, keep it. The board is for the morning you are tired of performing.
Related
- Running local dev processes: from terminal tabs to a process manager
- Procfile validator
- Procfile guide: syntax, process types, and running it locally
- Run multiple dev servers locally: which approach fits
- Sticky notes are not a control plane
- Teleport a project between Macs
- Procfile projects
- Health-aware start order
- Processes table
- Journal