Reference
CLI
Manage monitors, channels, and incidents from your terminal — single static binary, structured output.
Coming soonPhase 2
Overview
The teravor CLI will land as part of Phase 2. Create and list monitors, trigger heartbeats, view recent incidents, and dry-run config changes without leaving the terminal. Track progress on the roadmap.
✦
Everything the CLI does is also in the API
Every CLI command is a thin wrapper over the REST API. If you need automation before the CLI ships, use the API directly — the contract is identical.
What to expect
- Single static binary — distributed via Homebrew and GitHub releases.
teravor monitor,teravor channel, andteravor incidentsubcommands mirroring the REST API.- Apply monitors from a YAML or JSON file, with a
--dry-runplanner. - API-token auth via
TERAVOR_API_TOKENor a stored profile. - Structured JSON output for piping into scripts.
Command preview
bash
# macOS via Homebrew
brew install teravor/tap/teravor
# Linux
curl -fsSL https://get.teravor.com | sh
# npm
npm i -g @teravor/cliEarly access
Email [email protected] and we'll ping you when the first build is usable.
Was this page helpful?Last updated