Return to a debugging thread
Search for the error message, API name, or hypothesis you discussed before reopening the relevant work.
Claude Code · session history
Search Your Claude Code Session History
“Which Claude Code session was I debugging this issue in?” The answer may be in a local transcript from another project or a session you worked on last week. L2Cache lets you browse and search supported Claude Code session history on your Mac, so earlier investigation and decisions are easier to find again.
Find the conversation that contains the missing context
Claude Code’s built-in resume flow is useful when you know which project or session to continue. When you only remember the bug, filename, or question, searching local session history helps you discover the right conversation first. L2Cache presents supported session records in a searchable interface with project and session context.
Recover a project decision
Find the session where you compared an implementation, traced a regression, or settled on a design.
Keep agent work in context
Claude Code and Codex session history sit alongside terminal commands and clipboard items in one native Mac app.
Session discovery and resuming work
L2Cache helps with local session discovery and transcript search. When you find the conversation, use the supported resume workflow to continue it in Claude Code. The exact resume command and transcript locations can change with Claude Code releases; our guide explains the current local files and CLI options.
Agent history can also include token telemetry and prompt/cache information where those fields are available in the local session data. It is a view of the records produced by the tools, not a claim that every session exposes the same metrics.
Read How to Track & Resume Claude Code Sessions on Mac for the file locations, resume commands, and current workflow details.
Local developer history, together
Claude Code sessions are only one part of a debugging trail. You might also need the kubectl command you ran or the cURL request you copied. L2Cache brings supported Claude Code and Codex history together with terminal and clipboard history. The local records stay on your Mac; L2Cache does not turn them into a cloud search service.
See how this compares with searching Codex CLI history, or explore the developer clipboard manager.
Pick up where the previous session left off
Use session search to locate the relevant conversation, inspect its project context, and continue through Claude Code’s supported resume flow. For details about stored transcripts and available commands, follow the step-by-step guide.