Named sessions
Named sessions let you park one working context and boot another — useful when you juggle client A vs client B without leaving a dozen processes half-alive.
Switch sessions
- Save or name your current session when prompted / from the session switcher.
- Switch to another session — Rig stops the outgoing stack and starts the incoming one (including DBs when configured).
- Confirm logs and ports for the new context before you keep coding.
From an AI agent
Agents connected over MCP can call list_sessions to see your named sessions and the last saved one, resume_session to bring back what was running, and switch_session to move to a named session. Resume and switch start and stop servers, so they wait for you to click Approve in Rig before anything runs.
Tips
- Pair sessions with project groups so a switch boots the whole stack.
- Use lanes (branch · env · port) when the same repo needs two contexts.
- Restore last session on launch from Settings if you always resume yesterday’s work.