- Who it helps
- Developers comparing the cost and accuracy of repository search.
- Availability
- Public Apache-2.0 project; documented setup requires Node.js 22+ and local model downloads. Native Windows uses WSL2.
Account for the whole intervention
Setup changes agent instructions as well as search tools. The published task benchmark uses version 2.9.0 on 200 tasks across five model-and-harness configurations. Its cost figures are token-based list-price equivalents from subscription runs, rather than invoices.
Sweet-search combines local retrieval with agent instructions ↗
Keep accuracy beside cost
The author reports the same pooled solve count across the two arms, with differences by configuration. A separate retrieval evaluation reports a model-specific accuracy regression linked to following the search rules too literally. These findings do not establish equivalent behavior on every repository.
Sweet-search combines local retrieval with agent instructions ↗
What you can do
- Inspect the per-configuration results and setup changes before a controlled trial. Open reference ↗
Where the evidence stops
Repository documentation read November 1; no code or benchmark executed. Independent replication and an original video demonstration were not found.
Sources read. Primary sources read November 1, 2026 UTC. No third-party installation, inference or complete workflow executed.
Sources & further reading
GitHub · official
Sweet-search combines local retrieval with agent instructions ↗
Identifies the subject, documented capability or specific verification limit.
mrsladoje / GitHub · page checked 2026-11-01
Coverage note: Independent attention and end-to-end execution remain unverified.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
- · Added to Current
Sweet-search indexes a repository locally and gives coding agents ranked code search and navigation tools.