| title | Quickstart |
|---|---|
| description | Launch your first workspace and install your first app with production-safe CLI steps |
This guide walks you through creating a workspace, installing an app recipe onto it, and validating live routing — all with the rig CLI.
- A Rigbox account (sign up here)
- The Rigbox CLI installed:
curl -fsSL https://rigbox.dev/install.sh | bash
The CLI opens your browser to sign in and stores credentials locally, so the rest of these commands need no tokens or headers.
rig loginrig workspace spawn creates the workspace, boots it, and waits until it's ready — all in one call. The dev template is a general-purpose development image with Node.js, Python, and common build tools. Replace my-project with a name of your choice.
rig workspace spawn --name my-project --template devThe built-in templates are base (minimal) and dev (full toolchain). Everything else — VS Code, Jupyter, Firecrawl, and so on — is installed as an app recipe on top of a workspace, which is the next step.
App recipes are pre-packaged applications you install into a workspace with a single command. Official recipes are addressed as @rigbox/<id>@builtin. Install the VS Code Server recipe:
rig recipe app install -r @rigbox/vscode@builtin -w my-projectThe install blocks until the app is live, then prints its name and URL. The app is served at https://<APP_NAME>.rigbox.dev — here, https://my-project-vscode.rigbox.dev.
List the apps in your workspace:
rig app ls --workspace my-projectCheck a specific app is reachable before surfacing its URL in your own UI:
rig app health --app <APP_NAME>Expected output:
{
"live": true,
"service_status": "running",
"port_open": true
}For workspaces with AI integration, set the AI mode:
rig workspace ai mode --workspace my-project managedProvider and model are account-level defaults — set them once with rig ai defaults:
rig ai defaults --provider google --model google/gemini-2.5-pro