Signal, not pixels
Bolt builds memory from lightweight OS signals (the app you were in, the file you touched, what you searched), not a full-screen video recorder churning in the background. Orders of magnitude lighter, and far less to leak.
Bolt · Recall
Memory that works for you, without watching your screen.
Everyone wants an assistant that remembers what they were doing. Most of them record your screen to get it. Bolt builds private working memory from lightweight on-device signals instead, distilled into session cards and a local entity graph, encrypted, and never uploaded. Then it feeds the AI you already use, so 'what was I doing' turns straight into 'here's the next action.'
How Bolt remembers
Four principles that make recall safe to turn on.
On-device signals
Content encrypted at rest
Never uploaded
Masked at the AI boundary
Distilled, not raw
You get understanding, session cards and a local entity graph, instead of an endless scroll of screenshots to hunt through. Recall answers 'what was I doing' and 'what comes next', not just 'find the frame'.
Local and encrypted
Memory lives on the device and is never uploaded. Memory content is encrypted at rest; titles, short facts, names, dates, file paths and URLs stay readable on the device so recall can search them, and full-disk encryption covers them. If Bolt cannot save its key, content is stored unencrypted with a logged warning. Raw signals age out on a short TTL. Nothing is indexed in someone else's cloud.
Consent you control
Pause it, scope it, or forget it, anytime. And because recall feeds the same AI you already use, anything model-bound is masked at the boundary first.
How it compares
Recall without the screen recorder.
Screen-recorder recall (Rewind, Microsoft Recall, LittleBird)
Capture the whole screen (as images or text) into a large personal index, often cloud-assisted. Powerful, but heavy, and a rich new target the moment it exists.
Bolt recall
Captures distilled signals on the device, keeps them encrypted and local, masks anything sent to a model, and wires the memory directly into the governed AI actions you already take, so recall becomes action, not just search.
Where it is today
Shipping honestly.
We tell you exactly what the build you run does.
- Text-based recall is live in the desktop build today Session cards, search, an on-device entity graph, and a "coming up" view.
- A visual timeline you can scrub is on the roadmap
A memory you'd actually trust on your work machine.
See recall alongside Bolt's governed agents, boundary masking, and offline daily-driver tools.