ornn to inspect and manage your organization’s resources from a terminal.
Install
The Ornn CLI requires Node.js 20 or newer. Install it with npm or the hosted installer.ornn --version to check the installation. Then sign in and try the CLI.
On desktop, Cloud Shell opens a browser terminal with the CLI already signed in.
Check your organization
Runornn context to see the account and organization the CLI is using. Browser sign-in defaults to the organization you joined most recently.
ornn login --no-browser and open the printed URL on your device.
Find commands and flags
Runornn help for common commands and ornn resources to browse by resource. Pass a command to ornn help to see its arguments and flags.
ornn connect TARGET searches your organizations and uses the organization with the unique match. If a hostname is ambiguous, pass the machine ID. For examples, see Connect to compute.
Follow the storage and image guides for the commands and mount or push checks. Mount a volume · Import a GCS bucket · Push a container image.
See the endpoint pages for request fields and CLI equivalents. API reference.
VPN connection commands use the organization that owns the reservation you pass. Private network commands use your current organization.
Run commands in scripts
LoadORNN_API_KEY from your secrets manager. It takes precedence over a saved browser login and uses the organization that issued the key. Unset it before running ornn login again. API keys.
Pass --format when running outside an interactive terminal. Use json for a single result or ndjson to receive progress records before the final result.
ornn.cli/v1 schema. Read data for the result, outcome for its status, and errors for failures. If page.next_cursor is non-null, pass it to --cursor to read the next page.
For commands that change resources, use exact IDs. If the command supports --idempotency-key, reuse the same key and input when retrying. Set a timeout when waiting for readiness.
Upgrade from CLI 0.2
Runornn update --major to move to CLI 1.x, then check with ornn --version. Your saved login and endpoint settings carry over.
Use ornn context in place of ornn whoami, ornn connect in place of ornn ssh, and --format json in place of --json. Run ornn help for current commands. You can roll back by reinstalling @ornncompute/cli@0.2.10 before January 4, 2027 UTC.