AI tool comparison
fff.nvim vs Microsoft Harrier-OSS-v1
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
fff.nvim
Freakin Fast Fuzzy Finder for Neovim — built for AI agents too
50%
Panel ship
—
Community
Free
Entry
fff.nvim (Freakin Fast Fuzzy File Finder) is a high-performance fuzzy search plugin for Neovim that takes the standard file-search experience and rebuilds it for the era of AI coding agents. Beyond fast fuzzy matching, it ships with a built-in MCP server that lets Claude Code, Codex, and other agents call it directly — reducing token waste from repeated file glob patterns and directory listings. The token-efficiency angle is the differentiator. Every time an AI agent needs to find a file, it typically burns tokens on recursive directory listings or blind glob patterns. fff.nvim's frecency scoring (blending frequency + recency) and git-status awareness mean the agent gets the most relevant files in the first response, not after three rounds of narrowing. Prebuilt binaries in Rust make cold-start negligible even on large repos. The plugin supports three grep modes — plain, regex, and fuzzy — plus multi-select, configurable thread counts, and telescope-compatible keybindings. It's currently trending on GitHub with 3,700+ stars after a weekend Show HN that focused heavily on the agent-aware angle. The MCP integration is the hook that makes this more than a Telescope/fzf replacement.
Developer Tools
Microsoft Harrier-OSS-v1
SOTA multilingual embeddings in 3 sizes — quietly MIT-licensed with zero fanfare
75%
Panel ship
—
Community
Free
Entry
Microsoft Harrier-OSS-v1 is a family of multilingual text embedding models released with almost no publicity on March 30, 2026 — no blog post, no press release, just a HuggingFace upload. Available in three sizes (270M, 0.6B, and 27B parameters), the models achieve state-of-the-art performance on Multilingual MTEB v2 across 94 languages, 32k token context windows, and use a decoder-only Transformer architecture rather than the traditional BERT-style encoder design. The 27B variant scores 74.3 on MTEB v2, outperforming all previous open-source multilingual embedding models. All three sizes are MIT-licensed — fully open, including commercial use. The decoder-only architecture mirrors modern LLMs rather than the encoder-only models (like E5, BGE, and mE5) that have dominated embedding benchmarks for years. For developers building RAG systems, semantic search, multilingual document clustering, or cross-lingual retrieval, Harrier represents a significant quality jump. The 270M and 0.6B variants are practical for production deployment; the 27B is for maximum quality where compute isn't a constraint.
Reviewer scorecard
“The MCP integration and frecency scoring for agents is genuinely useful — I've measurably reduced token burn in Claude Code sessions by pointing it at fff.nvim instead of raw glob calls. The Rust prebuilts mean zero configuration pain. Strong ship.”
“MIT license + SOTA multilingual MTEB scores + 270M/0.6B/27B size options = drop this into your RAG stack immediately. The decoder-only architecture is architecturally interesting but what matters is the benchmark numbers, and they're the best in class. Drop-in replacement for mE5-large or multilingual-e5-large.”
“Telescope and fzf-lua have years of plugin ecosystem maturity. The agent-aware MCP angle is clever marketing but how many Neovim users are also running Claude Code via MCP? The overlap feels narrow. Wait until the agent integrations mature.”
“Benchmark scores don't always translate to real-world retrieval quality — domain-specific datasets often favor fine-tuned models over general SOTA. The lack of any documentation, paper, or announcement is a yellow flag; it's unclear what training data was used, which affects reproducibility and potential data contamination concerns.”
“Agent-aware developer tools are a new category. Once your IDE and file search are MCP-native, the agent can navigate your codebase as efficiently as an experienced human dev — without wasting 40% of its context window just finding the right files.”
“The shift to decoder-only embeddings mirrors the broader architectural convergence in AI — the same foundational architecture working for both generation and retrieval. As RAG systems go multilingual and handle longer documents, models like Harrier with 32k context and 94-language coverage become load-bearing infrastructure.”
“This is deeply Neovim-specific and developer-focused. If you're not living in a terminal editor with AI agents piped into your workflow, nothing here is for you. Pass.”
“For anyone building multilingual content search or recommendation systems — this is the embedding model to use. Being able to search across 94 languages with a single model rather than language-specific pipelines dramatically simplifies cross-cultural content projects.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.