8c2970e70e
Review found five real defects in the configuration-source work, all confirmed against the code rather than argued: 1. The note claimed --config outranks settings.yaml. It does not: the settings seam registers a plugin's cordis entry config as the `base` layer and the user section layers over it, and the seam cannot tell a shipped value from a --config one. The note now states shipped reality and names --config-replace as the lever for a deployment that must win. Separately, a literal `apiKey` in settings outranked both the environment and .credentials.yaml — the field is removed, so configuration carries a reference and nothing else. 2. DEEPSEEK_SEARCH_BASE_URL was functionally deleted: the shipped inline went away without the provider learning to read it. It now resolves from the environment snapshot, as the README always claimed. 3. The bootstrap deny list missed the interpreter start-up hooks. BASH_ENV is the sharpest: `bash -c` sources it on every bash tool call, so a project .env could run a file of its choosing before every command. The list now covers BASH_ENV and its per-language siblings, the Git hook commands, and the remaining preload and CA variables, organised by what a variable does rather than which runtime owns it. 4. YAML parse errors quoted the offending source line — which in a credentials document is the secret — into boot stderr and the watcher's logger. Only the error code and position are reported now, in credentials-local and settings-local alike, pinned by a test that asserts the secret is absent. 5. 0600 governed only files the harness wrote. A hand-created 0644 document was read normally. POSIX now checks the mode before reading contents, at boot and on every reload; Windows has no mode to inspect and is skipped rather than faked. The project a session is launched in is trusted by default, with no prompt and no stored trust record: it may supply its own endpoint, ordinary variables, and a key ranked below the managed store. Trust stops at the harness itself — a discovered file still cannot set DSH_PERMISSION_MODE, PATH, BASH_ENV, or the rest, because those take effect with no user action, before any turn, outside the permission policy and the sandbox.
7.5 KiB
@deepseek-ai/dsh-web-search-deepseek
English | 中文
A DeepSeek-backed WebSearchProvider for the harness web capability seam (ctx.web). It calls DeepSeek's Anthropic-compatible Messages API (POST {baseURL}/messages) with the native web_search_20250305 server tool enabled, and maps the structured web_search_tool_result blocks DeepSeek returns into the seam's normalized WebSearchResult.
This is an implementation package: it registers a provider into ctx.web, resolves its credential for each search through the optional ctx.credentials seam, records the auxiliary request in the initiating Agent session when one exists, and does not register a model-facing tool. Like @deepseek-ai/dsh-llm-deepseek, it is a function/namespace plugin (inject: ['web']). The Anthropic wire shape is a provider-private detail — it does not make this provider depend on ctx.llm.
How it differs from a dedicated search endpoint
Exa and Perplexity expose dedicated search endpoints; DeepSeek does not. Instead this provider issues a full Messages model call carrying the web_search server tool, so one search costs a complete model turn in latency and tokens — heavier than a pure retrieval endpoint. DeepSeek runs the search server-side and returns structured web_search_tool_result blocks; the provider parses those blocks and never scrapes URLs out of model prose.
Strict mode: if the response carries no web_search_tool_result block (native search did not trigger), the provider throws WebError WEB_PROVIDER_ERROR rather than degrading to prose-scraping — honest and debuggable.
It reuses the DEEPSEEK_API_KEY credential reference (no new secret) but not $DEEPSEEK_BASE_URL: the search endpoint is the Anthropic-compatible base (https://api.deepseek.com/anthropic/v1), distinct from the chat-completions base (https://api.deepseek.com) the LLM adapter uses. A mounted credentials service is authoritative; without one, the provider falls back to the launching process environment. The reference is resolved for each search, so a key stored or rotated by the Web Models page reaches the next call without a restart.
Config
| Key | Default | Meaning |
|---|---|---|
apiKey |
omitted | Literal DeepSeek API key. Prefer apiKeyEnv so no secret enters configuration; a non-empty literal wins. |
apiKeyEnv |
DEEPSEEK_API_KEY |
Credential reference resolved for each search through ctx.credentials, or from the process environment when that seam is absent. A missing value fails the call as WEB_PROVIDER_CREDENTIAL_MISSING. |
baseURL |
https://api.deepseek.com/anthropic/v1 |
Anthropic-compatible endpoint base; /messages is appended. Falls back to $DEEPSEEK_SEARCH_BASE_URL from any environment layer; do not reuse $DEEPSEEK_BASE_URL, which belongs to the chat-completions LLM adapter. An unparseable value makes the provider unavailable. |
model |
deepseek-v4-flash |
Anthropic-format model name. |
apiVersion |
2023-06-01 |
anthropic-version header value. |
maxTokens |
4096 |
Positive-integer upper bound on generated tokens for the Messages request. |
maxUses |
5 |
Positive-integer maximum web_search server-tool uses per request. |
- id: web-search-deepseek
name: '@deepseek-ai/dsh-web-search-deepseek'
config:
apiKeyEnv: DEEPSEEK_API_KEY
baseURL: https://gateway.internal/anthropic/v1
Mapping
DeepSeek returns no provider-generated answer surface this provider trusts as content, so content is omitted. sources[] comes from web_search_result items inside web_search_tool_result blocks: url ← url, title ← title, and publishedAt ← page_age. Snippets live separately as URL-keyed cited_text entries in a text block's citations[]; the provider joins them, leaving snippet absent when no excerpt exists.
Results are deduplicated by URL because one request may surface the same page across searches. DeepSeek exposes maxUses, not a result-count knob, so the seam enforces maxResults by truncating sources[] and setting truncated.
Provider failures become WEB_PROVIDER_ERROR; caller cancellation becomes WEB_ABORTED. HTTP redirects are rejected before the Location target is contacted and surface as WEB_PROVIDER_ERROR.
Request logging
Immediately before dispatch, a search running under an initiating Agent appends the log-only web/deepseek-search-llm-request session event. It contains the resolved endpoint, API version, and exact secret-free JSON body sent to DeepSeek; headers and credentials are excluded. Credential failures and cancellations before dispatch create no event, while later HTTP or response failures leave the attempted request durable. Direct programmatic provider calls outside an Agent have no initiating session to log.
Model Experience
Auxiliary DeepSeek search request
What the model sees
A separate DeepSeek model receives exactly Perform a web search for the query: <query> as its user text and one native web_search server-tool definition. This request is not part of the conversation model's context.
Token effect
Separate provider input and output tokens are incurred for each search; maxTokens caps generated output and maxUses caps native search uses.
KV Cache effect
Independent of the conversation request cache. The auxiliary instruction and native tool definition can form a stable prefix, but each changed query or model route prevents reuse from its first difference.
Conversation tool result, indirectly
What the model sees
Through dsh-tool-web, the conversation model sees deduplicated URLs, titles, dates, and citation snippets from structured search blocks; provider prose is not trusted as an answer. This provider's exact failures include the actionable missing-credential message, DeepSeek search credential resolution failed: <error>, DeepSeek search aborted, DeepSeek search request failed: <error>, DeepSeek returned no web_search_tool_result blocks; the request may not have triggered native web search, and DeepSeek returned an unprocessable response body: <error>; HTTP failures preserve the provider message. The consumer owns the error wrapper.
Token effect
Zero direct conversation tokens from registration. Result tokens scale with returned sources and snippets, then the seam enforces the requested source bound.
KV Cache effect
Append-only; newly visible content follows the reusable request prefix and does not invalidate existing KV-cache entries.
Known Limitations and Deferred Work
- One search costs a full Messages model turn — latency plus generated tokens, with up to
maxUsesserver-side searches; DeepSeek exposes no dedicated retrieval endpoint. - Dynamic credential availability resolves inside the operation — the synchronous
available()contract can establish that a resolver exists but cannot query an asynchronous credential store. A selected keyless provider therefore fails the search withWEB_PROVIDER_CREDENTIAL_MISSING; the stableweb_searchschema remains registered. Caller cancellation races this preflight locally, but cannot force an arbitrary credential backend itself to stop work. - Over-returned sources still cost tokens — with no result-count knob on the wire,
maxResultsis enforced only post-hoc by seam truncation. - Uncited results carry no
snippet— a source gains one only when atextblock citation (cited_text) matches its URL.