Reference

CLI reference.

Every meridian-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 meridian/tap/cli
# or
curl -sSL https://get.meridian.systems/cli | sh

Verify:

Shell

meridian --version
# meridian-cli 1.4.2 · workspace acme-prod · region us-east-1

Field	type	description
agent	command	Install, configure, and inspect the host agent.
pipeline	command	Apply, validate, and roll back OTLP pipeline configs.
objective	command	Create and manage SLOs and budgets.
incident	command	List, open, and close incidents from the terminal.
workspace	command	Manage workspace-level config: retention, members, regions.
voice	command	Manage the auto-postmortem voice corpus.

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

Shell

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

These work on every subcommand:

Field	type	description
--workspace	string	Override the workspace from MERIDIAN_WORKSPACE.
--region	string	Pin the request to a specific region (us-east-1, eu-west-1, ap-south-1).
--format	string	Output format: text (default), json, or yaml.
--dry-run	boolean	Validate and explain, but don't make changes.
--diff	boolean	Show the diff against the current state before applying.

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

Config

workspace = "acme-prod"
region    = "us-east-1"
format    = "text"

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

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

CLI ready