A command-line tool for game studios to install, update, rollback, and launch builds across Windows, macOS, and Ubuntu — without ever opening the Desktop App. Built for build engineers, DevOps teams, and CI/CD pipelines.
solstahq/claude-cli
Claude Skills for install, rollback & CI/CD — drop into any Claude project.
Pull the latest build or pin to any snapshot. Set a location and the CLI handles the rest.
Update one environment or all of them at once. Schedule it, automate it, run it nightly.
Roll back to any prior build snapshot using a history ID. Full build history available — no reinstall required.
Trigger launches from the terminal — game client, debugger, QA tools with custom launch entry args.
Verify and restore any environment without a full reinstall. Run by name or by location.
Queue and throttle downloads across your network when a throttling rule is enabled. Prevents bandwidth bottlenecks across shared studio infrastructure.
Three scenarios where the Solsta CLI replaces manual processes.
Your team arrives in the morning. Builds are already current on every machine. No one touched anything. Schedule these two commands on each machine to run overnight:
solsta local update --all --queue
solsta queue run
The CLI runs locally — each machine manages its own installs. Queuing requires the Orchestration Service with a throttling rule active. Items in the queue expire after 24 hours.
A Jenkins job kicks off. Machine credentials authenticate silently. The latest build lands on the agent. No browser. No human in the loop.
# Authenticate with M2M credentials — store as env vars, never hardcode
solsta login client_credentials \
--client_id=$CLIENT_ID \
--client_secret=$CLIENT_SECRET
# Install the latest build
solsta local install \
--product=LlamaCraft \
--environment=dev-daily \
--location=/builds/llamacraft/
M2M tokens expire after 24 hours — re-authenticate at the start of each job. Store credentials as environment variables, never hardcoded in scripts.
Something is wrong with today's build. Roll back any machine to a known-good snapshot in one command. Find snapshot IDs in the Desktop App → History tab, or use specific release versions instead.
# Roll back using release versions — no Desktop App needed
solsta local install \
--product_name=LlamaCraft \
--env_name=dev-nightly \
--repository_name=dev-debug \
--release_version=6.1.0 \
--repository_name=gameclient \
--release_version=13.2.33 \
--location=c:/ssn/solsta/cli/install/llamacraft/dev-nightly/
# Or use history ID if you have snapshot IDs from the Desktop App
solsta local install \
--product=LlamaCraft \
--environment=dev-daily \
--history_id=b55b42a6-481d-4c92-b3d6-ad1cb1fc68f8 \
--location=/builds/llamacraft/
Version numbers are typically tracked in your git build tags or CI/CD system. Run this on each machine you want to roll back. Optional repositories not named in the command will be uninstalled — name all repos you want to keep.
User tokens stay active as long as the CLI is used once every 30 days. On idle machines like dedicated build servers, schedule a lightweight read command to prevent token expiry.
# Schedule this on idle machines to keep the user token alive
solsta local read
This command reads local install state — no downloads, no changes. Run it on a schedule (cron or task scheduler) on any machine where someone logged in manually but the machine sits idle.
| Platform | Minimum Version |
|---|---|
| Windows | 10+ |
| macOS | 12+ (Apple Silicon & Intel) |
| Ubuntu | 22+ |
Prerequisites
chmod +x /path/to/solstaStandalone binary — no runtime environment, no package manager, no dependencies. A few megabytes. Runs anywhere.
Three steps and you have full CLI access to your environments.
Grab the CLI binary for your platform at solsta.io/download. Standalone executable — no runtime, no dependencies. On macOS or Ubuntu, set execute permissions after download.
Download CLI ›Accept your invitation to a Solsta organization. One command opens a browser login. For CI/CD machines, use machine credentials from the Desktop App — no browser required. Tokens stay active as long as the CLI is used once every 30 days.
List your products and environments. Object names are case-sensitive. From there, every operation is a single command.
Full Command Reference ›The right tool for machines that run unattended, pipelines that can't wait for a click, and studios that want their build workflow scripted and repeatable.
Trigger installs and updates as part of your existing pipeline with M2M credentials. No browser. No human. Re-authenticate at job start — tokens expire every 24 hours.
Install the CLI once on each machine. Keep all environments current with a single command. Each machine manages its own installs independently — no central server pushing commands. Upcoming: centralized orchestration to push commands to nodes.
Nightly syncs, automated rollbacks on a schedule, token keep-alive on idle build servers. The CLI fits naturally into any automation workflow.
Every local, download, or file operation available in the Desktop App is available in the terminal. Fully supported on headless machines and cloud agents.
The Solsta CLI is a standalone command-line tool that lets game studios manage builds on any number of machines. Using a single terminal command, studios can install specific game builds, keep environments current with automated updates, trigger game client launches, and roll back to any prior snapshot. It integrates with Jenkins, TeamCity, GitHub Actions, and GitLab using machine-to-machine (M2M) authentication — no browser required on CI/CD agents.
Each machine runs the CLI independently. There is no central orchestration server pushing commands to machines — your pipeline stays in your control. The CLI and Desktop App share the same local auth token. Do not run both simultaneously — restart the GUI to see CLI changes reflected.
Every CLI command returns a standard exit code. Use debug flags to capture logs for support tickets or pipeline diagnostics.
Command completed without errors.
Help text was returned in response to the command.
Command failed. Use --expected=404 to suppress known errors and return 0.
Windows only — elevated permissions required to write to protected directories.
# Write debug log to desktop (recommended for support tickets)
solsta local update --location=/builds/llamacraft/ --debugfile
# Suppress a known error code — returns exit 0 instead of exit 2
solsta local update --location=/builds/llamacraft/ --expected=404
# JSON output — useful for CI/CD pipelines parsing results
solsta product read --out=json,minify
The Solsta CLI is a command-line tool for game studios that automates build management across Windows, macOS, and Ubuntu machines. It allows studios to install, update, launch, repair, and roll back game builds from the terminal without using the Desktop App — making it well-suited for CI/CD pipelines, headless build servers, and automated studio workflows.
No. The Solsta CLI is a standalone executable, only a few megabytes in size. It requires no runtime environment, no package manager, and no additional dependencies. Download the binary for your platform, set execute permissions on macOS or Ubuntu (chmod +x /path/to/solsta), and run.
Yes. Use Machine-to-Machine (M2M) authentication to connect the Solsta CLI to any CI/CD platform that supports shell commands. Generate M2M credentials from the Desktop App, store them as environment variables, and re-authenticate at the start of each job — M2M tokens expire after 24 hours.
Install the Solsta CLI on each machine. Each machine manages its own installs independently — the CLI does not orchestrate commands across machines from a central location. To keep builds current across your studio, schedule solsta local update --all --queue and solsta queue run on each machine using cron jobs or task schedulers.
Use solsta local install with the --history_id flag to roll back to any prior snapshot. Find snapshot IDs in the Desktop App under the History tab for any environment. Alternatively, use --release_version if you know the specific version number. Note: solsta local update only advances forward — rollback always uses local install with either a history ID or release version.
Solsta uses data deduplication to speed up downloads — only changed data is transferred between updates. Content is delivered via Akamai's global CDN using secure token authentication, reducing transfer size by 85–90% compared to re-downloading the full artifact.
Yes, for most operations. The Desktop App is required to generate Machine-to-Machine (M2M) credentials for CI/CD use. For rollbacks, you can look up snapshot IDs in the History tab, or use specific release versions to roll back without the Desktop App. All other CLI operations — installs, updates, launches, repairs, and orchestration — run entirely from the terminal. The Desktop App also provides team management, user roles and permissions, release promotions, and object creation (products, environments, repositories) — features beyond what the CLI offers.
Solsta supports builds for PC (Windows, macOS, Linux), PlayStation, Xbox, and Nintendo Switch. Platform availability depends on your organization's configuration.
Solsta sets up a dedicated storage bucket for your organization, or you can connect your own. Data is encrypted in transit and secured at rest with AES-256 encryption. Content is delivered via Akamai's global CDN using secure token authentication. Solsta is SOC 2 Type II and ISO 27001 certified. See solsta.io/features#security for full details.
Standalone binary for Windows 10+, macOS 12+, and Ubuntu 22+. No runtime, no dependencies. Download and run.
Download CLICommand reference, authentication guide, orchestration setup, CI/CD integration examples, and debug logging.
CLI Resources ›
