Coding agents
Recall watches your Claude Code and Codex sessions the way it watches your own work. A session that is waiting on you is another loop, and a session that finished can close the loop it was working on.
- Waiting means the agent finished its turn and is waiting for your next message. It shows as an AGENT row. Waiting sessions never send a reminder.
- Blocked means the agent stopped to ask your permission. It shows first, in amber, as BLOCKED. If you leave it for five minutes, Recall sends one quiet nudge.
- Agents. Coding sessions that finished or need your approval.
- Blocked session. What it is asking for, the tool, the session, the project and how long it has been blocked.
- Finished Codex session. Its closing message and how long it has been waiting.
- Finished Claude Code session. Same layout. Hover for Go to session, Seen and Dismiss.
Go to session
Go to session brings the editor or terminal forward and selects the session's tab. A Codex conversation opens where it runs: in the Codex app, or in VS Code for the extension. If the session is gone, Recall opens Loops → Agents.
When an agent finishes
When an agent's closing message says the work a loop was about is done, Recall can close that loop on its own. When it isn't sure, the row asks you with Confirm done and Not done.
Precise tracking with hooks
Without hooks, Recall checks the sessions' own files about every 30 seconds and can tell running from waiting. Only hooks can tell Recall the moment a session stops to ask for your approval, so BLOCKED rows and the five-minute nudge need them. Turn them on in Settings → Integrations. They add a small entry to Claude Code's and Codex's own settings, and Remove hooks takes it out again.
Moving a session to a project
Move to project… on an agent row files the session's whole repository under that project, from now on. Sessions in the same repository follow.
Screenshots show a fictional demo day. All people, projects and messages are made up.