Know the moment your agent needs you.
Recall shows the Claude Code and Codex sessions that need your approval or have finished their turn, in the tray, in Loops and on Smart Return. Go to session takes you straight to the tab.
Blocked, waiting, done
Blocked
It stopped to ask your permission. It goes first, in amber, and gets one quiet nudge after five minutes.
Waiting
It finished its turn and waits for your next message. It stays in the list and never sends a reminder.
Done
When its closing message says the work is done, Recall can close that loop. Not sure? The row asks: Confirm done or Not done.
To see the moment a session stops for approval, turn on the optional hooks in Settings → Integrations, and remove them any time. Without them, Recall still shows the sessions waiting on you.
One click to the session. The chat comes back too.
Blocked goes first, wherever you look.
- A Codex conversation
- Opens where it runs: the Codex app, or VS Code for the extension
- A session that has closed
- Recall opens Loops → Agents instead
- Move to project…
- Files the session's whole repository under that project, from now on
The chat comes back with your work.
- Up to three chats
- The ones you looked at on that thread, newest first
- A closed Claude Code chat
- Reopens in VS Code or Cursor
- A chat running in a terminal
- Recall never opens a second terminal next to it
Recall MCP, for the AI tools you approve.
Your tools hold the pieces. Recall knows which pieces belonged together. We are exploring a local, read-only MCP server, so an AI tool you approve could start from the thread you are in and the exact file behind the task.
Tools we are exploring
get_current_thread- The project, the thread and what it has open.
get_smart_return- Where you left off, your note, and what Return would reopen.
list_loops- What is waiting on you: people, agents, your notes, unfinished work.
summarize_day- What actually moved today.
search_threads- Find a past thread by what you were doing.
restore_thread- Shows you the restore checklist first. Nothing opens until you say so.
The rules it would follow
- Read-only by default.
- Only the AI clients you approve.
- Local-first, on your Mac.
- Visible permissions.
- Never a raw screen feed.
- Nothing destructive without your confirmation.
Want early access to Recall MCP?
A tool that watches your screen has to earn your trust.
Agent sessions stay on your Mac with the rest of your history. If Recall ever hands context to an AI tool, it will be read-only, and only for the clients you approve.
- What is on your screen stays on your Mac.
- Never the microphone, camera, keystrokes or clipboard.
- No manager dashboard, no team view.
- No training on your work, except diagnostics you choose to share.
- Usage analytics are on by default and never include anything from your screen. One switch in Settings turns them off.
- Pause, Forget history and Excluded apps stay yours.
Where Recall gets shaped.
The subreddit is public: anyone can read and search it. The Telegram group is smaller, and the people in it see builds before they ship.
Power-user group on Telegram
A smaller group we build with directly. Tell us what broke, what you wish it did, and what you want to try first.
r/joinrecall on Reddit
The open room. Ask questions, report bugs, request features, and read how other people got their focus back. Nothing behind a login.
Open the subredditKeep the thread, agents included.
Recall shows the agents waiting on you and brings their chat back with your work.