@terminal-api/cli. Its commands are generated from the Terminal OpenAPI spec. For setup steps, see the Agents guide.
Configuration
The CLI authenticates with a secret key and, for connection-scoped commands, a connection token. See Authentication.
Environment variables take precedence over the config file. The config file lives at
~/.terminal/config.json; terminal config show prints the active values and terminal config path prints the file location.
Profiles
Profiles keep separate credentials, for example sandbox and production. The CLI ships withprod (default) and sandbox profiles.
TERMINAL_PROFILE to choose a profile without passing --profile.
Usage
terminal with no arguments to open an interactive TUI for browsing and running commands.
Global options
Commands
Each Terminal API operation is a command named after the operation in kebab-case. For example, List Vehicles isterminal list-vehicles. Unlike the MCP server, the CLI includes write operations such as passthrough and request sync.
Path, query, and body parameters are flags with the same names as the API parameters:
authentication, connections, data-management, devices, drivers, fault-codes, groups, hours-of-service, ifta, issues, link, providers, safety, trailers, trips, vehicle-utilization, and vehicles. Run terminal --help for the full list, or terminal <command> --help for a command’s flags.
Response schemas
Appendschema to any command to print its response schema without calling the API:
Shell completions
Agent skills
The CLI repo ships skills and commands for Cursor, Claude Code, and OpenCode. Copy them into your project so the agent knows how to call the CLI.Rate limits
CLI commands are ordinary Terminal API requests and count toward the same rate limits.--all fetches pages one at a time.