For developers

Stop grepping. Ask questions of your codebase.

Point StrataFS at ~/work, leave it running, and search your codebase the way you'd search Slack — except the results are ranked, the latency is in milliseconds, and the index updates in real time.

Why grep falls short

grep and ripgrep are fast at what they do, but what they do is exact substring matching. Useful when you know the identifier. Useless when you remember the concept but not the name — "where do we handle the retry-after header on rate-limit errors", or "what file owns OAuth refresh".

StrataFS ranks results across both signals: BM25 for the exact tokens you typed, vector similarity for the intent. If both align, you get the right file in position one. If only one aligns, you still get a useful answer.

What works out of the box

Install and search in 60 seconds

npm install -g stratafs
stratafs config init
stratafs serve
macOS · Linux · Windows

Then in another terminal:

stratafs config init
stratafs sources add code --type local --path "$HOME/work"
stratafs serve &

# Ask a question
stratafs search "where do we handle JWT refresh" --mode hybrid --limit 5

# Filter to Go files only
stratafs search "rate limit configuration" --path "**/*.go"

# Restrict to recent changes
stratafs search "circuit breaker" --since 7d

Editor integration

StrataFS exposes a REST API on port 8080 — your editor's search panel can call it directly. Wrappers shipped:

Hand it to your AI assistant

If you use Claude Desktop or any MCP-aware client, the same engine becomes a tool your assistant can call. No more pasting code into chat — the agent runs stratafs.search and reads the answer from your actual repository. See the Claude Desktop setup walkthrough.

What this is not

Index your repos. Ask your editor questions.

MIT licensed. Multi-language. Real-time updates. Native MCP server for Claude and friends.