Revisit a code change
Search for the module or test name involved in a past implementation and recover the reasoning around it.
Codex CLI · session history
Search Your Codex CLI Session History
“What did Codex change when we fixed that test?” The session may be in a date-based rollout file from a different project. L2Cache helps you browse and search supported local Codex CLI history, so you can recover the conversation and context behind earlier work.
Find the session from the detail you remember
You may remember a failing test, a filename, or the instruction you gave Codex, but not the session ID or date. A Codex history viewer makes those local sessions easier to discover and search than opening rollout JSONL files one by one.
Recover debugging context
Look up a compiler error, command, or hypothesis from an earlier Codex CLI session.
Continue the work
After finding the relevant session, use Codex’s own resume workflow where supported by your installed CLI.
Codex history in your Mac developer workflow
L2Cache supports local Codex session discovery and search. Session files can include prompts, assistant responses, and tool activity; available details depend on the local records and Codex version. L2Cache complements the Codex CLI rather than replacing its own resume commands.
Read How to view and search OpenAI Codex CLI sessions for the local session layout, built-in resume command, and ways to inspect rollout files.
Claude Code, Codex, terminal, and clipboard history
Agent work often spans more than one tool. The earlier session may mention the terminal command you need, or refer to a snippet copied while debugging. L2Cache brings supported Codex and Claude Code history together with terminal commands and clipboard history in one native Mac app, with the underlying history kept locally.
Compare with Claude Code session history and see the broader AI agent history guide.
Search first, resume with Codex
Use L2Cache to locate and inspect the old session, then continue through the Codex CLI’s available resume flow. This makes historical Codex sessions useful even when you do not remember their IDs or exact dates.