LEANN Roadmap - 2026 Q1

[yichuan-w]

LEANN aims to be a personal knowledge layer - not just a storage-efficient vector database, but a unified, always-up-to-date knowledge base that runs entirely on your own machine. It connects your code, images, and your personal data (documents, emails, browser history, chats) into a single multimodal search interface.

Contributions and feedback are welcome. Join Slack at https://join.slack.com/t/leann-e2u9779/shared_invite/zt-3ol2ww9ic-Eg_kB8omwe6xmYVd0epr4Q.

P0 — Core

LEANN MCP

• IVF backend (IVF support #231, [Feature Request]: Incremental Build #89, [FEAT] Frequent update recommend no-recompute and impl leann --reindex #141) @ASuresh0524
• Merkle tree (leann watch) ([Feature]Code retrieval enhancements #41) @yichuan-w
• Cold start optimization ([Feature] Better warmup strategy #166, Search with recompute second level latency for code RAG #177) @andylizf

Search Quality

• Hybrid search (Hybrid search support[important!] #233, [Feature] Hybrid search #90)

Documentation

• ReadTheDocs (Some improvement of the contributing guide #234) @ASuresh0524
• Benchmarks @jane-jhu

---

P1

Multimodal

• Video retrieval ([Question & Feat] Will LEANN support video rag? #160) @yichuan-w
• CLIP support ([Feature]CLIP support #94)
• OCR ([feat] OCR based application #158)

Platform & Distribution

• Windows support ([TODO] Add support for Windows [Many requests] #14) @andylizf
• UI (appimage #229) @ASuresh0524

Applications & Integrations

• Agent + Deep research ([Feature] Co-search with Deep-research #104) @ASuresh0524
• Local Cursor — local model + local retrieval ([Feature] Fully local cursor reproduce 1/N using your own ollama #47)
• LlamaIndex integration (Support LEANN in llamaindex #217)
• Obsidian support (Obsidian MD support with backlins/wikilinks #96)

---

Timeline

	Target
P0 — Core	Q1 2026 (Jan–Mar)
P1	Q2 2026 (Apr–Jun)

Contributing

Contributions are welcome! If you're interested in working on any of the items above, please reach out to @yichuan-w or @andylizf. Join our Slack to discuss.

[Rob12312368]

Just click the link of Slack and got the following error doesn’t have an account on this workspace.
Tried to logged in with existing account but failed. Is the channel public?

[yichuan-w]

https://join.slack.com/t/leann-e2u9779/shared_invite/zt-3ol2ww9ic-Eg_kB8omwe6xmYVd0epr4Q
@Rob12312368 can you try this one?

[Rob12312368]

That worked for me. Thanks

[tevfik]

Hello! I've been following LEANN and its impressive storage efficiency. To support the 2026 Q1 roadmap (specifically around UI and tracking/syncing goals), I've developed LeannVault: a standalone application that adds hash-based file tracking (using SQLite) and a Web UI (FastAPI + Gradio) on top of LEANN. It also integrates Microsoft's markitdown for universal text extraction. Feel free to check it out or use it as a reference for the roadmap: https://github.com/tevfik/LeannVault

[yichuan-w]

@tevfik, wow, that is huge!! It would be nice if you could contribute some Web UI to the repo. But, again, congrats and amazing repo!

[andylizf]

Hello! I've been following LEANN and its impressive storage efficiency. To support the 2026 Q1 roadmap (specifically around UI and tracking/syncing goals), I've developed LeannVault: a standalone application that adds hash-based file tracking (using SQLite) and a Web UI (FastAPI + Gradio) on top of LEANN. It also integrates Microsoft's markitdown for universal text extraction. Feel free to check it out or use it as a reference for the roadmap: https://github.com/tevfik/LeannVault

Wow that's awesome. Thanks for your contribution!

[tevfik]

Hey @yichuan-w and @andylizf, thanks for the encouragement!

I just released LeannVault v0.3.3. I took your advice and updated the Web UI (added tabs and better cards), which definitely improved the UX.

I also wanted to share why I built the tracking layer: since LEANN is so lean it doesn't store embeddings, I was having issues with the index breaking when local folders were reorganized. The tracker now maps content hashes to paths, so results don't break when files are moved. This keeps the search results valid even after files are moved or renamed.

You can check out the new UI and the latest release here: https://github.com/tevfik/LeannVault

Let me know if any part of this logic or UI would be useful as a reference for the core roadmap