Skip to main content
You need the nasiko CLI and somewhere to connect it: your Nasiko Cloud workspace, or a Nasiko server you or your organization runs. The CLI calls whichever one it’s connected to a cluster. Coding-agent discovery (the coding-agent rows of nasiko status) works with just the CLI. Nasiko ships two command-line tools, both standalone Rust binaries:

Install the CLI

Check it with nasiko --version.
The dashboard has the same steps with copy buttons. On Nasiko Cloud, open the Nasiko CLI page (/cli): its connect command already names your workspace. On a self-hosted server, click Set up CLI to open a walkthrough covering install, connecting, creating your first agent, and deploying it.

Connect to Nasiko Cloud

1

Sign up

Go to app.nasiko.com and continue with Google or GitHub. Any email works, and Free needs no card.
2

Connect the CLI and sign in

In the dashboard, open the Nasiko CLI page (/cli) and copy the connect command. It names the workspace you’re in. On Free:
The CLI checks the workspace is reachable, saves it, and makes it the active cluster. Then it signs you in: it prints a code and opens your browser, and you approve it with your Nasiko account. Your token is stored in ~/.nasiko/config.json. Check it with nasiko auth whoami or nasiko auth status. Sign out with nasiko auth logout.
3

Pick the coding agents to connect

Once you’re signed in, the CLI lists the coding agents it found on this computer and asks which should report sessions to this workspace. Nothing is selected to start with. An agent that already reports to another cluster is listed as reports sessions to <cluster>; select to move it here. Select none to change nothing.The CLI doesn’t ask again about an agent you leave unselected, for this cluster and account. To turn on reporting for every detected agent without questions, and import their past sessions, run nasiko agents setup. See Discover and register.
When you switch workspaces in the dashboard, connect the CLI to the new one the same way. List saved connections with nasiko clusters, and switch with nasiko use <name>.

Connect to a self-hosted server

The open-source Nasiko server is free to run yourself. Pick where it runs.
Get the URL and an account from your administrator. An administrator creates your account and gives you either a username and password, or an access key and secret. The secret is shown once, so save it.
Then connect and sign in:
1

Connect and sign in

The CLI checks the server’s health endpoint, saves it, and makes it the active cluster. Then it signs you in: through SSO in your browser when the server has an identity provider, otherwise at a username and password prompt, where an access key and secret also work. Your token is stored in ~/.nasiko/config.json. Check it with nasiko auth whoami. Sign out with nasiko auth logout.Once you’re signed in, the CLI asks which of the coding agents on this computer should report sessions to the server. An agent that reports to another cluster can be moved here. See Discover and register.nasiko up registers the server as local for you without signing in. Run nasiko auth login and sign in as admin with the ADMIN_PASSWORD from .env (changeme in .env.example).
2

Pick the active cluster

Every command runs against the active cluster.
The dashboard and the CLI use the same account. Sign in to the dashboard at your server’s URL.

Troubleshooting nasiko up

nasiko up and nasiko down run from a clone of the repository: the current directory or one above it must hold docker-compose.yml and server/Dockerfile. Clone the repository and run the command inside it.
The stack started, but the server didn’t pass its health check in time. The first build can take longer. Read the server’s log from the repository checkout:
nasiko up registers the local cluster either way, so once the server is healthy you can sign in.

Admin CLI (nasiko-ee)

Plans: Enterprise (dedicated or self-managed). Self-hosted: Enterprise license. Nothing in this section applies to Free, Individual, or Pro workspaces on Nasiko Cloud.
Anonymous download, no login. Installs to ~/.local/bin, never uses sudo, and 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 cluster

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

Registry access

The Enterprise server image comes from a private registry. Save the read-only pull token Nasiko provides:
This writes ~/.nasiko/registry-values.json, which the cluster install commands use to authenticate pulls. All nasiko-ee commands: Admin CLI reference.