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 is not a command. Developers keep using Cursor’s own model settings.
Discover and report
hooks.json in the Cursor config directory. Existing hooks stay. Uninstall 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 install, keep using cursor-agent the way you always do. Completed turns show up in Sessions and in TokenOps under the Cursor (<your email>) agent.
What you cannot do
claude, codex, and opencode only. Cursor spend is still attributed when reporting is installed, 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.