meerkat-cli-referencelisted

# Meerkat CLI Reference Use this skill as the exact authority for `rkat` shell commands. Command spelling, singular/plural forms, flags, and enum values matter. ## Hard Negative Facts - There is no `rkat sessions`; use singular `rkat session`. - There is no `rkat resume`; use `rkat run --resume ...`. - There is no `rkat rpc`; use the `rkat-rpc` binary for JSON-RPC. - `rkat-rpc --tcp` is not a Meerkat signed peer/comms listener; use `rkat run --comms-listen-tcp ...` for remote peers and external mob members. - There is no `rkat live`; use JSON-RPC `live/*` with `rkat-rpc --live-ws`. - There is no `rkat image` command. - There is no `rkat mcp reload` CLI command. - There is no `--tools all`; valid values are `safe`, `workspace`, `full`, `none`. - `rkat blob get` has no `-o` or `--out`; use `--output <FILE>`. - `rkat session show` has no `--json` flag. - `rkat models` and `rkat capabilities` already print pretty JSON and have no `--json`/`--format` flags. ## Root ```bash rkat [OPTIONS] <PROMPT> # shorthand for rkat run <PROMPT> rkat [OPTIONS] <COMMAND> ``` Global/realm options: ```bash -r, --realm <REALM> --isolated --instance <INSTANCE> --realm-backend <jsonl|sqlite> --state-root <PATH> --context-root <PATH> --user-config-root <PATH> --default-model <MODEL> ``` `--default-model <MODEL>` persists the default agent model into the scope-resolved config (same project/user/realm resolution as every other command) and exits when given without a command, or applies first