The new Windsurf adapter (src/retitle/adapters/windsurf.py) is a thin wrapper over the Cursor adapter, since Windsurf (Codeium) is a Cursor fork. We assumed Windsurf uses the same state.vscdb layout (composerHeaders + composerData) but in its own user-data dir:
- macOS:
~/Library/Application Support/Windsurf/User/globalStorage/state.vscdb
- Linux:
~/.config/Windsurf/User/globalStorage/state.vscdb
- Windows:
%APPDATA%/Windsurf/User/globalStorage/state.vscdb
Need a Windsurf user to validate. Specifically:
- Does that path exist on your machine?
- Run
sqlite3 <db> ".tables" — do you see ItemTable + cursorDiskKV (or something Codeium-renamed)?
- Run
sqlite3 <db> "SELECT key FROM ItemTable WHERE key LIKE '%composer%'" — what comes back?
- After running
retitle once --tool windsurf --session <id>, does Windsurf actually show the new title?
If Windsurf has forked the schema (renamed keys, changed the JSON shape), we need to know — could be a 10-minute fix or a full rewrite. PRs welcome.
The new Windsurf adapter (
src/retitle/adapters/windsurf.py) is a thin wrapper over the Cursor adapter, since Windsurf (Codeium) is a Cursor fork. We assumed Windsurf uses the samestate.vscdblayout (composerHeaders + composerData) but in its own user-data dir:~/Library/Application Support/Windsurf/User/globalStorage/state.vscdb~/.config/Windsurf/User/globalStorage/state.vscdb%APPDATA%/Windsurf/User/globalStorage/state.vscdbNeed a Windsurf user to validate. Specifically:
sqlite3 <db> ".tables"— do you seeItemTable+cursorDiskKV(or something Codeium-renamed)?sqlite3 <db> "SELECT key FROM ItemTable WHERE key LIKE '%composer%'"— what comes back?retitle once --tool windsurf --session <id>, does Windsurf actually show the new title?If Windsurf has forked the schema (renamed keys, changed the JSON shape), we need to know — could be a 10-minute fix or a full rewrite. PRs welcome.