CLI

The Nodaro CLI (@nodaro/cli) is a command-line client for Nodaro. It lists and runs workflows, runs published apps, runs a single node without a workflow, and follows each run until it finishes. It keeps several signed-in profiles side by side and prints JSON for scripts, so it fits terminal work, cron jobs and CI pipelines.

The CLI is a thin wrapper around the TypeScript SDK. For an integration written in code, use the SDK directly.

Install

npm install -g @nodaro/cli
nodaro --version

npx @nodaro/cli projects list

# 1. The newest CLI version
NODARO_CLI_VERSION=$(curl -fsSL "https://api.github.com/repos/nodaroai/app.nodaro.ai/git/matching-refs/tags/cli-v?per_page=100" \
  | grep -o '"refs/tags/cli-v[0-9][0-9.]*"' | tr -d '"' | sed 's#refs/tags/cli-v##' \
  | sort -t. -k1,1n -k2,2n -k3,3n | tail -n 1)
echo "Installing @nodaro/cli $NODARO_CLI_VERSION"

# 2. Your platform: darwin-arm64 (Apple silicon), darwin-x64 (Intel Mac), linux-x64 or linux-arm64
NODARO_CLI_PLATFORM=darwin-arm64

# 3. Download. -f fails on an HTTP error instead of saving the error page as the binary.
curl -fL "https://github.com/nodaroai/app.nodaro.ai/releases/download/cli-v$NODARO_CLI_VERSION/nodaro-$NODARO_CLI_PLATFORM" \
  -o /usr/local/bin/nodaro && chmod +x /usr/local/bin/nodaro
nodaro --version

$v = (Invoke-RestMethod "https://api.github.com/repos/nodaroai/app.nodaro.ai/git/matching-refs/tags/cli-v?per_page=100") |
  ForEach-Object { $_.ref -replace '^refs/tags/cli-v', '' } |
  Where-Object { $_ -match '^\d+\.\d+\.\d+$' } |
  Sort-Object { [version]$_ } | Select-Object -Last 1
Invoke-WebRequest "https://github.com/nodaroai/app.nodaro.ai/releases/download/cli-v$v/nodaro-windows-x64.exe" -OutFile nodaro.exe
.\nodaro.exe --version

To pin a version, skip the first step and set the version yourself. Every CLI release and its binaries are listed under the cli-v releases of the public repository.

Sign in

The CLI authenticates with a personal API token and saves it in a profile.

If the browser flow fails, the CLI asks you to paste a token instead. To create a token yourself, open Settings › API in Nodaro and click Create Token. The full token is shown once. Personal API tokens are available on Nodaro Cloud and on Business edition installs. Read Authentication for how tokens work.

nodaro auth login                                   # browser sign-in
nodaro auth login --no-browser                      # paste a token instead
nodaro auth login --token "$NODARO_TOKEN"           # non-interactive, for CI
nodaro auth status [--profile <name>] [--json]      # show a profile, token masked
nodaro auth logout [--profile <name>]               # delete a saved profile

The CLI stores profiles in ~/.config/nodaro/config.json, readable only by your user (file mode 0600). Set NODARO_CONFIG_DIR to keep the file in another folder.

Use profiles for several instances

A profile is a saved instance address and token. Create one profile per instance, such as Nodaro Cloud, a staging install and a local install. Then choose one with --profile, which every command accepts:

nodaro auth login --profile prod    --base-url https://app.nodaro.ai
nodaro auth login --profile staging --base-url https://staging.example.com
nodaro auth login --profile local   --base-url http://localhost:3000

nodaro projects list --profile staging

A command without --profile uses the default profile. The default is production until you save a profile: the first profile you save becomes the default. So a single nodaro auth login, without flags, is all most people need.

Choose a workspace

On an instance with organizations, work lives in workspaces. Choose one for a single command with --workspace <id>, for a shell or a CI job with NODARO_WORKSPACE, or save one on the profile with nodaro workspace use <id>. With none set, work happens in your personal space. See Workspaces and organizations.

Three ways to run something

The CLI covers the three ways Nodaro runs work. Choose the one that matches what you have built.

nodaro nodes run is the CLI equivalent of the verb tools of the MCP server, such as generate_image and generate_video. Every generation node answers at POST /v1/<type>, so any node that nodaro nodes list shows can run with nodaro nodes run. See Run a single node for the REST side.

Add --watch to wait until the run finishes:

nodaro nodes run generate-image \
  --param prompt="a snow leopard on a mountain ridge, cinematic" \
  --param provider=flux \
  --watch

Read Parameters and input files for the --param syntax, and Output and exit codes before you script the CLI.

What the CLI does not cover

The CLI leaves out credits, developer apps, OAuth, pipelines, Reduce and the upload helpers. Use the SDK or the REST API for those.

Moving from the CLI to code is short. This is the SDK equivalent of nodaro workflows run wf_abc:

import { createClient, StaticTokenAuth } from "@nodaro/sdk"

const nodaro = createClient({
  baseUrl: "https://app.nodaro.ai",
  auth: new StaticTokenAuth(process.env.NODARO_TOKEN!),
})

const run = await nodaro.workflows.run("wf_abc")

Next steps