← Back to Blog

One ⌘K search for everything you did as a developer

November 9, 2026 · 4 min read

You know you've seen it. The command that finally fixed the build, the error from yesterday's screenshot, the commit that changed the retry logic, the Claude Code session where you worked out the migration. Each one lives somewhere different: shell history, a screenshot folder, git log, an agent's transcript files. So you search four places, or you give up and work it out again.

L2Cache already keeps all of that on your Mac. ⌘K in L2Cache's Developer Home searches it in one go.

What one search covers

Agents, Terminal and Files are part of Developer Pro, which the free trial includes. Clips are always searchable.

Best match first, then grouped

Results don't come back as one long list. When they span more than one kind, the single best match goes at the top as the Top Hit. The rest are grouped by kind, and the group with the strongest match comes first. Each group shows a few rows, with View all to see more.

Ranking mixes how well each result matches (about 70%) with how recent it is (about 30%). Exact title matches and results from the project you've scoped to get a small boost. Matching words are highlighted in each row, so you can see why it came up.

Press ⌘P to open a preview pane beside the list and read a result without leaving the search.

Narrowing it down

Scope pills across the top switch between All, Projects, Docs, Clips, Files, Agents, Terminal and Commits. Tab moves to the next one.

If you'd rather type, start the query with a short token and a space:

Tokens only count at the start of the query and only when a space follows, so a search for c:\Users or git: bump version without the space still works as plain text. Tokens can be combined: @atlas a: token refresh searches one project's agent sessions.

Going straight to the result

Every result opens where it lives, and the keyboard shortcut at the bottom of the window changes to match the selected row:

⌘C copies the selected result and Esc closes the search.

Agent results are the ones that save the most time. Opening one takes you into the session, scrolled to the message that matched, not the top of a transcript that might be hundreds of turns long. If you want to carry on from there, ⌘↵ resumes the session in your terminal.

Before you type

An empty search isn't blank. It shows your recent searches, the results you recently opened, and a short reminder of the search syntax, so getting back to something you looked at an hour ago is one click.

All local

The index is SQLite full-text search (FTS5) on your Mac. Clip search uses stemming, so "retrying" finds "retry". Screenshot and image text is read with on-device OCR. Nothing you search for, and nothing in the index, is sent anywhere.

If you'd rather your coding agent did the searching, the same history is available to Claude Code, Codex and others through L2Cache's MCP server. And for finding screenshots by the text in them, see screenshot search on Mac.

The short version

• ⌘K searches clips, screenshots, agent sessions, terminal commands, commits, files and docs at once.
• The best match comes first, and the rest are grouped by kind.
• Narrow it with scope pills, Tab, or tokens like a:, >, g: and @project.
• Agent results open at the matching message, and ⌘↵ resumes the session.
• Everything is indexed and searched on your Mac.