AI agents

Know the moment your agent needs you.

Recall shows which Claude Code or Codex session has finished its turn and, with the optional hooks on, which Claude Code session needs your approval. Go to session takes you straight to the tab, or to the window for the Codex CLI.

Illustration of the app, with a made-up example. Blocked shows with the optional Claude Code hooks on.

Blocked, waiting, done

Blocked goes first, wherever you look.

The tray's Waiting on you line, Smart Return and Loops all lead with a Claude Code session that needs your approval, with the optional hooks on.
Blocked
A Claude Code session stopped to ask your permission, with the optional hooks on. 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. A Codex session shows up this way, when its turn ends.
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 Claude Code session stops for approval, turn on the optional hooks in Settings → Integrations, and remove them any time. Without them, Recall checks about every 30 seconds and still shows the sessions waiting on you. A Codex session can't show as blocked today.

A developer's day with four agent sessions
The menu bar tray: today's active time by project, then a Claude Code session blocked on your approval, then what you worked on
The tray leads with the blocked session.
Going back

One click to the session. The chat comes back too.

Go to session brings the editor or terminal forward with the session's tab selected.
How every way back works
The restore checklist for a thread: Terminal, Slack and Code, each ticked with what it reopens, Code marked left off here, with Cancel and Restore
The restore checklist. Cancel opens nothing and changes nothing.

Go to session

A Codex conversation
Opens where it runs: the Codex app, or VS Code for the extension
A Codex CLI session
Raises the terminal window whose title has the session title or project folder name, not the tab. Otherwise opens the folder in iTerm2, then Terminal, then VS Code or Cursor, or else brings the terminal app forward
A session that has closed
Recall opens Loops → Agents instead

The chat comes back

Listed before it opens
Going back to a thread lists what it will reopen, all ticked. The chat and its editor are one row: untick it and neither opens
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
Takes over the terminal row with the matching folder. Recall tries Go to session first, and reopens that terminal only if that neither raised its window nor opened its folder
Exploring, not shipped

Recall MCP, for the AI tools you approve.

We are exploring a local, read-only MCP server, so an AI tool you approve could draw on your work context, starting from the thread you are in.

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.

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.

Private by design. Agent sessions stay on your Mac with the rest of your history. What is on your screen stays on your Mac.

Questions about Recall and coding agents

Does Recall work with Claude Code?

Yes. Recall lists Claude Code sessions that finished their turn and wait for your next message, in the menu bar tray, Loops and Smart Return, without the hooks. With the optional hooks on, it also shows a session that stopped for your approval, first and marked BLOCKED, with one nudge after five minutes. Go to session brings its editor or terminal forward with the session's tab selected.

Does Recall work with Codex?

Yes, when a turn ends. A finished Codex session shows as waiting on you, and Go to session opens it where it runs: the Codex app, or VS Code for the extension. For the Codex CLI, Recall raises its terminal window, not the tab. A Codex session can't show as blocked today.

Do I have to install the hooks?

No. Without them, Recall checks the sessions' own files about every 30 seconds and still shows the ones waiting on you. Install hooks, in Settings → Integrations, adds a small entry to Claude Code's and Codex's own settings. Claude Code's hooks add the blocked state and its five-minute nudge, and the Codex hook tells Recall when a turn ends. Remove hooks takes them out again.

What about other coding agents?

Only Claude Code and Codex show up as sessions, with a chat that comes back. With any other agent, Recall still follows the work on your screen, and VS Code, Cursor and Windsurf return as the workspace folder you were in.

Does Recall have an MCP server my agents can use?

Not today. A local, read-only Recall MCP is under Exploring on the roadmap: a direction, with no date. Today your agents can't read Recall.