Unverified50% confidenceOpinionExact time
Drex 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/26/2026
First Seen
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.74% similarUnverifiedThe strategy is a research instruction rather than a mandatory whitelist; if the search scope needs to be restricted, request-level search configuration should be used; a cutoff date in the Prompt does not generate a historical snapshot of the underlying data.65% similarUnverifiedDrex for Search requires an average of only 12.6 search calls on BrowseComp-Plus.64% similarUnverifiedThe Adaptive Instructed-Retriever dynamically adjusts search depth based on actual needs, rather than executing a fixed number of retrieval steps.64% similarUnverifiedDrex 1.5 can return probabilities for all candidate options in a single forward pass59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1100039API
curl https://kongchang.com/api/v1/knowledge/claims/1100039MCP
get_claim(id=1100039)