The Triform CLI
Triform ships a single CLI binary available under three names: triton (the
primary), with triform and triform-cli kept as aliases for existing
automation.
One CLI, any coding agent — and our own built in
The CLI is the fastest way to drive Triform from a terminal, and it is built to
work with whatever coding agent you already use. Every element operation is
the same generated tool catalog whether you reach it over HTTP, the CLI, or
MCP — so Claude Code, Codex, or any MCP-capable agent
operates your circle through it, and a workflow you script one way runs verbatim
the others. Nothing is installed to start: plain curl against the
API already works; the CLI and MCP server are the same operations with
nicer ergonomics when you want them.
It also ships our own coding agent, Triton. triton "your prompt" opens an
agent chat right in your terminal (see the Chat (Triton) section below) — so
you can bring your own model and agent, use ours, or mix both against one
platform.
Install
One command installs the CLI and the MCP server into
~/.triform/bin:
curl -fsSL https://triform.cloud/downloads/install.sh | sh
The installer detects your OS/arch, downloads the matching prebuilt binary,
verifies its SHA-256 checksum, and installs triton, triform, triform-cli,
and triform-mcp. Pin a version with TRIFORM_VERSION=…, or change the install
dir with TRIFORM_BIN_DIR=…. Prebuilt binaries are published for Linux
(x86_64, arm64) and Windows (x86_64).
Windows: use the PowerShell installer instead —
irm https://triform.cloud/downloads/install.ps1 | iex.macOS: there’s no prebuilt binary yet — cross-compiling a Mac binary on the Linux release runners needs Apple’s SDK, so the installer tells you to build from source instead (one command, no SDK on your own Mac):
cargo build --release -p triform-cli -p triform-mcp # then copy target/release/{triton,triform-mcp} onto your PATH
Add ~/.triform/bin to your PATH if the installer reports it isn’t already.
Authenticate
triton auth login # interactive login (opens the browser)
triton auth set-api-key # use a bearer token (trif_…) instead
triton auth status # show who you're authenticated as
triton config show # show the resolved circle + URLs
For production (triform.cloud) and CI, mint a trif_ token from an
api-token element in your circle and use triton auth set-api-key — see
Authentication & access.
Chat (Triton)
triton # open Triton chat; prompts for login when needed
triton "your prompt" # open chat with an initial prompt
triton -p "your prompt" # print one response and exit
triton -p --raw "prompt" # print only the response body and exit
triton -c # continue the latest chat
triton -r <conversation> # resume a specific chat
Calling elements (generated tool commands)
Every element operation is reachable as a CLI command. The shape is uniform:
triton <tool> <action> [--field value ...]
triton <tool> --action <action> [--field value ...]
triton <tool> --input '{"field":"value"}'
triton <tool> --help
triton tools # list the available tools
The same compact tool catalog is exposed over MCP and the HTTP API, so a workflow you script with the CLI is callable verbatim from an agent or a backend.
Related
- MCP server — the same tools over the Model Context Protocol
- Reference: API — the underlying HTTP surface
- Concept: Authentication & access