L2Cache — stop burning your Claude Code limit on cold resumes. Developer memory for Mac.

Resuming a Claude Code session after its cache expires reloads the whole context at 12× to 80× the cost. L2Cache warns you first and starts you fresh with a handoff, so your weekly limit can last.

Built for your entire coding day. From morning ramp-up to evening wrap-up.

  1. 09:00 · Morning

    “Where was I?”

    Yesterday's sessions, branch and next step, ready to resume.

  2. 11:00 · Hit an error

    “Just fix this.”

    Copy the error or screenshot and keep typing. Your agent's next prompt already has the full trace.

  3. 13:30 · Cache alert

    “Will resuming this cost me?”

    Resuming an expired session can cost up to 80× more. L2Cache flags cold caches before they burn your weekly limit.

    Why →
  4. 15:00 · New task

    “Didn't I work on this ticket before?”

    Search past tickets with their prompts, branches, commits and time spent.

  5. 18:00 · Wrap up

    “Fill in my timesheet.”

    Hours per ticket and a standup, built from your actual work.

Free download · 15-day Pro trial · macOS 13 or later · Local-first: your history lives on your Mac, and you choose what's captured.

Live demo. Click around the app to explore L2Cache.

Today

Your morning starts with context, not archaeology.

Open L2Cache and Today shows the last thing you were doing in every project: what you asked your agent, what it finished, and the one step that comes next.

More about TodayLess about Today
  • You were working on.The goal of your last agent session, in your own words.
  • Last update.What the agent reported before you stopped.
  • Resume.Reopen the session in the agent you were using, in one click.
  • Needs attention.Failed runs, unpushed commits and branches pushed but never merged.
L2Cache — Developer HomeCache expired · 254k cold
● Developer Home ✦ Weekly Brief ☰ Copy standup
5commits
4agent sessions
5milestones this week
0need attention
Pick up where you left off‹ Tue, Nov 10 ›
NI✳
Query parser refactorClaude Code · Nimbus
⏱ 254k⚡ Expired

A fresh session could save you from carrying unnecessary context.

Your previous context cache has expired after 55 min idle. Continue with a focused handoff instead of reloading the entire conversation.

🌡
CURRENT SESSION
254k
Cache expired · 55 min idle
⚡
FRESH + HANDOFF
52k
Estimated starting context
Alternative: ⧉ Copy /compact Command
SESSION RECAP4 minutes ago
● Last user requestAdd zero-copy buffering to parser and fix benchmarks
✦ Last agent actionBuffer reuse implemented; 1 parser benchmark still fails
⑂ Commit7f2a9d1 not pushed perf(parser): reuse buffer across chunk boundaries
Recap ›⑂ dev/query-parser✳Copy resume command
RE
Relay
yesterday

Upgrade stripe-node to 17.2 and fix whatever breaks.

LU
Lumen
2 days ago

Get the homepage launch-ready: hero copy, OG images and a sitemap.

AT
Atlas
4 days ago

Merge the streaks branch, bump to 1.3.2 and draft App Store release notes.

Proactive token savings

Stop paying to reload old context.

Long agent sessions cost more with every turn, and resuming one after its prompt cache has expired reloads the whole context instead of reading it from cache. L2Cache shows where each session stands and warns you first.

The pickup card in L2Cache, with example data.

~/Projects/Atlas — claude
~/Projects/Atlas $ claude --resume Resumed "Auth token retry" · idle 9 h ❄ Cache expired · next message reloads 241k /clear → fresh with handoff · 47k > fix the concurrency race in AuthRetryTests ✋ Held · /clear, or ↑ Enter to send > /clear ✓ Fresh with handoff · 47k · cache warm
Example data
  • Before it expiresA heads-up

    A menu-bar badge when a heavy session's cache is about to go cold.

  • While you're awayKeep it warm

    One short heartbeat keeps a 1-hour cache alive.

  • After it expiresThe costly message, held

    Your first message waits once. /clear starts fresh with a handoff.

Your weekly limit, to the last day. Act on these warnings and the reloads that quietly eat your plan stop happening, so your weekly limit can last until it resets.

For Claude Code, with L2Cache hooks on. Read from session files on your Mac. Nothing is sent anywhere. How the cold resume guard works

What's inside

Never start from zero again.

Every part of L2Cache gets you back to where you were, faster. Open any tile to see it working.

1 / 8

Today

Your morning starts with context, not archaeology.

Open L2Cache and Today shows the last thing you were doing in every project: what you asked your agent, what it finished, and the one step that comes next.

L2Cache — Today
AT✳
Auth token retryClaude Code · Atlas
◔ 241k⚡ 49m

Cheap to continue for 49 min.

After that, the next message reloads all of it.

Current session
241k
Cached · 49 min left
⧉ Copy /compact command·✦ Start fresh with handoff
Session recap8 minutes ago
Last user request
Background refresh still logs people out on a 401. Handle it, then get AuthRetryTests green.
Last agent action
Background refresh handles 401s; one concurrency test still fails.
Commit
7b2a7f4 not pushed Handle 401 during background refresh
Full history › ⑂ fix/ATL-142-auth-retry ✳Copy resume command
Example data
  • You were working on.The goal of your last agent session, in your own words.
  • Last update.What the agent reported before you stopped.
  • Resume.Reopen the session in the agent you were using, in one click.
  • Needs attention.Failed runs, unpushed commits and branches pushed but never merged.

Coding agents

Your coding agents finally have a history.

Every agent keeps its sessions in a different place and format. L2Cache reads your Claude Code session history and Codex session history, plus Copilot, Grok Build and Antigravity, from your Mac and lays it out by project and branch. A conversation from last Tuesday is a search away, and you can resume Claude Code or Codex right where it stopped.

Session history from
  • Claude Code
  • Codex
  • GitHub Copilot
  • Grok Build
  • Google Antigravity
L2Cache — Coding Agents
Today
Auth token retry
✳241k · 2h 10m warm
Shell completions
◎41k · 35m done
Yesterday
Stripe-node 17.2 upgrade
✳88k · 1h 05m cold
Homepage launch ready
✳63k · 50m cold
Auth token retry ⑂ fix/ATL-142-auth-retry 3 files 2 commits
Background refresh still logs people out on a 401. Handle it, then get AuthRetryTests green.
I'll update the refresh handler to retry once on 401 before revoking the session.
✎Edit Sources/Atlas/Auth/TokenManager.swift +38 −6
✎Edit Tests/AtlasTests/AuthRetryTests.swift +44 −2
›Bash swift test --filter AuthRetryTests 1 failed
Add the concurrency test too so we don't race in-flight refreshes.
Background refresh handles 401s; one concurrency test still fails.
⑂7b2a7f4Handle 401 during background refreshnot pushed
Example data
  • Resume.Copy or run the resume command for a supported session. The agent's CLI and the original session need to be available.
  • Handoff.Live capture and session handoff for Claude Code, Codex, GitHub Copilot and Grok Build.
  • Plans and skills.Browse plans from Claude Code and Antigravity, and installed skills and their use from Claude Code and Codex.

Available details and live-continuity features vary by agent.

Context & cost

Know before a session gets expensive.

Long agent sessions cost more with every turn, and resuming one after its prompt cache has expired reloads the whole context instead of reading it from cache. L2Cache shows where each session stands and warns you first.

L2Cache — Today
AT✳
Auth token retryClaude Code · Atlas
◔ 241k❄ Cold cache

A fresh session could save you from carrying unnecessary context.

Your previous context cache has expired. Continue with a focused handoff instead of reloading the entire conversation.

Current session
241k
Cache expired
→
⚡
Fresh + handoff
47k
Estimated starting context
✦ Start Fresh with L2Cache Handoff
~/Projects/Atlas — claude
~/Projects/Atlas $ claude --resume Resumed "Auth token retry" · idle 9 h ❄ Cache expired · next message reloads 241k /clear → fresh with handoff · 47k > fix the concurrency race in AuthRetryTests ✋ Held · /clear, or ↑ Enter to send > /clear ✓ Fresh with handoff · 47k · cache warm
Example data

Pickup card See where a session stands

Size and cache state on every session.

  • Context at a glance. Each Claude Code and Codex session shows its context size, marked Light, Heavy or Very heavy, and whether its prompt cache is still warm.
  • Start fresh or compact. One click copies a handoff for a fresh session, or a /compact command with a focus line you can edit.
  • Where your tokens go. A breakdown of your agents' token use, with cache advice based on your own cache misses.
  • Your context audit. Setup shows your cold resumes from the last 30 days, counted in tokens.

Read from your agents' session files on your Mac. Nothing is sent anywhere.

Warnings L2Cache tells you first

A heads-up before the cache goes cold.

  • Cache expiring soon. A menu-bar badge and a row at the top of the quick panel when a Very heavy session's cache is about to expire, plus a macOS notification if you turn it on.
  • Keep warm. For a Heavy session on a 1-hour cache, L2Cache offers a short heartbeat you can send to keep it warm.
  • Cold resume guard. Resume a session whose cache has expired and the terminal warns you before your first message, then holds that costly message once. Type /clear to start fresh with a handoff, or press ↑ and Return to send it anyway.

For Claude Code. Terminal warnings need L2Cache hooks turned on. Everything here is on by default except macOS notifications, and each can be turned off in Settings.

For your coding agents

Your agents can ask L2Cache, and L2Cache briefs them.

Two optional connections, one in each direction: agents look up what you copied or captured, and every session starts with the context it needs.

MCP server Agents ask L2Cache

Agents look up your context.

No more copy-pasting. Claude Code, Codex, Cursor, and Antigravity query your clips, past error fixes, and session history directly.

  • search_clips
  • get_clip
  • get_error_resolutions
  • get_session_summary
  • search_screenshots
  • search_agent_history

Works with Claude Code, Claude Desktop, Codex, Cursor and Antigravity. Queries run on your Mac, and sensitive items such as passwords and keys are never returned.

Hooks L2Cache briefs your agents

Every session starts briefed.

  • Recent clipboard. Last 30m of clips ride along with prompt #1.
  • Session handoff. Pick up right where your last agent stopped.
  • Fixes remembered. Solved errors are saved for the next run.
  • Cold resume guard. Warns before your first message to a session whose cache has expired.

For Claude Code, Codex, GitHub Copilot and Grok Build. You turn each agent on in Settings; nothing is installed until you do.

Projects & Worklog

Every project keeps its story.

Commits, branches, agent sessions, test runs and releases line up on one timeline per project, so you can see how the work got here, not just where it is.

  • Project Story. A commit graph and timeline read straight from .git. L2Cache never runs Git for you.
  • Milestones. Each piece of evidence is labelled Git verified, Test verified, You noted, or L2Cache inferred.
  • Worklog. Tickets you worked on and approximate hours per day, which you can correct and copy into your timesheet tool.
  • Weekly Brief & standup. An editable standup built from your recorded activity.
L2Cache — Projects › Atlas
AT
Atlas~/Projects/Atlas
✳Copy resume command
✓
RecommendedTest failing after 7b2a7f47b2a7f4 Handle 401 during background refresh
✳Ask Claude to fix
● Work at risk 3 commits only on this Mac
7b2a7f4Handle 401 during background refresh
d4844adAdd AuthRetryTests for expired tokens
0167140Retry token refresh once (ATL-142)
● Last known good Tests passed at b6afd48 · 4 days ago
✓48 passed
b6afd48Bump version to 1.3.2
+ 4 commits since
BlockedATL-142 auth retry — tests failing3 h ago
ReleasedTagged v1.3.24 d ago
MergedATL-131 streaks — merged4 d ago
L2Cache — Worklog › Timesheet
This week2.75 h
Tickets3
On tickets82%
WorkMonTueWedThuFriTotal ATL-142Blocked–0.250.750.5–1.5 LUM-31In progress––0.5––0.5 ATL-131Merged0.25––––0.25 Other work · Relay––0.5––0.5
Example data

Clipboard

A programmable clipboard.

Copy anything and L2Cache recognises it: code, JSON, SQL, URLs, colours and more. The right actions appear next to your cursor, and every clip is filed under the project it came from.

  • Smart bubble. Copy, and a bubble with the best action pops up at your cursor. Open it for every action for that type.
  • Your own actions. Add shell scripts or AI prompts as custom actions, shown for the clip types you choose.
  • By project, pinned. Clips land in the project they came from. Pin the ones you reuse.
L2Cache — Clipboard
⌕ Search clipboard…
All projectsAtlasRelayLumenNimbus
Pinned
</>
Coalesce in-flight token refreshCodefunc refresh() async throws -> Token {
2h ago
Recent
{ }
Session payloadJSON{"user":"sam","token":"sk_live_…","roles":["admin"]}
Just now
›_
Install zsh completionsCommandnimbus completions zsh > ~/.zfunc/_nimbus
4h ago
UUID
Test user id9b1d2f4e-6a0c-4f7b-9d2e-31c5a8e7f0b6
6h ago
!
Refresh token revoked errorAuthError.refreshTokenRevoked: the refresh token was revoked
23h ago
↗
github.comhttps://github.com/alexrivera/lumen/pull/31
Yesterday
Example data

Terminal

Every command, with its exit code.

Your shell history stops being one long list. Every command is grouped by day, filed under its project and marked with how it ended.

  • Exit codes at a glance. See which runs passed and which failed, and when.
  • Your shell and your agents. See the commands you ran, the ones your coding agents ran, or both.
  • By project or tool. Filter to one project, or to one tool such as git or xcodebuild.
L2Cache — Terminal
⌕ Search commands…
My ShellAgentsAll
Today
xcodebuild test -scheme Atlas -only-testing:AtlasTests/AuthRetryTestsRun AuthRetryTests
× 651:21 PM
git diff --stat main...fix/ATL-142-auth-retry
✓12:45 PM
cargo clippy -- -D warnings
✓10:45 AM
Yesterday
npx tsc --noEmitType-check after the Stripe upgrade
× 210:51 AM
npm run dev -- --port 4321
✓8:51 AM
Example data

Privacy

Local-first, by design.

Your history lives in L2Cache's database, on your Mac, and its smart features run there too.

On your Mac

  • History databaseSessions, commands, Git activity, clips and screenshots
  • Apple IntelligenceOn-device, where your Mac supports it
  • OllamaA local model you run yourself
  • Rule-basedWorks with no AI provider at all
  • You choose what's captured. Exclude apps and pick the folders L2Cache indexes.
  • Read, don't run. L2Cache reads your .git files and agent logs. It doesn't run Git or your agents to do it.
L2Cache App Icon

Try everything free for 15 days.

$9.99 Black Friday special · $19.99 regular · one-time unlock
  • Clipboard history 100% free forever
  • 15-day unrestricted Developer Pro trial
  • Pay once, own forever
  • Regional pricing in your local currency
  • No subscriptions, no cloud accounts
Download on the Mac App Store

Requires macOS 13 or later. Fully functional 15-day Pro trial starts on first launch.

Frequently asked questions

What is L2Cache?

L2Cache is developer memory for Mac. It connects your projects, coding-agent sessions, terminal history, Git activity, screenshots and clipboard content, so when you come back to your Mac you can see where you left off and resume the work.

Is L2Cache a clipboard manager?

It includes one. L2Cache started as a clipboard manager and still has searchable clipboard history with smart actions, opened with the ⌘⇧V quick panel. Version 2.0 adds the Developer Home, which brings clipboard, terminal, Git and coding-agent history together by project.

Which coding agents does L2Cache read history from?

L2Cache reads local session history from Claude Code, Codex, GitHub Copilot, Grok Build and Google Antigravity. Available details and live-continuity features vary by agent.

Can I resume a Claude Code or Codex session from L2Cache?

Yes. L2Cache generates the resume command for supported sessions and can open it in your terminal. The agent's command-line tool and the original session must still be installed and available on your Mac.

Can my coding agents use L2Cache directly?

Yes. Connect the L2Cache MCP server and agents such as Claude Code, Codex, Cursor and Antigravity can search your clipboard history, screenshots and saved folders themselves. Optional hooks for Claude Code, Codex, GitHub Copilot and Grok Build share your recent clipboard items and the previous session's context with each new session. Agents can also look up earlier sessions' fixes, decisions and work summaries. Both run on your Mac, and sensitive items are never shared.

Where is my history stored?

Your history is stored locally in L2Cache's database on your Mac. Smart features use on-device Apple Intelligence where your Mac supports it, a local Ollama model, or rule-based processing.

Will L2Cache make my Claude Code limit last longer?

It helps you waste less of it. Anthropic sets your 5-hour and weekly limits, and L2Cache can't raise them. It stops the reloads that quietly eat them: it shows each session's context size and whether its prompt cache is still warm, warns before a heavy session's cache expires, and stops the first message to a cold Claude Code session once so you can start fresh with a handoff instead of reloading the whole context. Works with Claude Code and Codex history; the cold resume guard is Claude Code only.

How much does L2Cache cost?

L2Cache is free to download from the Mac App Store. Clipboard history is 100% free and unlimited forever. Developer Pro features (terminal command history, Claude Code and Codex session continuity, prompt cache guard, MCP server) include an unrestricted 15-day free trial, followed by a one-time Pro unlock ($9.99 Black Friday price ($19.99 regular)). Pay once, own it forever—no subscriptions, ever.

From the blog

Guides for developers working with coding agents.

Read all articles