mirror of https://bitbucket.org/siakitem/my-pi.git synced 2026-10-26 10:45:22 +00:00

Files

T

云服务部-叶林立andDevin <158243242+devin-ai-integration[bot]@users.noreply.github.com> 0c9823ef5c feat(pi-web-search): 搜索凭据迁移到 Pi auth.json

三个搜索 key 改为 auth.json 中的 tavily/exa/keenable api_key 凭据，
pi-web-search/auth.ts 复刻上游 resolve-config-value 语义（!command、
$VAR 插值、credential env 优先、$$/$! 转义）并在每次调用时读取，
进程环境变量与 search.env 不再被直接读取。search_config.sh 重写为
scripts/search-auth.mjs 的薄封装：加锁原子写、权限 600、保留其他
凭据条目，支持 --migrate 从旧 search.env 一次性导入。

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

2026-10-19 20:39:13 -07:00

clients

feat(pi-web-search): 搜索凭据迁移到 Pi auth.json

2026-10-19 20:39:13 -07:00

test

feat(pi-web-search): 搜索凭据迁移到 Pi auth.json

2026-10-19 20:39:13 -07:00

auth.ts

feat(pi-web-search): 搜索凭据迁移到 Pi auth.json

2026-10-19 20:39:13 -07:00

index.ts

feat(pi-web-search): 搜索凭据迁移到 Pi auth.json

2026-10-19 20:39:13 -07:00

LICENSE

feat(pi-web-search): 统一 web_search/web_fetch 并由主模型路由搜索厂商

2026-10-19 20:13:37 -07:00

package.json

feat(pi-web-search): 搜索凭据迁移到 Pi auth.json

2026-10-19 20:39:13 -07:00

README.md

feat(pi-web-search): 搜索凭据迁移到 Pi auth.json

2026-10-19 20:39:13 -07:00

router.ts

feat(pi-web-search): 搜索凭据迁移到 Pi auth.json

2026-10-19 20:39:13 -07:00

README.md

pi-web-search

Unified web search and fetch for Pi. The main model only ever sees two tools — web_search and web_fetch — provider selection happens inside the extension.

web_search(query, max_results?, site?, published_after?, published_before?, depth?) routes each query to Tavily, Exa, or Keenable using the session's current main model (ctx.model + ctx.modelRegistry.complete), guided by per-provider rules. Results include details.provider / details.routedBy for debugging.
web_fetch(urls, max_characters?) always reads pages via Exa (web_fetch_exa), degrading silently to Keenable then Tavily.

Providers (`clients/`)

Plain fetch calls — no MCP adapter, no upstream extension wrappers:

clients/tavily.ts — POST api.tavily.com/search|extract, Bearer key. Requires a tavily credential.
clients/keenable.ts — api.keenable.ai, keyless /public endpoints by default, a keenable credential raises rate limits. Adapted from @keenable/pi-search.
clients/exa.ts — JSON-RPC over mcp.exa.ai/mcp (Streamable HTTP): initialize once, cache mcp-session-id, tools/call per request, re-init on session expiry. An exa credential is optional (x-api-key header).

Keys live in Pi's auth.json as one api_key credential per provider (tavily, exa, keenable), read by auth.ts with upstream resolution semantics — literal values, $VAR/${VAR} interpolation, and !command indirection (e.g. "!op read op://Vault/Tavily/key"). search_config.sh writes them (atomically, mode 600, preserving all other entries); process environment variables are not read directly — use "key": "$TAVILY_API_KEY" to indirect through env. KEENABLE_API_URL stays env-only, or can be stored in the keenable credential's env map.

Routing

router.ts asks the current model to answer with exactly one provider name, given a prompt containing the per-provider strengths and the query's requested filters. Decisions are cached per session (LRU, 32 entries). Failure paths are deterministic: an unroutable answer or a dead provider falls back across the remaining available providers — never a heuristic choice over the model.

README.md

pi-web-search

Providers (clients/)

Routing

Providers (`clients/`)