Overview
A saved search is a named MQL query you can reuse without retyping. Save any query you've written, run it again on demand, or let Trix run it for you on a schedule and notify you about the results. It's how a one-off query becomes an ongoing view of your memory.
Saving a query
Author a query on the Query page, then save it with a name. Saved searches are editable — update the query, rename it, or change its schedule at any time. Because the query is stored as MQL, it always reflects the latest matching memories when it runs, not a frozen snapshot.
Scheduling & notifications
Attach a schedule to a saved search and Trix runs it in the background on that cadence. When it runs, you get a notification — in-app and through any channels you've configured — so you can monitor your knowledge without polling it yourself.
Useful patterns:
- "Anything tagged
urgentadded since yesterday" - "New high-quality memories in a space this week"
- "Open items on the Action super-type that are overdue"
A scheduled saved search can also drive automation — its run can trigger a downstream action, turning a recurring query into a small workflow. Pair saved searches with webhooks to deliver results wherever you work.
Available everywhere
Saved searches aren't limited to the web app. They're part of the API and are exposed to agents through the MCP server, so a bot can list your saved searches and run one to pull exactly the memories it needs — the same query, whether a human or an agent runs it.