Smplify CLI Workflows

Use Smplify CLI in shell, automation, and AI-assisted loops.

The CLI is designed to be predictable for humans, shell scripts, CI jobs, and coding agents: stable resource-action verbs, clear flags, JSON output, and tenant-aware execution.

Operator flow

Sign in, choose the active tenant, inspect devices, and trigger a remediation run with a human-reviewed command sequence.

smplify auth login
smplify tenant list
smplify tenant use <tenant-id>
smplify device search --os windows --status vulnerable --output json
smplify remediation run patch-critical --device dev-123

Automation flow

Prefer JSON output in scripts so downstream tooling can filter, transform, and act on results without rebuilding API auth and request handling.

smplify device search --os windows --status vulnerable --output json \
  | jq '.[] | select(.risk_status=="vulnerable") | .id'

AI coding workflow

For tools like Codex or Claude Code, the CLI becomes the deterministic execution layer underneath a higher-level reasoning loop.

Reasoning layer

Use MCP and docs to plan: discover what needs to happen, identify the right tenant, and decide the remediation or admin action.

Execution layer

Use the CLI to execute: the command structure is stable, scriptable, and easier for agents to call repeatedly and safely.

Design principles

The CLI is optimized for composability and predictable execution, not for interactive hidden state.

Stable verbs

smplify <resource> <action> is the core command pattern.

JSON-first

Machine-readable output is available wherever automation needs it.

Tenant-aware

Active tenant context is persisted and injected into requests consistently.

Release-backed

Installers resolve published binaries and checksums from GitHub Releases.