Search your agents' conversations and messages

Search finds words in what your agents said. It needs Pro. Use it to find a decision an agent explained, or a problem it described, across all your agents on this machine, without scrolling back through terminals or asking an agent to recall it.

There are three places to search in the web UI, and your agents can search too.

Search the web UI

The Search page: every agent’s conversations

Search is under Your Inbox in the sidebar, above My Inbox. It searches your agents’ conversations on this machine.

1. Open Search and type a few words in Search transcripts. Results appear as you type. Each word becomes a chip you can remove.
2. To refine the search, type in Add term and press Enter. Type -word to leave a word out, "two words" for a phrase, or OR (in capital letters) to match either word. A word also matches longer words that start with it: restart finds restarted.
3. The results show how many matches there are and how many come from each agent, with a snippet of each match and its age.
4. Choose Agents instead of All agents to search only some agents. Filter agents… narrows a long list, and the list includes agents that are no longer running.
5. Click a result to see the conversation around it. Click Open in conversation to go to the agent’s Conversation tab, scrolled to that spot.

Search this conversation: one agent’s session

Each agent’s Conversation tab has a Search this conversation box above the transcript. Type a word and press Enter. The view jumps to the first message that contains it and shows how many there are, for example “1 of 70”. Press Enter again, or use Next match and Previous match, to move between them. This searches the session you have selected in Transcript sessions. To search an agent’s older sessions, pick another session, or use the Search page.

Filter loaded messages: the Messages tab and My Inbox

Each agent’s Messages tab and My Inbox have a Filter loaded messages… box. It shows only the messages already loaded that match what you type, and says “6 of 50 loaded messages match — load more to include older ones”. Click Load More to bring in older messages. On Free, a note there says message filter is a Pro feature.

Ask an agent to search for you

Search finds words. An agent can add judgment about meaning: it runs the search, reads the hits, and tells you which ones answer your question. That is semantic search: search by meaning, built on search by words. This works because search is plain command line: any agent can run it.

Ask your coordinator, the agent you talk to, which starts the other agents and hands out work, for example: Search our conversations for the release notes format, read the hits and tell me which ones say why we chose it.

To keep the coordinator’s own context clean, ask it to use a subagent for the semantic search. A subagent is a helper that your coordinator starts for one job and that reports back when it is done: Use a subagent to search our conversations for the release notes format and bring back only the hits that say why we chose it. The subagent runs the search and reads the hits, including the messages around each one, and reports back. The pages of hits never fill the coordinator’s context.

What Search covers

Search covers agents on Claude Code, Codex, Cursor, OpenCode, GitHub Copilot and Muse, not just one runtime, on this machine only. A conversation search does not reach paired machines. When Pro is on, Thrum builds the search index in the background. Until it finishes, the Search page says “Results may be incomplete: the transcript index is still catching up.” and thrum transcript search prints (partial: index catching up).

Both searches are Pro: the search of conversations and the search of messages. Listing messages without a query is Free.

From the command line

These are the commands an agent runs, and you can run them yourself:

• thrum transcript search searches conversations. It searches your own agent by default; add --all for every agent on this machine, or --agent to pick some. The query takes "two words", -word and OR.
• thrum transcript show shows the messages around one hit. Give it the runtime:session:seq id that thrum transcript search prints. --before and --after choose how many messages to show on each side.
• thrum message search searches messages. thrum message list --query and thrum inbox --query search them too.

For example, to search every agent’s conversations, then your messages:

thrum transcript search --all "release notes"
thrum message search "release notes"

See the CLI reference.

Next steps

• Watch your agents in the web UI: the Search page sits under Your Inbox with the rest of the web UI.
• Command-line reference: every thrum transcript and thrum message command.