Cursor

Set up

curl -fsSL hanzo.sh | sh
hanzo login
hanzo code cursor

This runs Cursor's agent CLI, agent, or cursor-agent where that is the only name on your path. Install and sign in to it first, as you would to use it alone. agent and cursor-agent are accepted spellings of cursor.

What the wrapper does

Cursor keeps its own login and its own backend. hanzo code cursor has no gateway route for it, so it always runs on Cursor's account, with or without --no-route. The wrapper:

• starts the binary in your repository, with --force so it stops asking before each action; --ask leaves its own prompts in place;
• for a task (hanzo code cursor "fix the failing test"), runs it with --print and --output-format stream-json, and when the session is linked streams the assistant's messages and the final result to the cloud;
• registers the session in the cloud with its machine and directory, and updates its status when the tool exits. An interactive run is Cursor's own screen, so its events are not streamed;
• passes any other flags through to the tool unchanged.

What it does not do

• No routing. Cursor's model calls do not go through api.hanzo.ai, and Hanzo does not see them.
• No metering. Nothing is counted into your org's usage. The end-of-session block prints the duration and the session link, and says the usage was not observed.
• No Hanzo toolset. The Hanzo MCP server and your org's cloud tools are not attached to Cursor.
• No resume. The tool discloses no session id to the wrapper, so hanzo --resume has nothing to continue.

See the session

hanzo console          # sessions and machines; press 6 for the usage Savings page

The Savings page shows your org's usage from other tools, not Cursor's. How to read the numbers →

Keep your own plan

There is nothing to turn off: Cursor already runs on its own. --no-link stops the session being shown in the cloud.