// GUIDES
Claude Code and Codex CLI guides
I built Claude Code and Codex Assist because I kept losing track of what the CLI had done the day before. These guides are the notes from that: where the session files are, how to get an old session back, how much the tokens cost, and which extensions I'd actually install. Each one says when it was last checked, because the CLIs change often.
Guide
Claude Code weekly limit and 5-hour limit, explained
How the Claude Code weekly limit and 5-hour session limit work on Pro and Max, when each resets, how to check what's left, and what to do at the limit.
How-to
How to undo Claude Code changes (rewind, git, recovery)
Undo Claude Code changes with /rewind checkpoints, git and VS Code Local History, and recover files a Bash command deleted. Covers Codex CLI too.
Guide
Where Claude Code stores conversations (and why they vanish)
Claude Code saves each session as a JSONL file in ~/.claude/projects and deletes it after 30 days. Exact paths per OS, the file format, and how to keep them.
Roundup
Best Claude Code VS Code extensions in 2026
The Claude Code VS Code extensions worth installing in 2026, grouped by job, with install counts and update dates checked on 1 October 2026.
Comparison
CCAssist vs ccusage: which Claude Code usage tool?
ccusage is a free CLI for Claude Code and Codex usage reports; CCAssist puts usage beside chat history and diffs in VS Code. Tested side by side on one week.
Feature guide
Claude Code usage tracker: tokens, cost per day, quota
How Claude Code usage is measured: the four token fields in each session file, how cost estimates use API prices, what /usage shows, and a daily cost script.
Feature guide
Codex CLI history: find, resume and read old sessions
Where Codex CLI keeps session history, how codex resume and codex fork find it, jq one-liners for rollout files, and viewing it all in VS Code.
How-to
How to view Claude Code chat history
View Claude Code chat history: claude --continue, --resume and the /resume picker, jq one-liners for the JSONL files, and searching every project in VS Code.
Short version: where the history files are
Claude Code keeps one JSONL file per session in ~/.claude/projects/<project>/. Codex CLI keeps them in ~/.codex/sessions/YYYY/MM/DD/. Nothing is encrypted or uploaded, they are just text files, so you can grep them yourself if you don't want an extension. The how-to guide covers both layouts and the--resume pickers if you only need to get back into yesterday's session.