Claude Code and Codex Assist - Chat History, Diffs & Usage Analytics

Hi Himanshu, I take data-safety reports seriously, so I reviewed every deletion, cache, and subscription path. The headline needs an important clarification: the extension does not delete sessions automatically or because they fall outside the Free-tier window. A source .jsonl file can only enter the deletion path after the user explicitly selects Delete and then agrees to the VS Code warning popup by clicking “Move to Trash.” If you did not initiate Delete and accept that popup, the permanent-unlink fallback could not have run. You correctly identified that, after this explicit confirmation, a failed Trash operation could fall back to unlinkSync. Although it was never an automatic path, permanently deleting after a failed Trash request was unsafe. I have removed that fallback: if VS Code cannot move the file to Trash, the operation now stops and the original remains untouched. Some command names in the bundle also need context: clearProjectCache only clears an in-memory parser cache. clearAllData only clears the extension’s local database. Neither command deletes files from ~/.claude/projects. A confirmed session deletion also attempts to remove that session from the SQLite index; there is no intentional flow that deletes the source while preserving and paywalling the extension’s copy. The Free/Pro limits are explicitly disclosed in the README, Marketplace description, and website. They limit features inside this third-party viewer; they do not delete, move, encrypt, or otherwise restrict the underlying files. History outside the Free window remains in its original location and can still be accessed directly or through the official tools while those source files exist.

Hi Daniel, Thank you for trying this out. Here's what actually happens: - ⁠Chat content never leaves your machine. The extension reads ~/.claude/projects/ and ~/.codex/sessions/ locally and stores everything in a local SQLite database. You can verify with any network proxy (Charles, Proxyman, Little Snitch) — no chat text, file content, or diffs are ever sent. - ⁠⁠What does go over the wire by default: an anonymized device ID, OS/extension version, and aggregated usage counters (e.g. "session opened", "search ran"). Error reports include error messages and stack traces — never chat content. Both are togglable in extension settings (enableErrorReporting, enableUsageStatsSharing). - Leaderboard sharing is off by default and requires explicit opt-in. I have updated the README to mention this now.

Hi Paul, sorry that landed wrong. You're right that the 7-day free history limit wasn't called out clearly before install, and that's on me. I have updated the listing so the free vs Pro split is visible upfront. For context: the extension is free for everyday use (recent sessions, search, diffs, dashboard) and Pro unlocks full history, export and session forking. Pricing and a 7-day refund window are on ccassist.dev — happy to refund within that window if Pro doesn't solve your case. Thanks for the feedback and using this extension.

Thanks for raising this. I want to clarify and correct the record. When the extension was first published, it was mistakenly marked as Apache-licensed. This was an honest mistake on my part — this was my first extension and the first time one of my projects gained this level of usage, and I did not fully understand the licensing differences at the time. This was corrected over a month ago, and the extension is now clearly distributed under a proprietary EULA. There is currently no claim that the source code is open. The extension does not include any malware, crypto-miners, trackers, or obfuscated payloads. It uses only documented VS Code APIs and does not execute arbitrary binaries or external scripts. The VS Code Marketplace also performs automated security checks. I agree users should stay cautious, but implying malware based solely on a past licensing metadata mistake or closed-source status is misleading. If you have any specific technical evidence (API usage, network calls, files, etc.), please share it and I’ll investigate immediately.

Thanks so much for the feedback! If you ever run into other issues or have feature ideas, feel free to reach out - I'm @yashagl on X/Twitter!

Thanks so much for the feedback! If you ever run into other issues or have feature ideas, feel free to reach out - I'm @yashagl on X/Twitter!

Thanks so much for the feedback! Stories like yours are why I keep improving the extension. If you ever run into other issues or have feature ideas, feel free to reach out - I'm @yashagl on X/Twitter!