Cursor
Status: editor chats are read, and Cursor can be turned on. Cursor Agent CLI chats are detected but not read yet.
Where its history lives
Section titled “Where its history lives”| macOS | Windows | |
|---|---|---|
| Editor chats | ~/Library/Application Support/Cursor/User |
%APPDATA%\Cursor\User |
| Cursor Agent CLI (detected only) | ~/.cursor/chats |
%USERPROFILE%\.cursor\chats |
If you set CURSOR_USER_DIR, Seggo uses that for editor chats.
What Seggo reads
Section titled “What Seggo reads”- Cursor’s chat database (
state.vscdb), opened in place, read-only. It’s never copied and never written.
What it can’t read
Section titled “What it can’t read”- Cursor Agent CLI chats are detected, but not read yet.
- If Cursor is writing while Seggo reads, a few messages can be missed. Bad rows are skipped, never made up.
- Seggo reads Cursor’s databases at most every 2 minutes.
What turning it on changes
Section titled “What turning it on changes”Only after you confirm the preview:
| What | Where |
|---|---|
| Seggo’s MCP entry | ~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json) |
| Rules section | .cursor/rules/seggo.mdc in each chosen project |
Cursor has no session-end hook, so everything relies on the rules section. You can always ask directly: “Save a Seggo handoff for this work.”