The Triform CLI
Scaffold — Phase 4 will expand this. A first reference for the
tritoncommand-line interface. The command summary below mirrors the CLI’s own--help; the full per-tool reference is generated from the tool catalog in a later pass.
Triform ships a single CLI binary available under three names: triton (the
primary), with triform and triform-cli kept as aliases for existing
automation.
Install & authenticate
triton auth login # interactive login (opens the browser)
triton auth set-api-key # use a bearer token instead
triton auth status # show who you're authenticated as
triton config show # show the resolved circle + URLs
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