Skip to content

CLI Overview

The Orvanta CLI (orvanta) is the primary command-line interface for managing scripts, flows, apps, and other resources in a workspace. It works on a local-files-synced-to-workspace model: you keep scripts and flows as files in a git repository, then push and pull changes to a workspace.

See Installation for full setup instructions.

Terminal window
npm install -g @orvanta/cli
orvanta --version

Upgrade later with orvanta upgrade.

orvanta <command> [subcommand] [options]
Terminal window
orvanta workspace add # connect to a workspace (creates a profile)
orvanta init # initialise a project directory + sync config
orvanta sync pull # bring remote scripts/flows/apps into local files
# ... edit files ...
orvanta sync push # deploy local changes back to the workspace
GroupDescription
workspaceAdd, switch, and manage workspace profiles.
syncPush and pull changes between local files and a workspace.
scriptCreate, run, and manage scripts.
flowCreate, run, and manage flows.
jobList, inspect, and cancel jobs.
appCreate and develop apps (app new, app dev).
resource / variable / schedule / triggerManage workspace resources.
FlagDescription
--workspace <name>Target a specific workspace, overriding the default.
--token <token>Provide an API token directly (overrides any stored token).
--base-url <url>Target a specific instance URL (requires --token and --workspace).
--config-dir <dir>Use a custom config directory (overrides OV_CONFIG_DIR and the default ~/.config).
--debug --verboseShow debug/verbose logs.
--jsonOutput as JSON (useful for piping to jq).

Workspace profiles, each a (name, remote URL, workspace id, token) tuple, are stored under your Orvanta config directory (default ~/.config, override with OV_CONFIG_DIR). Switch between profiles with orvanta workspace switch <name>.