Omniscio

Session recall (agents search their own project's past sessions)

Session recall lets your agents remember how a problem was solved before. An agent can search this project's past sessions, read the lines around what it found, and get a short summary of the closest sessions. Passwords and keys are hidden, other projects are never searched, and anything found is treated as history, never as instructions. It is in development, so it is off by default.

On this page

What it is

Agents start every session from scratch, so they often work out again something a session last week already worked out. Session recall gives them a safe way to look back: the same project's own past sessions, searched by the app on the agent's behalf, with the app — not the agent — deciding what it may see.

It is different from the two other "search your sessions" features:

  • Session Search is for you: you ask in the sidebar, and a search agent looks through every project.
  • Transcript recall lets a session search its own full transcript after a compaction.
  • Session recall lets an agent search the other past sessions of its own project.

Where to find it

  • Turn it on: Settings → Lab → Sessions & agents → Session recall.
  • Tune it: Settings → Session recall (search Settings for "recall"): whether summaries are made, and the daily limit for them. See Session recall settings.
  • What it cost: Stats → Spend, under Session recall, attributed to the session that searched.
  • The skill: while it is on, the bundled recall-past-work skill is installed for your agents, and copied to Codex, Gemini and Hermes along with your other skills.

How it behaves

What an agent can find

  • Only sessions in the same project as the searching session, and never the searching session itself.
  • Never a deleted session or a Clean Room session.
  • Never a session started by email, by an intake (bug, GitHub, Sentry, email or in-app reports), by another agent (crew members and other agent-spawned sessions) or by an automation rule. The app uses one shared rule for this everywhere, and when it cannot tell, it treats the session as one of these.
  • Those same sessions cannot search either.

What comes back

  • Matching lines — up to 30 per search (10 by default), each a short excerpt around the match, with passwords, keys and tokens hidden and any planted "instructions" defused.
  • Summaries — for the three closest sessions, a summary of at most 80 words from the background Utility model, describing what that session did that answers the question.
  • Each summary says what happened to it: made (ok), switched off (off), no usable AI key (no-key), today's limit reached (capped), too slow (timed-out), failed (failed), or withheld because it looked unsafe (flagged). The matching lines come back either way.
  • Reading around a hit — the lines just before and after it, in order, with a way to page further.

Cost and limits

  • Summaries have their own daily limit, $0.50 by default (from $0.10 to $100), separate from every other feature's. Once it is reached, no more summaries are made that day; searching still works.
  • A summary is cached for 24 hours for the same question and session; a new message in that session makes it fresh again. A cached summary costs nothing.
  • Each session may search 30 times in 10 minutes; reading around a hit counts as a quarter of a search.
  • Searches run off the app's main thread, so a busy search answers "try again" rather than slowing the app down.

Privacy and safety

  • Every line is masked before it leaves the app, and the summary model is told the lines are history to describe, never instructions to follow. A summary that carries a secret or planted instructions is dropped.
  • Every search and read-around leaves an entry in the app's access log, naming the searching session and the session it read.

Turning it off

Switching Session recall off stops every search at once: both routes answer "Session recall is switched off", nothing is searched, nothing is spent, and the skill is removed from your agents on the next skill sync. Switching summaries off keeps searching but stops all summary spend.

Last verified 2026-10-28