Unverified50% confidenceBenchmarkExact time
Drex for Search requires an average of only 12.6 search calls on BrowseComp-Plus.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/26/2026
First Seen
Valid until: 1/24/2027
Sources
Related Entities
Related Claims
UnverifiedDrex for Search's compatibility with mainstream Agent frameworks and whether it supports custom retrieval backends were not covered in the release materials.66% similarUnverifiedDrex for Search belongs to the retrieval strategy layer rather than the retrieval engine layer; it does not promise stronger recall but addresses the issues of retrieval timing and stopping conditions.64% similarUnverifiedOut of 937 searches, the agent followed the instruction in the rules file to check the module index first only 18 times.54% similarUnverifiedKeyword search easily misses files that are semantically related but differently named, vector search has uneven embedding quality in the code domain, and LSP depends on correct project configuration to work.54% similarUnverifiedKeyword-based search algorithms perform reasonably well with small corpora but degrade as the content library crosses a critical size threshold54% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1100035API
curl https://kongchang.com/api/v1/knowledge/claims/1100035MCP
get_claim(id=1100035)