Repository navigation
[research] Cursor sessions support in Claude Karma — data model + backend feasibility #71
Description
Goal
Investigate whether Claude Karma can ingest and display Cursor IDE sessions alongside Claude Code sessions.
Phase 1 (this issue): backend / data-side research only. No UI work yet.
Questions to answer
- Where does Cursor (currently 2.5.26 on macOS) store session data on disk?
~/.cursor/(we knowprojects/,plans/,ide_state.json,mcp.jsonexist)~/Library/Application Support/Cursor/(electron state, SQLite, backups)
- What is the on-disk format? JSONL like Claude Code? SQLite? Protobuf? Mixed?
- Does Cursor expose conversation / agent / tool-use traces in a parseable way?
- Path-encoding: does Cursor use the same
-Users-...-GitHub-reposcheme that Claude Code does? - Versioning: what does the v2.5.26 data layout look like vs older versions documented online?
- Can we replicate every existing claude-karma API endpoint for Cursor data? Which features map cleanly, which don't?
Current Claude Karma API surface (parity target)
| Capability | Endpoint family | Maps to Cursor? |
|---|---|---|
| Projects list/detail | `/projects`, `/projects/{name}` | ? |
| Sessions detail | `/sessions/{uuid}` | ? |
| Event timeline | `/sessions/{uuid}/timeline` | ? |
| Tool usage | `/sessions/{uuid}/tools` | ? |
| File activity | `/sessions/{uuid}/file-activity` | ? |
| Subagents | `/sessions/{uuid}/subagents` | ? |
| Analytics | `/analytics/projects/{name}` | ? |
| Live sessions | `/live-sessions` | ? |
| Agents | `/agents` | ? |
| Skills | `/skills` | ? |
| File history | `/history` | ? |
Method
- Parallel research agents:
- Local: inventory `
/.cursor/` + `/Library/Application Support/Cursor/` (Cursor 2.5.26 ground truth) - Web: official Cursor docs + community write-ups on session storage
- Cross-check: what docs claim vs what v2.5.26 actually writes
- Local: inventory `
- Gap analysis vs existing claude-karma API endpoints (table above)
Out of scope (deferred to a follow-up)
- Frontend routes / unified multi-IDE timeline UI
- Live-session tracking (Cursor doesn't have our hook substrate)
- Hook integration (Cursor lacks Claude Code's 10 hook types)
Deliverable
A research doc at `docs/features/2026-05-13-cursor-sessions-integration.md` with:
- Local data inventory (paths, formats, sample shapes) for Cursor 2.5.26
- Proposed Pydantic model mapping (Project → Session → Message)
- Parity matrix (table above, filled in)
- Viability verdict: "yes, full parity" / "partial, with these caveats" / "no"
- Recommended next steps (or kill decision)
Activity
docs: lock cursor sessions architecture (Option C) + scope adjustments (
feat(db): v11 migration — Cursor session support tables + 3-tuple ses…
feat(cursor): parsers + indexer for Cursor 2.x session ingestion (#71)
feat(cursor): router dispatch for /projects + /sessions/{uuid} (#71)
docs: status update — Cursor backend phase 1 of 2 complete (#71)
feat(cursor): remaining 5 endpoints + 48 tests = Cursor backend v1 co…
fix(cursor): code review follow-up — migration atomicity + epoch tz +…
test(cursor): MCP overview aggregation coverage + final status (#71)