CLI Commands Reference
Complete reference for all sprite CLI commands.
Authentication Commands
Section titled “Authentication Commands”sprite login
Section titled “sprite login”sprite login - Authenticate with Fly.io
sprite login [flags] [api-url]Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite-h, --help- Show this help message
Examples:
sprite loginsprite login -o my-orgsprite login https://custom-api.sprites.devRelated Commands:sprite auth --help Non-interactive token setup (CI/CD)sprite org --help Manage organizations and tokens after loginsprite logout
Section titled “sprite logout”sprite logout - Remove Sprites configuration
sprite logout [flags]Options:
-h, --help- Show this help message
Examples:
sprite logoutsprite org auth
Section titled “sprite org auth”sprite org auth - Add an API token
sprite org auth [-o <api>:<org>] [api-url|alias]Aliases: sprite orgs, sprite organizations, sprite o
Options:
-o, --org <name>- Specify organization-h, --help- Show this help message
Examples:
sprite org auth # Use default APIsprite org auth https://custom-api.sprites.dev # Custom API URLsprite org auth prod # Use 'prod' aliassprite org auth -o myorg # Specific organizationsprite org auth -o prod:my-org # Alias with org overridesprite org auth https://staging-api.sprites.dev -o staging:test-orgsprite org list
Section titled “sprite org list”sprite org list - Show configured tokens
sprite org list [api-url|alias]Options:
-h, --help- Show this help message
sprite org logout
Section titled “sprite org logout”sprite org logout - Remove all tokens
sprite org logout [flags]Options:
--force- Skip confirmation prompt-h, --help- Show this help message
sprite org keyring disable
Section titled “sprite org keyring disable”sprite org keyring disable - Disable keyring usage
sprite org keyring disableOptions:
-h, --help- Show this help message
Examples:
sprite org keyring disablesprite org keyring enable
Section titled “sprite org keyring enable”sprite org keyring enable - Enable keyring usage
sprite org keyring enableOptions:
-h, --help- Show this help message
sprite auth setup
Section titled “sprite auth setup”sprite auth setup - Set up authentication using a pre-generated token.
sprite auth setup --token <token>Options:
--token <token>- Token in format: org-slug/org-id/token-id/token-value-h, --help- Show this help message
Examples:
sprite auth setup --token "org-slug/org-id/token-id/token-value"Sprite Management
Section titled “Sprite Management”sprite create
Section titled “sprite create”sprite create - Create a new sprite
sprite create [flags] [sprite-name]Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite--skip-console- Exit after creating instead of connecting to console--label <label>- Label to apply to the sprite (can be repeated)-h, --help- Show this help message
Creates a new sprite with the specified name. The sprite will be created in the selected organization. If sprite name is not provided, you will be prompted. Lifecycle:
- Sprites pause when idle (no HTTP requests and no active sessions)
- Services keep sprites alive and auto-restart on boot
- Use checkpoints to save and restore filesystem state Related Commands: sprite list —help List your sprites sprite destroy —help Delete a sprite permanently sprite console —help Open an interactive shell
Examples:
sprite create my-spritesprite create -o myorg development-spritesprite createsprite use
Section titled “sprite use”sprite use - Activate a sprite for the current directory
sprite use [flags] [sprite-name]Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite--unset- Remove the .sprite file from current directory-h, --help- Show this help message
Creates a .sprite file in the current directory to set the active sprite. This file will be used by other commands when no sprite is explicitly specified. Similar to ‘nvm use’ or ‘asdf local’ for version management. If no sprite name is provided, shows an interactive list to choose from.
Examples:
sprite use my-spritesprite use -o myorg dev-spritesprite usesprite list
Section titled “sprite list”sprite list - List all sprites
sprite list [flags]Aliases: sprite ls
Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite-w, --watch- Watch for live updates--prefix <prefix>- Filter sprites by name prefix-h, --help- Show this help message
Lists all sprites in the selected organization. Use —prefix to filter sprites by name prefix.
Examples:
sprite listsprite list -o myorgsprite list --prefix devsprite destroy
Section titled “sprite destroy”sprite destroy - Destroy a sprite
sprite destroy [flags] [sprite-name]Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite--force- Skip confirmation prompt-h, --help- Show this help message
Examples:
sprite destroy myspritesprite destroy -o myorg myspritesprite destroy -s myspritesprite destroy --force mysprite # Skip confirmationRelated Commands:sprite create --help Create a new spritesprite checkpoint --help Save state before destroyingCommand Execution
Section titled “Command Execution”sprite exec
Section titled “sprite exec”sprite exec - Execute a command in the sprite environment
sprite exec [flags] -- <command> [args...]Aliases: sprite x
Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite--dir <path>- Working directory for command--tty- Allocate pseudo-TTY--env <vars>- Environment variables (KEY=value,KEY2=value2)--http-post- Use HTTP/1.1 POST instead of WebSockets (non-TTY only)--no-port-forward- Disable automatic local port forwarding for ports opened by the command--file <source:dest>- Upload file before exec (repeatable)-h, --help- Show this help message
When using —tty, terminal environment variables (TERM, COLORTERM, LANG, LC_ALL) are automatically passed through from your local environment. Use ‘sprite sessions’ to list, attach to, or kill running sessions.
Examples:
sprite exec -- ls -lasprite exec --dir /app -- echo hello worldsprite exec --env KEY=value,FOO=bar -- envsprite exec --tty -- /bin/bashsprite exec -o myorg -s mysprite -- npm startsprite console
Section titled “sprite console”sprite console - Open an interactive shell in the sprite environment
sprite console [flags]Aliases: sprite c
Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite--no-port-forward- Disable automatic local port forwarding for ports opened by the console-h, --help- Show this help message
Opens an interactive shell with a TTY allocated. Uses shell environment variables to determine which shell to use. Supported shells: bash, zsh, fish, tcsh, ksh. Falls back to bash if shell detection fails. Detach with Ctrl+\ to leave the session running in the background. Related Commands: sprite exec —help Run a command without an interactive shell sprite attach —help Reconnect to a detached session sprite sessions —help List and manage running sessions
Examples:
sprite consolesprite console -o myorg -s myspriteCheckpoints
Section titled “Checkpoints”sprite checkpoint create
Section titled “sprite checkpoint create”sprite checkpoint create - Create a new checkpoint
sprite checkpoint create [flags]Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite--comment <text>- Optional comment describing this checkpoint-h, --help- Show this help message
sprite checkpoint list
Section titled “sprite checkpoint list”sprite checkpoint list - List all checkpoints
sprite checkpoint list [flags]Aliases: sprite checkpoint ls, sprite checkpoints ls
Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite--history <version>- Filter by history version--include-auto- Include auto-generated checkpoints-h, --help- Show this help message
sprite checkpoint info
Section titled “sprite checkpoint info”sprite checkpoint info - Show information about a specific checkpoint
sprite checkpoint info [flags] <version-id>Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite-h, --help- Show this help message
Examples:
sprite checkpoint info v2 # Show details for checkpoint v2sprite checkpoint delete
Section titled “sprite checkpoint delete”sprite checkpoint delete - Delete a checkpoint
sprite checkpoint delete [flags] <version-id>Aliases: sprite checkpoint rm
Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite-h, --help- Show this help message
Examples:
sprite checkpoint delete v3 # Delete checkpoint v3sprite restore
Section titled “sprite restore”sprite restore - Restore from a checkpoint version
sprite restore [flags] <version-id>Aliases: sprite checkpoint restore
Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite-h, --help- Show this help message
Examples:
sprite restore v1sprite restore -o myorg -s mysprite v2# Safe restore workflowsprite checkpoint create --comment "before rollback"sprite restore v1See also:sprite checkpoint --help Full checkpoint documentationNetworking
Section titled “Networking”sprite proxy
Section titled “sprite proxy”sprite proxy - Forward local ports through the remote server proxy
sprite proxy [flags] <port1> [port2] ... or <local1:remote1> [local2:remote2] ...sprite proxy --sshOptions:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite-W, --stdio <[host]:port>- Forward stdin and stdout to host:port on the Sprite--ssh- Emulate an SSH session with a Sprite over stdio, for use as an ssh ProxyCommand.-h, --help- Show this help message
Each port will be forwarded from localhost to the remote environment. Use LOCAL:REMOTE syntax to map different local and remote ports. Multiple ports can be specified to forward multiple services simultaneously. If a port was auto-forwarded by a running
sprite exec, stop that command or rerun it with--no-port-forwardbefore using the same local port here. Related Commands: sprite url —help Manage the sprite’s always-on HTTP URL
Examples:
sprite proxy 8080sprite proxy 3000 8080sprite proxy 4005:4000sprite proxy 3001:3000 8081:8080sprite proxy -W :22sprite proxy -o myorg -s mysprite 8080sprite proxy --ssh -s myspritesprite url
Section titled “sprite url”sprite url - Manage sprite URL settings
sprite url Show sprite URL and auth settingsprite url update [flags] Update URL authentication settingsOptions:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite-h, --help- Show this help message--auth <type>- Authentication type: ‘public’ or ‘sprite’
Examples:
sprite url # Show current URL and auth settingsprite url update --auth public # Make URL publicly accessiblesprite url update --auth sprite # Require org membership (default)sprite url -o myorg -s mysprite # Show URL for specific spriteAccessing Authenticated URLs:Visit the URL in your browser and log in with Fly.io, or use an org token:curl -H "Authorization: Bearer $SPRITE_API_TOKEN" https://mysprite-myorg.sprites.app/Security Notes:- Public URLs are accessible to anyone on the internet- Never expose secrets, env vars, or sensitive data via HTTP- Use 'public' only for demos, webhooks, or truly public servicessprite url update
Section titled “sprite url update”sprite url update - Update URL authentication settings
sprite url update --auth <type> [flags]Options:
-o, --org <name>- Specify organization-s, --sprite <name>- Specify sprite-a, --auth <type>- Authentication type: ‘public’ or ‘sprite’-h, --help- Show this help message
Examples:
sprite url update --auth public # Make URL publicly accessiblesprite url update --auth sprite # Require org membership (default)sprite url update --auth public -s demo # Make specific sprite publicUtility Commands
Section titled “Utility Commands”sprite api
Section titled “sprite api”Error: api requires a path argument
sprite api [flags] <path> -- [curl options]sprite upgrade
Section titled “sprite upgrade”sprite upgrade - Upgrade the sprite client to the latest version
sprite upgrade [flags]Options:
--check- Check for updates without installing--force- Force upgrade even if already up to date--version <version>- Upgrade to a specific version--channel <channel>- Release channel (release, rc, dev)-h, --help- Show this help message
Examples:
sprite upgrade # Upgrade to the latest versionsprite upgrade --check # Check for available updatessprite upgrade --force # Force upgrade even if up to datesprite upgrade --channel dev # Switch to the dev channelsprite upgrade --channel rc # Switch to the rc channelExit Codes
Section titled “Exit Codes”| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | General error |
| 2 | Command not found |
| 126 | Command cannot execute |
| 127 | Command not found (in sprite) |
| 128+ | Command terminated by signal |
Environment Variables
Section titled “Environment Variables”| Variable | Description |
|---|---|
SPRITE_TOKEN | API token override (legacy; falls back if no stored token) |
SPRITE_URL | Direct sprite URL (for local/dev direct connections) |
SPRITES_API_URL | API URL override (default: https://api.sprites.dev) |
Configuration Files
Section titled “Configuration Files”Global Config
Section titled “Global Config”~/.sprites/sprites.json (managed by the CLI; format may evolve):
{ "version": "1", "current_selection": { "url": "https://api.sprites.dev", "org": "personal" }, "urls": { "https://api.sprites.dev": { "url": "https://api.sprites.dev", "orgs": { "personal": { "name": "personal", "keyring_key": "sprites-cli:<user-id>", "use_keyring": true, "sprites": {} } } } }}Local Context
Section titled “Local Context”.sprite (in project directory):
{ "organization": "personal", "sprite": "my-project-sprite"}