Momor Search Now Runs on Momor Workflows
The Momor Team · Nov 1, 2026 · 3 min read
For most of its life, Momor Search was its own pipeline: purpose-built code that worked out what you asked, ran the tools and wrote the answer. That code is gone. Search is now a workflow. Two, in fact, running on the same engine that runs Momor Workflows for organizations.
Highlights
- Search runs as the Answer and Intent workflows
- Every step is recorded as it happens, and an interrupted search resumes where it stopped
- Every model call goes through Momor Gateway, with failover between providers
- Your saved conversations came with it
- Fewer knobs: the Fast/Thorough toggle and the model-family picker are gone
Two workflows, one engine
Answer takes your question, calls Intent to gather sources, then writes the reply. Intent chooses the tools: the web, news, places, weather, flights, papers and the rest. How Search behaves now lives in those two definitions rather than in special-purpose code, so improving Search and improving the engine are the same work.
Recorded as it happens
Before the engine asks a model or calls a tool, it writes down that it is about to, and it writes down the answer when it arrives. If a search is interrupted, it continues from the first step that did not finish instead of starting over, and a step that already finished never runs twice. If your connection drops, reopening the conversation picks up the stream from where you left it.
What came along, and what went
Conversations you saved before the move were copied into the new engine as runs, with their turns, so your history reads as it did. The Fast/Thorough toggle and the model-family picker have been retired. Search picks the model itself through Momor Gateway, trying the cheapest suitable one first and moving to the next if it is busy or fails. Your answer voice stays as a saved setting.
Why This Matters
Search has always been the proof of Momor's engine. Now it is literally running on it, with the same record, the same recovery and the same model routing an organization's workflows get. Anything that makes one more dependable makes the other more dependable too.
What this means for you: the same search box, answers that survive hiccups instead of restarting, and your history right where you left it.