Prerequisites
- A Nasiko Cloud account. Sign up at app.nasiko.com with Continue with Google or Continue with GitHub. Any email works, and Free needs no card. To use a self-hosted server instead, see Install and connect
- 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
2
Discover what's already running
nasiko status checks your workspace first. Until you connect one in the next step, that part reports an error; the coding-agent rows still print. They come from your machine only and change no settings. Installed means the harness binary is on your PATH or its config directory exists. Reporting says whether session reporting is on.3
Connect to your workspace
In the dashboard at app.nasiko.com, open the Nasiko CLI page (The command saves the workspace, signs you in (approve the sign-in in your browser), and then asks which of the coding agents it found should report sessions to the workspace. Select them with the space bar and press enter. An agent that already reports to another cluster is offered too, to move it here. When reporting is on, the CLI offers to send the sessions you ran before connecting, newest first.Everything you do runs against one workspace: your agents, sessions, model configs, secrets and TokenOps data. On Free you work in Nasiko Free, a workspace shared with everyone on the Free plan; your agents and data are still your own. Individual and Pro get a workspace of their own, and your Free agents and data come with you.Using a self-hosted server? Connect to it instead with the steps in Install and connect.
/cli) and copy its connect command. It names the workspace you’re in. On Free it looks like this:4
Check reporting
Run
nasiko status again and Reporting reads on for the agents you picked. Follow the import of past sessions with nasiko agents status, or on the Coding harnesses page in the dashboard.To turn on reporting for every detected harness without questions, run nasiko agents setup. It also imports their past sessions in the background.Reporting captures prompt and response text. To leave it out for a harness, connect that harness with --no-content. Later setup runs keep that choice, including for imported sessions: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 your workspace in the background. If Nasiko 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 in the same workspace.