CLI

npm install trigora

The npm package provides a Node launcher for the Rust CLI. Node 22 is required for that launcher and for TypeScript or JavaScript projects that use the TypeScript adapter. Projects that use only Python or Rust do not require Node. See Install. Authentication uses TRIGORA_TOKEN; the CLI does not provide a trigora login command.

TRIGORA_TOKEN authenticates Trigora Cloud. It does not choose the target of a runtime command.

Dual-target

These commands target trigora dev by default. Add --remote to target Trigora Cloud. --remote requires TRIGORA_TOKEN.

Command	What it does
`trigora programs`	List programs
`trigora executions`	List executions
`trigora executions inspect <id>`	One execution
`trigora start <program>`	Start an execution
`trigora send <id> <event>`	Deliver an event
`trigora cancel <id>`	Cancel

# Local — default
trigora programs
trigora executions
trigora executions inspect <id>
trigora start approval
trigora send <id> approved
trigora cancel <id>

# Trigora Cloud
trigora programs --remote
trigora executions --remote
trigora executions inspect <id> --remote
trigora start approval --remote
trigora send <id> approved --remote
trigora cancel <id> --remote

--input and --payload are JSON, or a path to a JSON file. --input is the ordered argument vector when it is a JSON array. A single JSON value is one argument. Omitting it sends {}.

trigora start approval --input '{"note":"stored"}'
trigora send <id> approved --payload '{"ok":true}'

Cloud-only

trigora deploy, trigora secrets, and trigora whoami always talk to Trigora Cloud. They require TRIGORA_TOKEN. They do not take --remote.

Command	What it does
`trigora deploy`	Compile and upload to Cloud
`trigora secrets`	List, set, or delete project secrets
`trigora whoami`	Workspace for the Cloud token

export TRIGORA_TOKEN=...
trigora deploy
trigora deploy --program approval
trigora secrets set OPENAI_API_KEY
trigora whoami

trigora secrets set reads the value from a prompt or stdin. See Secrets.

Local measurement

trigora bench and trigora verify run in-process on a temporary SQLite host. They do not start trigora dev, and they do not talk to Trigora Cloud. See Benchmark and verify.

trigora bench my-program
trigora verify my-program --faults all

Local setup

Command	What it does
`trigora init`	Writes the scaffold for TypeScript, Python, or Rust
`trigora dev`	Local runtime on `localhost:3477`

trigora dev follows the chain in the CLI reference: trigora spawns trigora-local, which drives tcc-host-sqlite.

trigora dev --host localhost --port 3477

Full flags, including per-language init files: CLI reference.