Source Repository URL
https://github.com/paperfoot/search-cli
Why this repo was selected
- Search CLI is already a search-native tool for AI agents, with a clear provider abstraction and explicit mode routing.
- The codebase is active, well-tested, and small enough that a new backend stays reviewable in one sitting.
- You.com fits naturally as an additional optional search provider rather than a new pattern.
Candidate evaluation summary
paperfoot/search-cli: selected. Best fit because it already fans out across multiple providers and has clear provider/config/doctor/test seams.
sydasif/web-search-mcp: strong fit for web research, but it’s a newer Python MCP server with fewer provider seams exposed.
mavam/pi-web-providers: strong abstraction surface, but the change would touch a broader configurable tool matrix instead of a single search backend.
Proposed integration type
Optional Search API provider.
Planned env vars and setup
YDC_API_KEY enables the provider.
SEARCH_KEYS_YOUCOM is also accepted through the existing SEARCH_KEYS_* config overlay.
search config set keys.youcom <key> stores the key locally.
- Default behavior stays unchanged for users who do not configure You.com.
Expected usage example
search "rust async runtimes"
search -p youcom -q "rust async runtimes"
search -m news -q "AI agents"
Validation plan
cargo fmt --all
cargo test
cargo test --test integration -- --nocapture
Fallback/error behavior
- If the key is missing, the provider stays unconfigured and the existing search fan-out is unchanged.
- You.com results are optional and participate in the same provider-failure reporting as the other backends.
- If You.com returns an API or parsing error, the CLI reports it as a normal provider failure instead of changing default search behavior.
Links
Status
Source Repository URL
https://github.com/paperfoot/search-cli
Why this repo was selected
Candidate evaluation summary
paperfoot/search-cli: selected. Best fit because it already fans out across multiple providers and has clear provider/config/doctor/test seams.sydasif/web-search-mcp: strong fit for web research, but it’s a newer Python MCP server with fewer provider seams exposed.mavam/pi-web-providers: strong abstraction surface, but the change would touch a broader configurable tool matrix instead of a single search backend.Proposed integration type
Optional Search API provider.
Planned env vars and setup
YDC_API_KEYenables the provider.SEARCH_KEYS_YOUCOMis also accepted through the existingSEARCH_KEYS_*config overlay.search config set keys.youcom <key>stores the key locally.Expected usage example
search "rust async runtimes"search -p youcom -q "rust async runtimes"search -m news -q "AI agents"Validation plan
cargo fmt --allcargo testcargo test --test integration -- --nocaptureFallback/error behavior
Links
cargo fmt --all,cargo test, andcargo test --test integration -- --nocaptureall passed after the final wiring fixStatus