Documentation
Recall

Search your history across every machine

Every computer you connect sends its sessions to one history, searchable from the web, the Mac app and your iPhone.

4 min read

Claude Code keeps each conversation on the computer that ran it. Yesterday's session on your laptop isn't on your desktop, and a session on a cloud machine or a teammate's computer isn't on either. Codecast puts them in one place: every computer you connect sends its sessions to your account as they happen, and you search all of them from the web at codecast.sh, the Mac app or your iPhone.

The search page with the query "webhook retry", its Everyone, Any message, Any time and Recent filters, and sessions with the matching messages highlighted
One search over every machine. Each result is a session, with the messages that matched.

Set it up

Install codecast and sign in on each computer your agents run on (Getting started walks through it). There is nothing else to turn on. From then on, every session on that computer is recorded and searchable, whether it ran in Claude Code, Codex, Cursor, Gemini, pi or Grok.

Search from anywhere

Press ⌘K anywhere in the app and start typing. Sessions with matching messages appear as you type, along with tasks, plans, docs and people that match.

The command palette open over the inbox, with "webhook" typed and matching sessions and tasks listed
⌘K searches as you type. ⌘↵ opens the full search page.

Narrow it on the search page

Press ⌘↵ from the palette to open the full search page. Tabs across the top split results into All, Sessions and the other kinds that matched. Four menus on the right narrow sessions:

MenuChoices
EveryoneSessions from everyone you share with, or Only mine
Any messageEverything said in a session, or My prompts, only the lines you typed
Any timePast week, Past month or Past 3 months
RecentNewest first, or Relevant for best match first

Put a phrase in quotes to match it exactly; words without quotes match anywhere in the session. The empty search page shows a row of filters you can add to the query by clicking them:

The empty search page with a row of filter chips: file:, commit:, pr:, label:, author:, repo:, after:, before:
Click a chip to add it to the search, then type its value.
TypeTo find
file:src/webhooks.tsSessions that edited a file or folder
commit:3f2a91cThe session that made a commit
pr:482Sessions linked to a pull request
author:meSessions a particular person ran
repo:acme-apiSessions in one repository
label:apiSessions you filed under a label
after:7d, before:2026-09-01Sessions active after or before a time

Read the results

Each result is a session. Under its title you see the matching messages, who said them (you or the agent) and when. Click a message to open the conversation at that point. When a session handed work to helper sessions, the result says how many of them matched too. Right click a result to open it in a new tab or copy a link.

The page address keeps your whole query, so a narrowed search is a link you can bookmark or send to a teammate.

On your iPhone

Pull the inbox down a little, or tap the search icon, and the search box appears above your sessions. It searches the same history and takes the same filters.

The phone inbox with the search box open above the session list and "webhook" typed
The phone searches the same history. Pull the list down to reveal the box.

Let your agents search it

With Memory on, your agents search this same history themselves, from whichever computer they run on. Ask "what did we decide about the schema in yesterday's session on my laptop?" and the agent finds it and answers with a link to the session.

What it covers

  • Your sessions, and your team's shared ones. A teammate's session appears only if it is shared with the team. Which folders are shared, and which stay private to you, is set per folder; see Team sessions.
  • Every message for the last 30 days, titles and summaries before that. Older sessions match by their title and summary, and the search page says so above the results.
  • Only computers running codecast. A computer that has never had codecast installed and signed in adds nothing.

If you only use one computer

Claude Code's own claude --resume lists recent sessions for the folder you are in, on that computer. Open source tools such as search-sessions and LLMnesia search the full text of the session files on one computer and keep everything on it. If your work lives on one machine and only you need it, those are less to set up. Codecast is for history spread across several computers, agents or people.

For agents and scripts

cast search takes the same query, filters included, from a terminal. It is what agents run when Memory is on.

More guides
Agent features: what your agents know how to do
Switch features on for each computer, and every new session there learns to remember, delegate, track work, show results and use your machine.
Memory: agents that look up past work
Your agents search every session you can see, across your machines, agents and team, and answer with the session they found it in.
See which agent session wrote a line
Set Blame to Sessions on any file to see the session behind each line, and open the conversation where it was decided.
Messaging between sessions
Your sessions hand each other results and answers directly, so you stop relaying text between them.
Stable context: sessions that know what's been happening
New sessions start with a short list of what you and your team worked on recently, so they pick up threads instead of starting cold.
See your whole team's agent sessions in one place
Every session your team runs, on every machine and agent, in one live Activity page and inbox, shared per folder.
Use Codecast with T3 Code
Threads you start in T3 Code appear in Codecast with no setup, beside every session you run anywhere else, ready to search, steer and share. What you get on top, and what stays in T3 Code.
Use Codecast with OpenCode
Sessions you run in the OpenCode TUI appear in Codecast within seconds, with no plugin. Reply to them from the app, start new OpenCode sessions there, and search them beside every other agent you use.
Share a session with your team
Choose what the team sees of a session, share it by link or a few messages at a time, and how that compares to other tools.
Pinned thread state
The agent keeps one short note on each session saying where it stands, above the composer and on its inbox card.
Decisions: asking without interrupting
Agents put the calls only you can make on one Decisions page you clear when you choose to, and each answer goes back to the session that asked.
Team chat with your agents in the room
Channels, threads and DMs where you can hand a session or a role something by mentioning it, while agents stay quiet unless they're needed.
Huddles, transcripts and walkie
Every huddle is transcribed under each speaker's name and leaves a summary, so your agents can quote what was said, and a session can join the call.
Workers, forks and switching agents
Your agent can hand work to workers that report back to it, and you can fork a conversation to try two directions from the same point.
Tasks and plans
Agents file the work they take on, post progress and close it with what they verified, and you follow it on the Tasks and Plans pages.
Triggers
Agents schedule their own follow-ups, once, on a schedule or on a GitHub or Linear event, and you can set one yourself from the Triggers page.
Workflows
A fixed sequence of agent steps, checks and approval gates that runs the same way every time and waits for you where you want a say.
Orchestration
Hand an agent a whole plan and it runs a team: implementers working in parallel, a reviewer on every task and critics on the result.
Pull requests and issues
Every pull request gets a page with its checks and threads, the session that opened it fixes what reviewers and CI flag, and Linear or GitHub issues become tasks.
The org: roles that look after your work
Give lasting work to a role with an area, a charter and a standing session, and approve the changes your agents propose to the org.
Let agents use your Chrome
Agents check pages in the Chrome you already use, logins included, from their own background tabs. Screenshots and errors come back to the conversation.
Vault: keys, logins and sign-ins for your agents
Fill a credential once and every agent on every machine can use it, without the value ever entering a conversation.
Computer use: agents in your Mac apps
Agents work in Preview, Slack, System Settings or your own desktop build, in the background, with an orange pointer that shows where they act.
Typecheck: one shared check for every agent
With Typecheck on, agents on a computer share one typecheck per project, so checks answer in seconds and a busy machine stays usable.
Skills: slash commands for the jobs you repeat
Type / in a Claude Code session to pick up work, hand it over, get a second opinion or ship a pull request, the same careful way every time.
Run sessions on other machines and in the cloud
Start a session on another computer or a cloud machine in your AWS account, move it there and back, and watch it from anywhere.
Codex Cloud tasks in codecast
Bring your Codex Cloud tasks into your inbox, start new ones with several attempts, and turn the result into a pull request or local changes.
Usage limits are a pause
When a Claude plan runs out, sessions wait for the reset or continue on another account you've saved, instead of stopping for good.
The visual canvas
Agents answer with charts, comparisons and diagrams drawn right in the conversation when a picture says it better than text.
Published pages
Agents turn reports and mockups into pages with their own link that you can share, gate, and get comments on.
Why codecast feels instant, even offline
Everything you see comes from a copy on your device that the server keeps current, so screens open at once, your edits show immediately, and nothing is lost offline.
Taking longer than usualOffline · reloads when back