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
- Install script (recommended)
- Build from source
macOS and Linux:Windows (PowerShell):No Rust, no account, and no administrator rights. The script picks the build for your OS and CPU (macOS Apple silicon and Intel, Linux x86-64 and arm64, Windows x86-64) and checks its SHA-256 against the registry digest before installing.It installs for your user only: The macOS and Linux script needs
~/.local/bin/nasiko on macOS and Linux, %LOCALAPPDATA%\Programs\nasiko\nasiko.exe on Windows. It never uses sudo and never edits your shell profile. If the install folder isn’t on your PATH, it prints the line to add. On Windows it adds the folder to your user PATH; open a new terminal.bash, curl, sha256sum or shasum, and jq or python3. If piping curl into bash is disallowed at your organization, download and review the script first.Run the script again to update. To remove the CLI, delete the binary and, if you no longer want its settings, ~/.nasiko/.nasiko --version.
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 (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
/cli) and copy the connect command. It names the workspace you’re in. On Free:~/.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.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.- Your organization's server
- nasiko up (recommended locally)
- Docker Compose
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.
1
Connect and sign 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
Troubleshooting nasiko up
no Nasiko checkout here
no Nasiko checkout here
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 server did not answer within 120s
the server did not answer within 120s
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.
- Install script
- Build from source
~/.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.nasiko-ee --version.
Provision a cluster
~/.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:
Registry access
The Enterprise server image comes from a private registry. Save the read-only pull token Nasiko provides:~/.nasiko/registry-values.json, which the cluster install commands use to authenticate pulls.
All nasiko-ee commands: Admin CLI reference.