CLI use cases

Practical workflows with the miqro CLI. For an end-to-end walkthrough that wires a real connector, see Use case: CLI + integrations.

Every command takes --json and exits non-zero on error, so each recipe below works equally well as a one-off in your terminal or as a step in CI.

1. Operate the approval queue from your terminal

The most important thing the CLI does: it lets a human drive the same approval gate every agent action flows through. An agent proposes a write; it lands in the queue; you decide.

# See what's waiting on a human
miqro queue ls --status awaiting_confirmation
miqro queue ls --status awaiting_human

# Inspect one before deciding
miqro queue ls --status awaiting_confirmation --json | jq '.[0]'

# Approve it (the executor then runs it) or reject it
miqro queue approve act_01H...        # awaiting_confirmation → queued; awaiting_human → done
miqro queue reject  act_01H...        # cancelled, never executed

Approvals are attributed to you automatically (--by defaults to your signed-in email) so the audit log shows who decided. Pass --yes to skip the confirmation prompt in scripts.

2. Triage the fleet

miqro runs ls --hours 24                       # everything in the last day
miqro runs ls --agent support_sla_agent        # one agent
miqro runs ls --json | jq '.[] | select(.status=="error")'   # just failures
miqro runs ls --watch 5                         # live tail, refreshes every 5s

3. Audit what the agents can touch

miqro connectors ls                             # every connectable system + capability counts
miqro connectors show servicenow                # exact reads/actions, risk, which need approval
miqro connectors ls --json | jq '.[] | {provider, actions: (.action_ops|length)}'

This is the same capability manifest that drives the dashboard and the connector docs — so the CLI never drifts from what's real.

4. Approve everything waiting, in a loop (scripting)

Because every command is JSON-friendly and composes, batch operations are one line:

# Approve all low-risk actions awaiting confirmation for a tenant
for id in $(miqro queue ls --status awaiting_confirmation --tenant "$T" --json | jq -r '.[].id'); do
  miqro queue approve "$id" --yes
done

Batch-approving is powerful — prefer it only for action kinds you've reviewed. For anything higher-risk, approve individually after queue ls --json | jq.

5. Run an agent on demand (operator)

# Requires operator/service credentials (the paid-tier boundary is fail-closed)
MIQRO_INTERNAL_KEY=… miqro agent run reporter --task "Summarize this week's runs" --trigger cli

6. Use profiles for dev vs prod

MIQRO_PROFILE=dev  miqro login --api-base http://localhost:8000
MIQRO_PROFILE=dev  miqro runs ls          # hits local
miqro runs ls                              # hits the default (prod) profile