CLI
npm install -g @glytos/cliRequires Node.js 18 or newer. The command is glytos.
Authentication
Log in once to save your credentials to ~/.glytos/config.json (written owner-only):
glytos loginEach setting resolves in this order, first match wins:
| Setting | Flag | Environment variable | Config file |
|---|---|---|---|
| API key | --api-key | GLYTOS_API_KEY | apiKey |
| Base URL | --base-url | GLYTOS_BASE_URL | baseUrl |
| Environment | --environment | GLYTOS_ENVIRONMENT | environment |
So you can skip glytos login entirely in CI:
GLYTOS_API_KEY=gly_... glytos agents listCommands
glytos agents list
glytos agents create --name "Support bot" --mode prompt
glytos agents publish <uuid>
glytos chat <uuid> # interactive text chat; /exit to leave
glytos chat <uuid> -m "What are your hours?" # one message and out
glytos calls create --to +15551234567 --agent <uuid>
glytos calls list
glytos numbers search --country US --area-code 415
glytos numbers import --e164 +15551234567 --provider twilio --workflow <uuid>
glytos campaigns create --name "July outreach" --agent <uuid> --from +15551234567 \
--contacts-file leads.csv --window 09:00-20:00 --timezone Europe/Istanbul
glytos campaigns start <uuid>
glytos campaigns stop <uuid>
glytos dnc add +15551234567 --reason "asked on a call"
glytos dnc list
glytos sessions # inspect conversations (alias: glytos logs)
glytos webhooks list
glytos suites list
glytos suites run <uuid> # exits non-zero when a case fails
glytos balance
glytos usage
glytos trunks list
glytos trunks test <uuid>Add --environment prod (or set GLYTOS_ENVIRONMENT) to run a command against a
specific environment. Remove saved credentials with glytos logout.
Gating a deploy on a test suite
suites run exits non-zero when a case fails, so a pipeline can stop on a prompt
regression before it reaches callers. The results print either way:
glytos suites run $SUITE_UUID || exit 1It runs the agent for real, so it spends credit like any other conversation.
Chatting with an agent
glytos chat is the fastest way to try a text agent. The reply streams in as it is
written; --no-stream waits for it whole, and --json prints the raw turn.
glytos chat <uuid> -m "Rate this transcript" --instructions "Score 1-5, reply as JSON."
glytos chat <uuid> -m "and then?" --session <session-uuid>--instructions applies to that run only and is never saved to the agent. See
Chat.
The CLI is built on the same public API as the SDKs, so anything you can do in the app you can script from your terminal or a CI job.