Cursor OpenSync Plugin: What it can and cannot track #22
waynesutton
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We shipped a sync plugin for Cursor IDE. It works, but has limitations compared to our other plugins.
What the plugin does
cursor-opensync-pluginsyncs your Cursor agent sessions to the OpenSync dashboard. You can review prompts, responses, file edits, and tool calls after a session ends.Setup configures hooks in
~/.cursor/hooks.json. Sessions sync automatically after that.What it captures
The plugin uses Cursor's hooks system (available in 1.7+). It observes these events:
beforeSubmitPrompt: your promptsafterAgentResponse: assistant text responsesafterFileEdit: file modification diffsbeforeShellExecution: shell commandsbeforeMCPExecution: MCP tool callsstop: session completionWhat it cannot capture
Token usage, cost data, and model information are not available through the hooks API.
Why the difference
Codex CLI, Claude Code, and OpenCode store complete session data in local files (JSONL or SQLite). Their sync plugins read these files directly and extract everything.
Cursor's hooks API provides event payloads but does not expose:
Cursor has an Analytics API and AI Code Tracking API, but those are Enterprise only and provide aggregated team metrics, not per-session data.
What you get
A searchable history of your Cursor sessions including:
This is useful for reviewing past work or searching across sessions. It does not replace Cursor's built-in usage tracking for cost monitoring.
Links
Feedback
Open an issue on GitHub if you run into problems or have suggestions.
Beta Was this translation helpful? Give feedback.
All reactions