Home / Blog / Release notes

Release notes

Finder 0.0.11: sharper file-finder, auto-start, lighter disk

Finder 0.0.11 returns the right function instead of a 120-line slab: on 45 never-seen questions, file-finder's top-1 hit rose from 0.84 to 0.93 and overlap with the true range from 0.24 to 0.74. Harnesses now start Finder themselves, and stale caches no longer eat a gigabyte. The cost: never-seen file-finder queries are ~70 ms slower.

Published October 4, 2026 · 5 min read

The numbers: 0.0.10 vs 0.0.11

Same machine, same index, 45 file-finder questions and 8 finder questions with hand-checked answers. Every question got a random suffix so no cache could help — this is the cold path an agent hits on a new question.

Repeated questions are much faster now (rerank results are cached for 10 minutes): file-finder ~15–30 ms, finder ~50–370 ms.

Why file-finder got sharper

• Symbol-unit rerank. Candidates are still found by chunk, but the reranker now scores whole functions and types (with their doc comments) instead of arbitrary chunks. In our lab this alone moved top-1 from 0.70 to 0.97 (exact McNemar p = 0.0078).
• No more slab merging. Adjacent chunks are no longer glued into one block, which used to return near-whole files.
• Tests stop outranking code. Test functions are demoted unless your question mentions tests; on 15 test-heavy questions overlap reached 0.83.

Zero-friction start

• finder mcp is a stdio shim: your harness launches it, it starts the shared daemon if needed (one daemon, even with many sessions) and proxies MCP. Live: initialize in 80 ms against a running daemon.
• Setup now writes stdio entries for all 15 harnesses (HTTP still available via mcp_transport).
• Unindexed project? The tool result tells your agent to ask you, call approve-indexing, then retry with wait_index_secs (0–300 s) to wait for the index.

Lighter

Embedding caches for models you no longer use are removed in the background after start-up: on our machine ~/.finder/embeddings went from 1.1 GB to 202 MB.

What did not improve

Never-seen questions still take about a second: every query makes two remote calls (embed + rerank). file-finder's cold path is ~70 ms slower than 0.0.10 because it reranks more, finer candidates. A one-remote-call design is the next latency track.

Full method and per-tool comparison: No MCP vs Finder vs GitNexus vs CodeGraph.

Upgrade

curl -fsSL https://downloads.skillissuelab.com/install.sh | sh

Frequently asked questions