Cursor
How it connects
runmarq adds Cursor agent hooks to ~/.cursor/hooks.json, or .cursor/hooks.json in a project. Project hooks run only in trusted workspaces. Cursor reloads the file automatically; restart Cursor if the Hooks panel does not list runmarq.
runmarq integrations setup cursorAn observer-only event set
Cursor's pre-execution hooks (preToolUse, beforeShellExecution and others) block an action when their output does not match the expected format, and an explicit “allow” may skip your normal approval prompt. A tool that only observes should take neither risk, so runmarq registers only sessionStart, beforeSubmitPrompt, postToolUse, postToolUseFailure, subagentStop, stop and sessionEnd.
As a result, runmarq sees tools when they finish rather than when they start, and cannot see approval prompts in Cursor. A turn Cursor reports as aborted is recorded as cancelled; one it reports as an error is recorded as failed.
Windows
Cursor does not document which shell runs hooks on Windows. runmarq writes a command without quotes or spaces (using the short form of the path when needed) so it works in both PowerShell and cmd. After setup, send one prompt and confirm the integration shows as connected.
Agent runs only
Commands you type yourself in Cursor's integrated terminal are not agent activity and are not tracked.
Compatibility
| Connection | Cursor agent hooks (hooks.json) |
| Support | Limited |
| Checked against | Cursor 3.23 hook payloads; not yet run live |
Capabilities
| Signal | Available |
|---|---|
| Prompt start | Yes |
| Turn completion | Yes |
| Tool start | No |
| Tool completion | Yes |
| Plan progress | Yes |
| Approval requests | No |
| Errors | Yes |
| Subagents | Yes |
| Model metadata | Yes |
| Token counts | No |
| Interrupts reported directly | Yes |
Known limitations
- Tool start and approval events are not collected: Cursor's pre-execution hooks can block or auto-approve actions, so runmarq does not register them.
- Cursor does not document which shell runs hooks on Windows. Verify the integration after setup.
- Project hooks run only in trusted workspaces. Integrated-terminal commands you run yourself are not agent activity and are not tracked.
- Cursor does not write a session transcript runmarq can read, so its runs have no token counts.