nasiko builds, tests, deploys, and monitors agents against a control plane. See CLI installation to install it and the quickstart for the core workflow.
State lives in ~/.nasiko/config.json (clusters, active cluster, tokens) and ~/.nasiko/.env (local-stack config).
Every command operates against the active cluster, selected with
nasiko use <name>. Run nasiko <command> --help for full flags.Setup
Create
Test
nasiko chat’s target can be a URL, an agent name or UUID, or orchestrator. Omit it to talk to the routing engine. A lone argument containing whitespace is treated as the message, not the target.
Operate
nasiko deploy to skip the build. nasiko push builds and pushes without starting the container — it does still register a registered-status catalog entry for the agent (visible in nasiko ps/agents ls), it just never runs.
Multi-agent
nasiko maf --help. See MAF for the workflow model and REST API.
LLM configuration
nasiko llm-config --help. See routing engine for how these fit into agent selection.
Integrations
What you’re connecting to
The CLI only operates on agents you own or have been granted. See access control.
