Search your history
Start with words
Type what you remember. Search covers prompts, replies, tool arguments, tool output, file contents an agent read, and files you edited by hand mid-run.The four worth learning first
is:error — every failure, and above the results the same failure grouped across
runs. The fastest way from “this keeps breaking” to “it broke here, 13 times.”
project: — scope to one repo. Matches a fragment, so project:turnlog is enough.
after: / before: — plain-word dates. after:7d, after:today, after:yesterday,
or an ISO prefix like after:2026-06.
like:<session-id> — “have I solved this before?” The other sessions that talk about
what that one talks about, its own resume chain excluded.
Narrowing without knowing the grammar
Run a search, then click the refine chips under the result count. They show what your current results actually contain — agents, branches, tools, kinds, projects — and clicking one appends the right operator. A dimension with a single value is not offered.When words fail
You remember a fragment, not a word. Build the opt-in deep-search index (health card → Maintain), then flip words | inside words.eWebSock finds useWebSocket.
You remember the file, not the phrase. path:useWebSocket.ts finds every session that
touched it; the Files screen then reads every change to it in order.
You remember roughly when. Flip to the timeline — the full match set on a time axis,
one marker per session.
You remember the branch. branch:feature/auth — every agent’s work on that branch.
Exact match, so branch:main never drags in main-experiment.