CLI
npm install trigoraThe npm package provides a Node launcher for the Rust CLI. Node.js 22 and 24 are supported for the npm CLI launcher and TypeScript adapter. Python-only and Rust-only projects do not require Node.js. 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
Section titled “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 — defaulttrigora programstrigora executionstrigora executions inspect <id>trigora start approvaltrigora send <id> approvedtrigora cancel <id>
# Trigora Cloudtrigora programs --remotetrigora executions --remotetrigora executions inspect <id> --remotetrigora start approval --remotetrigora send <id> approved --remotetrigora 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
Section titled “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 deploytrigora deploy --program approvaltrigora secrets set OPENAI_API_KEYtrigora whoamitrigora secrets set reads the value from a prompt or stdin. See Secrets.
Local measurement
Section titled “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-programtrigora verify my-program --faults alltrigora pulse runs a customer-operated host. It is not trigora dev and it is not trigora deploy.
| Command | Purpose |
|---|---|
trigora pulse start | Compile this project, start the Pulse host, and start the Node adapter beside it |
trigora pulse connect --dir /pulse | Register handlers with a host that is already running |
trigora pulse connect --dir /pulse --prepare | Write the handler manifest and exit without registering |
export TRIGORA_TOKEN=...trigora pulse starttrigora pulse connect --dir /pulsetrigora pulse connect --dir /pulse --preparetrigora pulse start requires TRIGORA_TOKEN unless you pass --ephemeral. The token stays on the host. --ephemeral keeps the checkpoint in memory and does not recover after the host exits. Do not combine TRIGORA_TOKEN with TRIGORA_PULSE_AUTHORITY_URL, TRIGORA_PULSE_WORKSPACE_ID, or TRIGORA_PULSE_WORKSPACE_TOKEN.
trigora pulse start prints ready after the adapter registers. It does not create an execution. trigora start targets trigora dev, or Trigora Cloud with --remote. It is not the Pulse start path. The application starts an execution by sending { type: "start", executionId } on the adapter session. The Compose reference does that when PULSE_EXECUTION_ID is set. See Node and Deploy.
--dir is the socket directory the host already bound. Both sides must run as the same user.
| Command | Where it runs |
|---|---|
trigora dev | Local SQLite runtime |
trigora deploy | Trigora Cloud |
trigora pulse start | Your host, with Trigora storing the checkpoint |
Local setup
Section titled “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 3477Full flags, including per-language init files: CLI reference.