[Blog](https://supermemory.ai/blog) · [Learning](https://supermemory.ai/blog/tag/learning)

# Hybrid Search: Combining Lexical and Semantic Retrieval

Combine keyword and vector results without mixing incompatible scores. Learn rank fusion, reranking, filtering, and how to evaluate the tradeoffs.

By Shardul Mane April 23, 2026 · 4 min read 

![Hybrid Search: Combining Lexical and Semantic Retrieval](https://supermemory.ai/_astro/cover.aVZlUmF3_Z24J80T.webp)

Hybrid search combines more than one retrieval signal, commonly lexical matching and vector similarity. Lexical search is useful for exact terms such as error codes and product identifiers. Semantic search helps when a question and its answer use different wording. Combining them can broaden the candidate set, but the result still needs evaluation and permission filtering.

The word “hybrid” is overloaded. Some products use it for dense plus sparse retrieval; others use it for several content types or stores. Check the API's definition before assuming two systems perform the same operation.

## Match the search method to the question

| Question                                        | Signal likely to help                       | Failure to test                                                  |
| ----------------------------------------------- | ------------------------------------------- | ---------------------------------------------------------------- |
| “What does ERR-482 mean?”                       | Exact lexical matching                      | A semantically similar but different code ranks first            |
| “How do I stop invoices renewing?”              | Semantic matching                           | The source says “cancel recurring billing”                       |
| “Does the enterprise plan support SSO?”         | Both                                        | A consumer-plan passage uses similar language                    |
| “Which service depends on the failed database?” | Explicit relationships or structured lookup | A passage mentions both entities without establishing dependency |

These are hypotheses for your corpus. A good keyword system can use synonyms, and a vector model may recognize an exact code. Measure the cases that matter instead of declaring a universal winner.

## Combine ranks when scores are incompatible

BM25 scores and cosine similarities do not share a natural scale. Adding their raw values can let one method dominate simply because its scores are numerically larger.

Reciprocal rank fusion (RRF) combines positions instead. Each result receives a contribution based on its rank in each list. This standalone Python example treats each list as unique document IDs and uses a conventional illustrative constant of 60:

```
def rrf(rankings, k=60):
    if k <= 0:
        raise ValueError("k must be positive")
    scores = {}
    for ranking in rankings:
        seen = set()
        rank = 0
        for doc_id in ranking:
            if doc_id in seen:
                continue
            seen.add(doc_id)
            rank += 1
            scores[doc_id] = scores.get(doc_id, 0.0) + 1 / (k + rank)
    return sorted(scores, key=lambda doc_id: (-scores[doc_id], doc_id))

assert rrf([["policy", "faq"], ["faq", "guide"]])[0] == "faq"
assert rrf([["a", "a", "b"]]) == rrf([["a", "b"]])
assert rrf([]) == []
```

Here, `faq` appears in both lists and wins the fused ranking. That does not establish that it answers the question. Fusion creates a candidate ordering; the evidence still needs to support the answer. Tune candidate counts and fusion settings on held-out questions rather than treating this constant as a product requirement.

## Apply permissions to every retrieval path

If the lexical path respects the tenant filter but the vector path does not, the combined result can leak data. Apply authorized scope consistently, including reranking inputs, caches, and any parent-document expansion.

An inaccessible document must not enter a downstream model prompt just because the application removes its citation afterward. For shared applications, use the [isolation checklist](https://supermemory.ai/blog/multi-tenant-memory-noisy-neighbor-isolation/) to test the full path.

Version filters matter too. A stale policy that matches exact words can outrank the current policy. Keep the old version only when the question and access rules allow historical evidence, and label it clearly.

## Add reranking for a specific reason

A reranker evaluates candidate relevance after initial retrieval. It is useful to test when supporting evidence already appears somewhere in the candidate pool but is not selected for the final prompt.

It cannot recover a passage that neither search path returned. It also adds processing work, and any external reranking service becomes another destination for the candidate text. Measure its effect on answer support, latency, and cost under the same workload.

Weaviate's [hybrid-search documentation](https://docs.weaviate.io/weaviate/search/hybrid) describes a concrete implementation and fusion options. Those details are product-specific; the Python example above is a general rank-fusion illustration rather than a reproduction of Weaviate's scoring.

## Keep graph traversal a separate choice

Graph traversal follows relationships such as account-to-contract or service-to-dependency. It can complement lexical and semantic search, but “hybrid search” does not automatically mean graph traversal is involved.

First identify whether the task needs an explicit relationship path. If it does, preserve the path and its supporting sources in the answer. The [graph-versus-vector guide](https://supermemory.ai/blog/knowledge-graph-solutions-rag-applications/) describes that decision.

## Build a comparison that can change your decision

Label a sample of exact-identifier questions, paraphrases, mixed queries, and no-answer cases. Compare lexical-only, vector-only, and fused candidates before adding a reranker. Keep filters, corpus version, and answer settings fixed.

Track evidence recall, first useful result, duplicate context, unsupported answers, and time spent in each stage. Report results by query type: an average can hide the exact-ID failures that affect your support team most.

If the combined system brings no meaningful benefit for your workload, keep the simpler path. If it helps one query class, consider routing that class deliberately rather than paying for every retrieval method on every request.

Supermemory's [search modes](https://supermemory.ai/docs/recall/search) use “hybrid” to return both extracted memories and document chunks. Distinguish that content-selection meaning from the lexical-plus-vector design discussed here when configuring an integration.

If relevant passages enter the candidate pool but rank too low, use the [contextual reranking guide](https://supermemory.ai/blog/contextual-reranking-for-rag/) to test that stage separately.

To evaluate Supermemory as a retrieval option, [test it with your own query set](https://console.supermemory.ai/) using the documented search modes above. Compare returned evidence, context size, and latency against your current path; let the workload determine whether it is a useful fit.

## Other posts.

1. [We're open sourcing the company brain. Here's how we designed the multiplayer harness Company Brain is now open source. A walkthrough of the multiplayer harness behind its Slack experience, from proactivity and memory boundaries to approvals and recovery. NewsSep 25, 2026 ](https://supermemory.ai/blog/open-sourcing-company-brain)
2. [Jev changes a lot in memory & context engineering. Here's exactly how. We tested Jev across reranking, chunking, observation, and harness decisions. Here is where fast decision models help memory systems, where they cost more, and where they still fall short. EngineeringSep 24, 2026 ](https://supermemory.ai/blog/jev-memory-context-engineering)
3. [I reverse-engineered Instinct's memory. Here's exactly how it works Instinct keeps its memory as git-tracked markdown files, found with grep rather than vectors. Here is the whole system as far as black-box probing can reconstruct it, and how to rebuild it on supermemory in about 60 lines. EngineeringSep 20, 2026 ](https://supermemory.ai/blog/reverse-engineering-instinct-memory)
4. [An update to supermemory We've discontinued the supermemory company brain and Nova. Everyone who was charged has been refunded, our MCP and plugins continue to run, and we're going all in on the memory engine. NewsSep 10, 2026 ](https://supermemory.ai/blog/an-update-to-supermemory)
5. [Scaling Conversations: How Adapta Grew Usage Without Losing Context Adapta added Supermemory as a persistent memory layer so every conversation keeps its context — letting the team scale usage without losing the thread. Case StudyJun 12, 2026 ](https://supermemory.ai/blog/adapta-scaling-conversations)
6. [How Chatarmin Ditched RAG and Went Memory-Only with Supermemory Chatarmin replaced a heavy RAG pipeline with Supermemory's memory layer — cutting average AI response time from 40s to 12s and token usage by 40–50%. Case StudyJun 10, 2026 ](https://supermemory.ai/blog/chatarmin-memory-only)
7. [SMFS: making agentic retrieval 55% cheaper AND more accurate We launched SMFS.ai (Supermemory Filesystem) a few weeks ago, with a simple bet: We can redesign the filesystem specifically for agents, with special files, structures, and commands that it can use for it's tasks. Today, SMFS is used by hundreds of companies to power their agents. EngineeringMay 28, 2026 ](https://supermemory.ai/blog/smfs-making-agentic-retrieval-55-cheaper-and-more-accurate)
8. [Introducing Dynamic Dreaming: supermemory now connects the dots, for you. Dreaming is magical. TLDR: We're launching Dynamic Dreaming in supermemory today, which automatically works if you're using supermemory in any way - API, OpenClaw, Hermes agent, etc. EngineeringMay 25, 2026 ](https://supermemory.ai/blog/introducing-dynamic-dreaming-supermemory-now-connects-the-dots-for-you)
9. [Dear reader, we just made supermemory insanely cheap... the Context Cloud When I first started building supermemory, I had one goal: To build the best memory system for AI. I would talk to customers, and find out that memory was not the only thing they needed - They were all setting up 7-8 different vendors at the same time. EngineeringMay 18, 2026 ](https://supermemory.ai/blog/dear-reader-we-just-made-supermemory-insanely-cheap-the-context-cloud)
10. [Introducing @supermemory/tools v2.0.0 Today we're releasing v2.0.0\. This release unifies the API across all agents sdk integrations from AI SDK to Mastra, makes conversation identity a first-class concept, and ships with memory saving on by default. EngineeringApr 27, 2026 ](https://supermemory.ai/blog/introducing-supermemory-tools-v2-0-0)
11. [Solving the Precision-Recall Tradeoff: Search Result Aggregation When you're building memory for AI, search is your foundational layer. The way search generally works is straightforward: the user defines a query, and then sets a limit (top-K) on how many search results they want returned. Usually, this is set to 10 or 20. EngineeringApr 5, 2026 ](https://supermemory.ai/blog/solving-the-precision-recall-tradeoff-search-result-aggregation)
12. [OpenClaw Memory Problems: Why It Forgets and How to Fix It (2026) TLDR: Today, we are releasing a new version of our openclaw plugin - https://github.com/supermemoryai/openclaw-supermemory. This post is going to be a bit technical, so bear with me (or bookmark for later!) In this post, I will talk about what we do about OpenClaw memory, and how we fix it. EngineeringFeb 19, 2026 ](https://supermemory.ai/blog/why-everyone-is-complaining-about-openclaws-memory-it-sucks-and-why-supermemory-fixes-it)
13. [Stateful Coding Agents with Memory: Build Long-Running Agents (2026) We built a plugin for Claude Code and OpenCode that gives your coding agent persistent memory. It remembers your preferences, learns your codebase, and never loses context mid-conversation. The result is an agent you can run for months without starting over. EngineeringFeb 18, 2026 ](https://supermemory.ai/blog/infinitely-running-stateful-coding-agents)
14. [Clawd / Molt bot's memory SUCKS. We gave it supermemory. I'm the founder of supermemory. Clawd/Molt bot is blowing up right now, with many, many use cases. I set it up, too, and have been using it through telegram. TLDR: just go to https://supermemory.ai/docs/integrations/clawdbot to set up supermemory for your clawd bot. EngineeringJan 28, 2026 ](https://supermemory.ai/blog/clawd-molt-bots-memory-sucks-we-gave-it-supermemory)
15. [Catch up with our UNFORGETTABLE Launch Week Over the last year, one belief has guided almost everything we’ve built at Supermemory AI becomes meaningfully useful only when it remembers. Memory shouldn’t be something developers rebuild from scratch. It shouldn’t be fragile, expensive, or trapped inside a single tool. NewsJan 4, 2026 ](https://supermemory.ai/blog/catch-up-with-our-unforgettable-launch-week)
16. [Empowering the Next Generation of Founders: Supermemory Startup Program If there’s one thing we’ve learned while building Supermemory, it’s that most startups don’t fail because they didn't build features; they fail when infrastructure slows them down, or they built too slow. NewsDec 31, 2025 ](https://supermemory.ai/blog/empowering-the-next-generation-of-founders-supermemory-startup-program)
17. [Building code-chunk: AST Aware Code Chunking At Supermemory, we're building context engineering infrastructure for AI. A huge part of that is dealing with code: ingesting repos, understanding structure, and making it searchable. The problem is that most code chunking solutions are terrible. We built code-chunk to fix this. EngineeringDec 29, 2025 ](https://supermemory.ai/blog/building-code-chunk-ast-aware-code-chunking)
18. [Supermemory raises $3 million with the best memory engine for LLMs Today, I am excited to announce our first funding round to accelerate our mission of building an interoperable, scalable and reliable memory for LLMs and agents. Memory is one of the hardest challenges in AI right now. NewsOct 6, 2025 ](https://supermemory.ai/blog/supermemory-raises-3-million-and-building-the-best-memory-engine-for-llms)
19. [Mem0 vs Supermemory: Why Scira Switched Scira AI moved its production memory layer from Mem0 to Supermemory. This is what failed, what improved, and how the team evaluated the two systems. Case StudyOct 2, 2025 ](https://supermemory.ai/blog/why-scira-ai-switched)
20. [Never Record Again: How Montra Uses Supermemory to Rethink Video Creation Campbell Baron, the founder of Montra, has been making videos since he was twelve. By thirteen, he was already doing brand work. Today, he’s betting on a very different future for creators: a world where recording is the exception, and most videos are generated from scratch. Case StudyAug 21, 2025 ](https://supermemory.ai/blog/never-record-again-how-montra-uses-supermemory-to-rethink-video-creation)
21. [Unified Memory That Works Where You Work: Your Second Brain With Supermemory Hi everyone, I’m Dhravya, the founder of Supermemory. I want to start with a little story behind why this product means so much to me. You can also skip straight to what it is and how it works below. EngineeringJul 25, 2025 ](https://supermemory.ai/blog/unified-memory-that-works-where-you-work-your-second-brain-with-supermemory)
22. [Supermemory just got faster on PlanetScale What is Supermemory? Supermemory completes the missing part of the LLM puzzle: memory. Just as memory is crucial for human intelligence, it's essential for truly intelligent AI systems. EngineeringJul 18, 2025 ](https://supermemory.ai/blog/supermemory-just-got-faster-on-planetscale)
23. [Faster, smarter, reliable infinite chat: Supermemory IS context engineering. People are obsessed with prompts and prompt engineering. Sure, what you say is important, but what the model knows when you say it is the difference between a stateless text generator and an intelligent AI system. In short, context is the most crucial component. NewsJul 9, 2025 ](https://supermemory.ai/blog/faster-smarter-reliable-infinite-chat-supermemory-is-context-engineering)
24. [We solved AI API interoperability One API to rule them all, One spec to find them, One library to bring them all and in the TypeScript, bind them. When we were building the Infinite Chat API, initially, we only supported the OpenAI format. This was fine, until a lot of our customers started asking for more. EngineeringJul 7, 2025 ](https://supermemory.ai/blog/we-solved-ai-api-interoperability)
25. [The Wow Factor of Memory - How Flow Used Supermemory To Build Smarter, Stickier Products Overview: Flow is a note-taking app built around a bold vision: to create a more personal, context-aware writing experience powered by AI. At the heart of this mission is memory. Case StudyJun 14, 2025 ](https://supermemory.ai/blog/the-wow-factor-of-memory-how-flow-used-supermemory-to-build-smarter-stickier-products)
26. [The UX and technicalities of awesome MCPs Last month, we launched the Supermemory MCP, mostly to test our own infrastructure and get some initial traction. It blew up. To my absolute surprise, the initial launch itself got half a million impressions (!!!). Then, we launched and got #2 on ProductHunt too. EngineeringJun 8, 2025 ](https://supermemory.ai/blog/the-ux-and-technicalities-of-awesome-mcps)
27. [Architecting a memory engine inspired by the human brain Language is at the heart of intelligence, but what truly powers meaningful interaction is memory — the ability to accumulate, recall, and contextualize information over time. Large Language Models (LLMs) have mastered language, but memory remains their Achilles’ heel. EngineeringJun 5, 2025 ](https://supermemory.ai/blog/memory-engine)

## Start building with supermemory.

Memory and continual learning for any model, any harness. Available through our API, plugins, and MCP.

[Build with supermemory ](https://console.supermemory.ai/)