Claude Code and Codex Assist
A VS Code extension that shows every Claude Code and Codex session, which prompt changed each file, and your quota
Developer Tools·AI & Machine Learning
What is Claude Code and Codex Assist?
Claude Code and Codex keep every session in JSONL files that nobody reads, and Claude Code deletes them after 30 days. Claude Code and Codex Assist is a VS Code extension that turns them into a history you can use.
It lists every session from Claude Code, Codex, OpenCode, Grok, Copilot and Cursor in one place, grouped by project with the cost of each folder. The File Timeline shows every prompt that edited a file, with the diff, so you can see which conversation changed what. Each turn's edits can be undone or reapplied in one click. Search covers prompts, replies, tool output and subagents, with regex. Quota cards show your 5-hour and weekly limits live and project when you'll run out.
Works in VS Code, Cursor, Windsurf, Antigravity and Trae. Runs locally, no account needed. Free for the last 7 days of history; Pro is $4.99/month or $49.99 lifetime.
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch Now
FounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
I didn't build any product, I didn't have anything. I just had a glimpse of what a product can look like in a landing page, and people were signing up from left and right.
Ship a landing page first — let strangers prove demand before you write code
Real validation comes before the product, not after. Ship a landing page that shows what the tool could look like, then watch whether strangers sign up unprompted. Signups from a page alone are the green light to actually build.
we still track like how often because I think should never say never right you should leave your doors open we always said like we're not doing the chatbot right and now here we are in like 2024 like maybe it makes sense for eventually for us to actually have a chat bot even though for years we're like we're not doing that that's like out of scope
Track every "no" so the tipping point becomes visible later
Out-of-scope feature requests don't get built, but they do get logged. Counting how often a request lands gives a tipping-point signal — what felt obviously off-scope (a chatbot) eventually becomes obviously core as the market shifts. Saying no today without locking the door shut tomorrow keeps optionality cheap.
There's a play for whatever you're stuck on.
Read all 2722 playbooks