Claude Code and Codex Assist
Browse Claude Code and Codex sessions, view file diffs, track token usage & costs.
Is this your product? Claim it to edit the listing, post updates and answer questions. Prove it with an email address at the product's domain (the listing becomes Claimed), or put the LotsDirectory badge on your website (the listing becomes Verified, and its link to your website is followed while the badge is live).
Description
Browse Claude Code and Codex sessions, view file diffs, track token usage & costs. Advanced analytics and workflow tools for AI-assisted development.
About Claude Code and Codex Assist
What is Claude Code and Codex Assist?
Claude Code and Codex Assist is a local IDE extension for managing, browsing, and analyzing AI coding sessions. It supports Claude Code, Codex, OpenCode, Grok, and Copilot across VS Code, Cursor, and Antigravity.
What Claude Code and Codex Assist does
The extension provides session management, code tracking, and analytics directly inside the editor sidebar. It automatically detects local session directories and organizes conversation histories by project and model. Users can review file diffs with syntax highlighting, undo or reapply file changes with a single click, and follow a file history timeline that connects prompts to specific code modifications. The tool includes token breakdown tracking by input, output, and cache categories, alongside live quota burn-down projections and status bar indicators. In addition, an embedded local MCP server exposes session history to local coding assistants, and sessions can be converted between Claude and Codex formats or exported to Markdown.
Who Claude Code and Codex Assist is for
It is built for software developers using AI coding assistants like Claude Code, Codex, OpenCode, Grok, and Copilot in VS Code, Cursor, or Antigravity who need local session history and token tracking.
How Claude Code and Codex Assist works
The extension executes locally using WebAssembly without sending chat text or diffs to external servers. It reads local directories including ~/.claude/projects/ and ~/.codex/sessions/ to parse transcripts, calculate token costs, and render diff views in the IDE sidebar.
Key features
- Multi-assistant session browser supporting Claude Code, Codex, OpenCode, Grok, and Copilot
- GitHub-style diff viewer with syntax highlighting and one-click undo or reapply
- File history timeline displaying sessions and prompts that modified active files
- Format converter between Claude and Codex session formats
- Session archive saving full-fidelity transcripts from CLI auto-cleanup
- Token and cost tracking breaking down input, output, cache read, and cache creation tokens
- Local MCP server providing session history endpoints to local AI agents
- Status bar indicators displaying quota percentages and reset countdowns
Pricing
As listed on ccassist.dev, checked 14 October 2026. Prices can change; see the site for current terms.
- Free: $0 forever with 7-day session history, 3-day search limit, same-day diffs, and up to 2 devices
- Pro Monthly: $4.99 per month with unlimited history, unlimited diffs, session forking, and up to 5 devices
- Pro Lifetime: $49.99 one-time payment with all Pro features and lifetime updates included
- Team: Custom per seat volume pricing from 5 seats with single invoice and priority email support
Facts from ccassist.dev, checked 14 October 2026
Written from Claude Code and Codex Assist's own website (Homepage). The maker can claim this listing to edit it.
Categories
Frequently asked questions
Which editors and platforms are supported by the extension?
The extension supports VS Code, Cursor, and Antigravity across Apple Silicon Macs, Windows, and Linux.
Does the extension send chat or code data to external servers?
No. All processing runs locally on the machine using WebAssembly, reading local assistant folders without external transmission.
Which AI coding assistants are supported?
It supports Claude Code, Codex, OpenCode, Grok, and Copilot.
What does the local MCP server do?
The local MCP server exposes local session history so connected assistants can search sessions, retrieve context, and inspect changes.