Skip to main content
Nasiko ships two command-line tools, both standalone Rust binaries. Building or deploying agents? Install nasiko. Provisioning a control plane or managing users, teams, and grants? Install nasiko-ee. Many administrators install both.

​
Set up from the dashboard

Set up CLI in the dashboard header opens a four-tab walkthrough with a Download CLI package button and a copy button on every command.
1

Install

Download the package, then install it globally and check the version.
2

Connect cluster

Connect with your access key and secret, make it the active cluster, and verify.
3

Create your first agent

nasiko agent new scaffolds interactively — framework, description, skills, project files — then copy .env.example and fill in your API keys.
4

Run and publish

Run locally on port 5000, chat with it, then deploy to the active cluster.

​
Developer CLI (nasiko)

Installs to ~/.cargo/bin. State lives in ~/.nasiko/config.json (clusters, active cluster, tokens) and ~/.nasiko/.env (local-stack config from nasiko up).
1

Point at a control plane

nasiko up connects itself automatically as cluster local. For an existing control plane:
2

Pick the active cluster

All commands operate against the active cluster.
3

Authenticate

​
Troubleshooting nasiko up

Known gaps in the current build. Find your symptom, apply the workaround.
nasiko up pulls nasiko/cp:latest from Docker Hub to run the local control plane, and that image isn’t publicly available yet. Build the control plane from source instead:
nasiko up only pulls the image when ~/.nasiko/bin/nasiko-cp doesn’t already exist, so once it’s there, nasiko up starts the infra containers and runs your build instead of pulling.
The control plane requires ADMIN_PASSWORD and JWT_SECRET at startup — neither has a default, and nasiko up doesn’t prompt for them or set them itself. Export them first:
With ADMIN_PASSWORD set this way, the printed nasiko auth login # admin / admin hint is accurate — log in with whatever username/password you chose.
Unlike the Docker infrastructure (which runs detached), the control-plane process is a plain foreground child of the shell you ran nasiko up in — closing the window, an SSH disconnect, or a multiplexer pane closing all kill it. Keep that terminal open, or run it yourself as a background process:
Use the same environment variables nasiko up would otherwise set — see its output for the full list.
nasiko up doesn’t set TEMPO_URL or LOKI_URL, so the control plane starts with observability disabled even though the same compose file already brings up Tempo and Loki containers. Set both before starting it to see trace and cost data in nasiko observe:

​
Platform admin CLI (nasiko-ee)

Enterprise feature. Everything below this heading (install script, build-from-source variants, control-plane provisioning, registry activation) is nasiko-ee — the enterprise admin CLI. Not available in the open-source edition.
Anonymous download, no login. Installs to ~/.local/bin, never uses sudo, never edits your shell rc files — it prints the PATH line to add.If piping curl into bash is disallowed at your organization, download and review the script first.
Verify with nasiko-ee --version.

​
Provision a control plane

Creates ~/.nasiko/.ee.env with a template for cloud credentials (AWS, DigitalOcean, Azure, or GCP), your Docker Hub org, and optional keys like OPENAI_API_KEY. Fill it in, then:
Next: setting up an organization.

​
Registry access

The control-plane image comes from a private registry. Save the read-only pull token Nasiko provides:
Writes ~/.nasiko/registry-values.json, which the cluster install commands use to authenticate pulls.