CLI Reference

stallari-cli is the local command-line companion for setup, diagnostics, and advanced operations. Most users can use the app. Use the CLI when you need a copyable diagnostic command or a low-level check.

Common Commands

Command	Purpose
`stallari-cli status`	Show helper and local subsystem status.
`stallari-cli config validate`	Validate the current configuration.
`stallari-cli config show`	Print a readable configuration summary.
`stallari-cli run <name>`	Request a named workflow or skill.
`stallari-cli plugins`	Inspect installed plugin state where supported.
`stallari-cli packs`	Inspect installed pack state where supported.
`stallari-cli lens`	Inspect or repair the local Lens index where supported.

Exact subcommands vary by release. Run:

stallari-cli --help
stallari-cli <command> --help

Running Work

Use the app or Chat for normal work. The CLI is useful for debugging and explicit manual runs:

stallari-cli run daily-summary

If the command touches plugins or external services, the same policy and review model applies. CLI use does not bypass plugin consent, credentials, or action gates.

Inspecting Activity

Recent work is best inspected in Activity. The CLI may expose commands for searching or showing recorded work, depending on the release.

Use Activity when you need the full detail view. Use the CLI when you need a quick terminal check for a support or debugging session.

Configuration

Validate configuration after manual edits:

stallari-cli config validate

If validation fails, fix the reported field or return to Settings for supported controls. Nix-managed or externally managed configurations should be edited at their source, not through generated output.

Safe Usage

Do not paste secrets into command arguments.
Prefer Settings for provider keys and plugin credentials.
Treat CLI output as local diagnostic material; redact it before sharing publicly.
Use Status first when the issue is health or permission readiness.

Legibility And Continuity — the CLI is a first-party inspection surface alongside the app
Agency Model — CLI runs honour the same plugin consent, scope, and review gates