Skip to main content
In about ten minutes you’ll install the CLI, discover the coding agents on your machine, start reporting their sessions to a Nasiko cluster, and see their spend in TokenOps. Routing a harness to a different model is an optional last step. Nothing about how you use your harnesses changes. Claude Code, Codex, OpenCode and the Cursor CLI keep running exactly as they do today.
Want to build and deploy your own agent instead? Follow Quickstart: deploy an agent.

​
Prerequisites

  • Rust to install the CLI
  • Docker with Compose, to run a local Nasiko cluster — or the URL of your organization’s cluster and an account on it
  • At least one supported coding agent installed: Claude Code, Codex, OpenCode or the Cursor CLI

​
Find and measure your coding agents

1

Install the CLI

This installs nasiko into ~/.cargo/bin. Use --force when you update: every build reports version 0.1.0, so the version number alone won’t tell you whether you have the latest commands.
2

Discover what's already running

Discovery reads your machine, prints one row per supported harness, and exits. It changes no settings, needs no account, and sends nothing off the machine. Detected means the harness binary is on your PATH or its config directory exists. Connected means session reporting is installed, and Version is the version of the Nasiko reporting hook.
3

Start or connect to a Nasiko cluster

From the nasiko repo you cloned:
Edit .env and set:
  • ADMIN_PASSWORD: the password for the admin account
  • OPENAI_API_KEY: a model provider key
  • AGENT_JWT_SECRET: uncomment it and set a random value (openssl rand -base64 48). Model routing in the last step needs it.
The first build compiles the server inside Docker and takes a few minutes. The dashboard is at http://localhost:8080. The Compose stack already sets up everything coding-agent cost reporting needs. See Deploy the stack for details.
4

Sign in — reporting installs itself

When you sign in, Nasiko installs session reporting for every detected harness that doesn’t already have it, and registers each harness with the cluster. Run nasiko agents discover again and Connected reads yes.To install reporting for one harness explicitly, or to leave prompt and response text out of what’s reported:
Restart OpenCode after reporting is installed so it loads the plugin. Codex asks you to trust the new Nasiko hooks the next time it starts.
5

Work as usual, then look at the spend

Use your harness the way you always do. Each completed turn is queued on your machine and delivered to the cluster in the background. If the cluster is unreachable, turns wait in the queue and the harness is never blocked.
In the dashboard, Sessions lists the same conversations. Overview and TokenOps break down spend by agent — each harness is registered as its own agent — and by model. See the TokenOps dashboard.
6

Optional: route a harness to the model you choose

Harnesses arrive tied to a vendor: Claude Code to Anthropic, Codex to OpenAI. Routing gives the model choice back to you. Register a provider key once, then connect a harness to it:
Claude Code keeps speaking its own protocol, and Nasiko routes each call to the model in your config. Routing is available for Claude Code, Codex and OpenCode. Undo it at any time with nasiko disconnect claude. See Route models for what changes on your machine and how failures behave.

​
Next steps

How reporting works

What’s captured, where it’s queued, and how delivery is kept safe.

Cost attribution

One cost schema across every harness and vendor.

Per-harness guides

Claude Code, Codex, OpenCode and Cursor specifics.

Deploy an agent

Build and run your own agent on the same cluster.
Stuck? See Troubleshooting, ask in Discord, or email support@nasiko.com.