Skip to main content
Nasiko treats the Cursor CLI (cursor-agent) as a coding harness. Discovery and session reporting use Cursor’s hook events. Model routing is not available for Cursor: nasiko connect cursor manages session reporting only. Developers keep using Cursor’s own model settings.

Discover and report

Turning on reporting writes Nasiko command hooks into hooks.json in the Cursor config directory. Existing hooks stay. nasiko disconnect cursor removes only the Nasiko entries. Cursor turns arrive across several hook events. Nasiko assembles them under ~/.nasiko/integrations/events/ and queues a turn once it is complete. See Session reporting. After that, keep using cursor-agent the way you always do. Completed turns show up in Sessions and in TokenOps under the Cursor (<your email>) agent.

Stop reporting

For Cursor, disconnect removes session reporting, since there is no routing to remove. Past sessions stay on the server.

What you cannot do

Model routing isn’t available for Cursor. nasiko connect cursor rejects the routing flags --agent, --config, --mcp, and --no-mcp, and nasiko status cursor shows routing as not supported. Routing targets are claude, codex, and opencode only. Cursor spend is still attributed when reporting is on, using whatever model Cursor itself called.

Identity in Nasiko

Registration creates a coding-agent identity named <username>-cursor, labelled Cursor (<your email>) in the dashboard. The agent page has no Configure or Logs tab — nothing runs on Nasiko for a coding agent.

Troubleshooting

More: Troubleshooting.