Cursor's agent hooks give Runi the same shape it has in Claude Code: a
sessionStart hook whose reply becomes real conversation context,
and per-turn hooks that record what the agent did.
Careful
Cursor 2.2 or later is required. Agent hooks did not exist before that, so earlier versions register nothing at all. The connect appears to succeed and no session is ever seen. Check Cursor → About before debugging anything else.
What Runi installs#
Agent hooks in ~/.cursor/hooks.json, and an entry for Runi's MCP
server in ~/.cursor/mcp.json so a Cursor session can ask questions
as well as being told things.
How the briefing arrives#
Cursor's sessionStart hook may answer with
additional_context, which Cursor stores on the conversation and
sends to the model. It is the exact analogue of Claude Code's
additionalContext. beforeSubmitPrompt takes the same
field per turn, which is how a mid-session overlap warning reaches you.
What is observed, and what is not#
| Recorded | Not recorded |
|---|---|
| Your prompts to the agent | Tab completions. Only agent edits are observed. The accepted suggestions you type through are not. |
| Files the agent edits, and the lines it changed | Cursor's private reasoning. The thinking hook is not registered. |
| Commands run and test results | Anything in a repository your workspace does not track. |
Runi also never blocks, delays or alters a prompt you send. The hooks it registers either observe or reply with context, and none of them can hold your turn up.
Verify it#
$ runi doctor
…
ok adapter:cursor ok, last seen 1 min agoThen open a Cursor agent conversation in a tracked repository and ask what context it started with. The briefing is ordinary conversation context, so it can tell you.
Known limits#
- Tab completions are not observed, only agent edits.
- A note queued while a turn is already running reaches the next prompt, not the one in flight.
- Only repositories your workspace tracks are published.
- Cursor 2.2 and later only. Earlier versions register nothing.
Troubleshooting#
In order: the Cursor version (2.2+), that ~/.cursor/hooks.json contains a Runi entry, and that the folder is tracked.
Update Cursor, then reconnect from Settings → Agents. Restart Cursor afterwards, because hooks are read when the app starts.
Your prompt-sharing switch is off. That is a setting, not a fault. Teammates see that you prompted and what changed, but not what you wrote.
If you meant to share them, turn What I ask on in Settings → Sharing. See The two sharing switches.