Switching from cursor to cc on the same project is brutal. spend 20 mins re-explaining architecture and why we ditched that one approach. CLAUDE.md helps but its manual. was about to write a script to parse cursor’s state.vscdb and dump it into a rules file. turns out Memmy already does this. reads state.vscdb, claude code’s JSONL, codex rollout history (and a few others). scan is read-only, does secret redaction before hitting the local sqlite. https://github.com/memmy-ai/memmy cursor: Reads state.vscdb directly claude code: Parses .jsonl session logs codex: Extracts rollout history (plus a few other local formats) still testing recall accuracy and cross-project bleed but the idea of recovering old agent history instead of starting fresh is pretty solid a few technical details that made me actually trust runningit. zero risk of mutating or corrupting your existing tool configs. Strips api keys, tokens, and env variables before touching storage and dumps everything into local sqlite, so your code history stays on your machine and out of 3rd-party clouds. still testing recall accuracy and cross-project bleed but the idea of recovering old agent history instead of starting fresh is pretty solid. submitted by /u/Silk_song11
Originally posted by u/Silk_song11 on r/ClaudeCode