Compare/fff.nvim vs Recall

AI tool comparison

fff.nvim vs Recall

Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.

F

Developer Tools

fff.nvim

Frecency-aware file search built for both Neovim devs and AI agents

Ship

75%

Panel ship

Community

Paid

Entry

fff.nvim is a Rust-built file search toolkit with a dual identity: a Neovim plugin for human developers and an MCP server for AI coding agents. The core insight is that both humans and AI models need context-relevant file discovery, and the same algorithm serves both use cases well. The scoring system combines frecency (frequency + recency), git status (modified/staged files score higher), file size (prefers smaller files that fit in context), and definition match (files containing definitions of symbols you're searching). The result is that the most likely relevant file surfaces first, reducing the token cost of codebase exploration for AI agents by avoiding the need to open and read many irrelevant files. The MCP integration is the breakout feature — AI agents using tools like Claude Code or Cursor can invoke fff.nvim's search capabilities directly, getting curated file suggestions instead of brute-forcing directory traversal. fff.nvim trended at #5 on GitHub today with 767 new stars, suggesting strong interest from the developer community that runs both human and AI development workflows.

R

Developer Tools

Recall

Find any file on your machine with a sentence — no tags, no indexing

Ship

75%

Panel ship

Community

Free

Entry

Recall is a local-first multimodal semantic search tool that lets you find any file on your computer using natural language — images, PDFs, audio, video, and text — without any manual tagging, folder organization, or metadata. Ask "that invoice from the dentist last spring" or "photo of the whiteboard with the Q3 roadmap" and it surfaces the right file. Under the hood, Recall uses Google's Gemini Embedding 2 to generate semantic embeddings for all your files and stores them in ChromaDB, a local vector database that runs entirely on your machine. Nothing leaves your device. The Raycast extension adds a visual grid UI so you can search from anywhere on macOS without opening a terminal. First-run indexing can take 20-30 minutes for large libraries, but subsequent queries are near-instant. The project is MIT-licensed and built by a solo developer. It's a clear response to the frustration that Spotlight, Find, and Windows Search still rely heavily on filename and metadata matching even in 2026. As Gemini Embedding 2 is free within generous limits, the operating cost is essentially zero for personal use.

Decision
fff.nvim
Recall
Panel verdict
Ship · 3 ship / 1 skip
Ship · 3 ship / 1 skip
Community
No community votes yet
No community votes yet
Pricing
Open Source
Free / Open Source
Best for
Frecency-aware file search built for both Neovim devs and AI agents
Find any file on your machine with a sentence — no tags, no indexing
Category
Developer Tools
Developer Tools

Reviewer scorecard

Builder
80/100 · ship

The frecency + git status scoring is exactly the heuristic I apply manually when navigating large codebases. Giving AI agents access to that same signal via MCP is a practical efficiency gain — fewer context tokens wasted on files that aren't what the model needs.

80/100 · ship

ChromaDB + Gemini Embedding 2 on local files is a setup I'd have spent a week configuring from scratch. Recall packages this cleanly with a Raycast extension that makes it actually usable day-to-day. The MIT license and zero vendor lock-in seal the deal for me.

Skeptic
45/100 · skip

Frecency works well for personal workflows but can mislead AI agents on shared repos where your personal access patterns don't reflect what's architecturally important. The 'skip large files' heuristic is also a double-edged sword — some critical config files are large for good reason.

45/100 · skip

Re-indexing after file changes, cold-start latency on large libraries, and the dependency on Gemini Embedding 2 (which isn't truly offline) are real friction points. Apple Intelligence already does some of this natively on-device. Wait for broader platform support before switching your file workflow.

Futurist
80/100 · ship

This is an early example of tooling built simultaneously for humans and AI agents — a design pattern we'll see everywhere as coding workflows become hybrid. The shared context between how a human navigates a repo and how their AI agent does will be a meaningful collaboration advantage.

80/100 · ship

Semantic search for personal files is the foundation for personal AI agents. If your agent can find any piece of information you've ever touched, you unlock genuine memory at human-years scale. Recall is primitive but points at something important.

Creator
80/100 · ship

For creative projects with complex file structures — design systems, multi-locale content, large asset libraries — intelligent file search that understands recency and relevance is a genuine workflow improvement over fuzzy find.

80/100 · ship

I have 80,000 photos, hundreds of PDFs, and years of Figma exports I can never find. The idea of describing an image or document and having it surface immediately is worth every minute of setup time. This is the dream of local AI finally shipping.

Weekly AI Tool Verdicts

Get the next comparison in your inbox

New AI tools ship daily. We compare them before you waste an afternoon.

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later