Discovery
nasiko agents setup is missing from nasiko agents --help, or nasiko status shows no coding-agent rows. Your CLI is out of date. Run the install script again, or reinstall from source with cargo install --path cli --force. Builds from different commits can report the same version, so --version can’t tell you whether you have the latest commands.
A harness shows INSTALLED as no in nasiko status. The binary is not on PATH and the config directory does not exist. For Cursor, the binary is cursor-agent, not the Cursor editor.
REPORTING is on but I never turned it on. nasiko agents setup turns on reporting for every detected harness that has none yet. On a terminal, nasiko auth login, nasiko connect <url>, and nasiko use also offer to turn it on, and accepting that offer counts.
REPORTING is still off after signing in. Signing in only offers to turn reporting on, and never changes a harness without a terminal to ask on. Run nasiko agents setup.
REPORTING says stale or needs reinstall. The hook is out of date, or the hook and the saved install record disagree. Run nasiko connect <agent> --no-routing --reporting again.
Session reporting
Turns never appear in Sessions or TokenOps.- Confirm Reporting is
onwithnasiko status. - Finish a turn in the harness (Claude Code
Stop, OpenCodesession.idle, Codex/CursorStop/stop). - Run
nasiko agents sync. - Read
~/.nasiko/integrations/report.log. - Files in
~/.nasiko/integrations/rejected/aren’t retried on their own. Thelast_errorfield says why. After fixing the cause, runnasiko agents sync --retry-rejected. - Codex: trust the hooks with
/hooks. OpenCode: restart so the plugin loads.
CODING_AGENT_OTLP_ENDPOINT on the Nasiko server to an OTLP/HTTP endpoint (Compose sets http://otel-collector:4318). Without it, ingested turns still create sessions, but no coding-agent traces reach Tempo. See Server configuration.
Past sessions don’t show up. nasiko agents setup imports them in the background. Check progress with nasiko agents status or in ~/.nasiko/integrations/import.log. If you ran setup --no-import, run nasiko agents import.
--no-content sessions have no transcript. Expected. Token counts, models, and tool metadata are still exported as traces when OTLP is configured.
I switched clusters and old turns vanished. They didn’t. Each install is bound to the cluster and user active at install time. sync refuses to deliver if that cluster’s URL changed, you are logged in as a different user, or the login expired. Re-login to the original cluster, or reinstall while the new cluster is active — that rebinds future turns only. Queued turns stay bound to their original destination.
The harness feels slow or blocked. Reporting is designed not to do that. The hook always exits successfully, does no network work, and finishes within a 10-second timeout. Delivery is a background nasiko agents sync. If a harness is waiting, it is not waiting on Nasiko reporting.
Model routing
nasiko connect cursor fails. Cursor CLI has no model routing. Reporting only. See Cursor CLI.
Connect succeeds, calls still hit the vendor.
- Restart the harness so it reloads settings or plugins.
- OpenCode: start a new session. Existing sessions keep the model they were created with.
- Claude Code: confirm
ANTHROPIC_BASE_URLin~/.claude/settings.json(or$CLAUDE_CONFIG_DIR). - Codex: confirm
model_provider = "nasiko"inconfig.toml.
nasiko auth status— login must be current on the cluster routing is bound to.AGENT_JWT_SECRETmust be set on the server. Empty means every router request is rejected with401. The.env.examplethatnasiko upand Docker Compose start from sets a development value; if your.envis older, check that the line is present and not commented out.- Routing fails closed. The harness will not fall back to the vendor. That is intentional.
disconnect refuses because the agent is running. Stop the harness, or pass --force.
I disconnected but reporting is still on. disconnect --routing, and disconnect without flags in a script, only remove routing. Run nasiko disconnect <agent> --reporting to remove reporting.
Cluster and login
connect or setup says I am not logged in. Run nasiko connect <url>, which signs you in. If the cluster is already registered, or your login expired, run nasiko auth login.
nasiko up routing or traces don’t work. Check that your .env is not older than .env.example: AGENT_JWT_SECRET must be set and not commented out. See Install and connect.
Logs and state to inspect
nasiko agents sync is always safe to re-run. Replaying a turn the server already stored is a no-op.