There are no global flags besides --help (and shell completion). The daemon address comes from the ASTROMESH_DAEMON_URL environment variable (default http://localhost:8000). JSON output is a per-command --json flag.
init, validate, config and centinela are not part of astromesh-cli itself: they are registered by the astromesh-node plugin (astromeshctl.plugins entry point), and orbit by astromesh-orbit. Install those packages to get them. astromeshctl version prints the CLI and core versions.
Model context window in tokens; without it the key is written commented out
--output-dir
./config/agents
Output directory
--force
false
Overwrite existing file
The generated template carries guardrails valid for core 0.70 (pii_detection on input and output, max_length, cost_limit 4000), context_window and a commented knowledge.bundle.
Run the kind: Eval files with the core runner (the same as astromesh-eval)
astromeshctl dev
--host, --port, --config, --no-open
Start the dev server with hot-reload
run flags:
Flag
Default
Description
--session
auto-generated UUID
Session ID for multi-turn conversations
--json
false
Output raw JSON response
--timeout
60.0
Request timeout in seconds
--workflow
false
Run as workflow instead of agent
--input
—
Workflow input data as JSON string
By default run prints the answer in a panel and, when the response carries usage.by_model, a Por modelo table below it with one row per provider, model and role: calls, input and output tokens, and cost (— when the cost is unknown). The table adds a Cached column (tokens_cached). When a guardrail blocks the run (core 0.70 answers HTTP 200 with the rejection as answer), run prints a BLOCKED by guardrail panel with direction, rule and reason; the writes recorded by mode: propose tools (propuestas) are listed in a table. --json prints the raw response instead. astromeshctl ask shows the same table.
eval:--out report.json writes the report. Exit 0 if every eval meets its threshold, 1 if one falls below it, 2 on a load error (an invalid eval runs no case).
Success — and also when the daemon is unreachable for the read-only commands (status, doctor, agents list, providers list, services, peers list, mesh …) and when new refuses to overwrite a file: they print the error and exit 0
1
Error in run, traces list, trace, metrics, cost, tools, ask; validate and config validate when they find an error or the config directory doesn’t exist (astromesh-node v0.1.6+, so they work as a CI gate)
2
Invalid arguments (Typer usage error); also centinela failures