cursor-agent. It starts cursor-agent acp, the CLI’s own agent protocol server, so there is no adapter to install.
What you need
The Cursor CLI. Arakun looks forcursor-agent on your PATH and in ~/.local/bin. The installer also links it as agent, but Arakun doesn’t look for that name. Arakun does not install the CLI: Cursor’s installer keeps it up to date.
ARAKUN_CURSOR_BINpicks anothercursor-agent.ARAKUN_CURSOR_ACPruns another command instead ofcursor-agent acp.
Sign in
Cursor runs on one of these:- Your Cursor account. Open Settings › Cursor and click Sign in, or press Ctrl+K and pick Sign in to Cursor. A terminal runs
cursor-agent login; approve the sign-in in the browser. If you signed in tocursor-agentin a terminal before, you’re done. - A Cursor API key. Set
CURSOR_API_KEYin the environment Arakun starts in. Settings › Cursor then names the variable.
cursor-agent logout.
Arakun has no account of its own. It only checks that Cursor has a sign-in, and never reads the tokens.
Pick a mode and a model
The menu next to the composer lists the models Cursor offers. The chip next to it sets Cursor’s mode: Agent, Plan or Ask. None of them skips asking. The environment remembers your picks for its next session. Arakun reads the options once Cursor is signed in, with a session that never gets a prompt, so it costs no tokens.Your MCP servers
Cursor sessions use the MCP servers in~/.cursor/mcp.json and in the project’s .cursor/mcp.json. Arakun doesn’t change them.
Good to know
- Cursor reads the project’s
AGENTS.mditself. Arakun can’t add its note about thearakuncommand to Cursor’s prompt. - With Sandbox agents on in Settings › Project, Cursor runs in a sandbox.
- Cursor can write commit messages and pull request descriptions. It runs in ask mode for that, so it only reads.
- Removing a session from Arakun leaves Cursor’s own copy of it.
What does not work yet
- The Usage tab shows no tokens, cost or plan limits for Cursor. When your plan runs out, Cursor says so in the session.
Common errors
cursor-agent was not found on PATH or in ~/.local/bin
cursor-agent was not found on PATH or in ~/.local/bin
Install the Cursor CLI, or point
ARAKUN_CURSOR_BIN at the binary.Cursor is not signed in
Cursor is not signed in
Click Sign in in a terminal under the error, or run
cursor-agent login in a terminal and sign in in the browser. Or set CURSOR_API_KEY. Then retry.