Skip to main content
Create and manage runtimes (sandboxes) with the gravixlayer CLI (grx symlink included).

Install

macOS / Linux

Installs to ~/.local/bin by default and adds it to your PATH when needed. Pin a version:

Windows (PowerShell)

Verify

Authenticate

Paste your API key from the console. The CLI verifies it, then stores it in your OS keychain for the active profile.

Profiles

Config lives at ~/.gravixlayer/config.toml. Each profile has its own defaults and keyring entry (so you can keep staging and production separate).
Set per-profile defaults:
Show config (API keys are redacted):
gravixlayer doctor prints the active profile, config path, base URL, and whether a key is in the keyring.

Create and use a sandbox

gravixlayer runtime create defaults to template base-small, cloud aws, region us-east-1. Pass --template, or set default_cloud / default_region on the profile, only when you want something else.
Output formats: --output table (default), --output json, or --output quiet.
You can also set GRAVIXLAYER_OUTPUT=json.

Background commands

Start a process and re-attach later by pid:
See Background commands.

Snapshots

See Snapshots.

Fork

Branch a running runtime — or a saved snapshot — into independent copies:
See Fork.

Files

Update

Or re-run the install script:

Uninstall

Windows (PowerShell):

What’s next

SDK Usage

Same sandbox workflows in Python

Create Runtime

Templates, cloud, region, and attach options

Quickstart

End-to-end SDK walkthrough