Talk to a security advisor — a free 30-minute review
Reference

CLI reference.

Every alphaciso-cli command, with the flags you'll actually reach for.

Installing the CLI

The CLI is a single static binary. Install it the same way you install the agent — script or manual.

Shell
brew install alphaciso/tap/cli
# or
curl -sSL https://get.alphaciso.com/cli | sh

Verify:

Shell
alphaciso --version
# alphaciso-cli 1.4.2 · workspace AlphaCISO · region us-east-1

Top-level commands

Fieldtypedescription
agentcommandInstall, configure, and inspect the host agent.
pipelinecommandApply, validate, and roll back OTLP pipeline configs.
objectivecommandCreate and manage SLOs and budgets.
incidentcommandList, open, and close incidents from the terminal.
workspacecommandManage workspace-level config: retention, members, regions.
voicecommandManage the auto-postmortem voice corpus.

The five commands you'll actually use

Print the live state of the local agent — connection, ingest health, clock skew, and the size of the on-disk buffer.

Shell
alphaciso status
# connected · ingest=ok · clock-skew=12ms · buffer=8.2 MB

Global flags

These work on every subcommand:

Fieldtypedescription
--workspacestringOverride the workspace from alphaciso_WORKSPACE.
--regionstringPin the request to a specific region (us-east-1, eu-west-1, ap-south-1).
--formatstringOutput format: text (default), json, or yaml.
--dry-runbooleanValidate and explain, but don't make changes.
--diffbooleanShow the diff against the current state before applying.

Configuration file

The CLI reads from ~/.config/alphaciso/cli.toml. Most teams check this file into a personal dotfiles repo.

Config
workspace = "AlphaCISO"
region    = "us-east-1"
format    = "text"

[notifications]
slack = "https://hooks.slack.com/services/..."

Tip. The CLI respects alphaciso_* environment variables, which trump the config file. CI systems should rely on env vars; humans on the file.

CLI ready