@auggieteo/dsh-synthetic-web-search
基于 Synthetic 的 DeepSeek Harness Web 能力接口（ctx.web）搜索提供程序和配置卡
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @auggieteo/dsh-synthetic-web-search@0.5.0Synthetic Web Search 以 @auggieteo/dsh-synthetic-web-search 发布，当前版本为 0.5.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A Synthetic Search-backed WebSearchProvider and configuration card for the DeepSeek Harness ctx.web capability seam.
This is a host-plane plugin: it registers the synthetic provider into the Harness-owned web service. It does not provide ctx.web or a model-facing tool. Use it with the existing @deepseek-ai/dsh-tool-web row.
The Harness web seam keeps a registry of search providers and selects one at execution time. Deployments that point web.config.searchProvider at synthetic need a provider that talks to Synthetic's documented search API and maps its responses into the Harness source vocabulary. This package is that provider, plus the configuration card that stores its API key in the DSH credentials domain.
It works with the shipped @deepseek-ai/dsh-tool-web agent-preset row, which exposes web_search to the model through the same seam.
Requirements:
web profile.Install the package as a profile layer in the profile that hosts web (normally web). The layer activates the provider row automatically. Choose one route.
dsh plugin --profile web add @auggieteo/dsh-synthetic-web-search
Install directly from the public Git repository:
dsh plugin --profile web add git+https://github.com/auggie246/dsh-synthetic-web-search.git
prepare allowlist for Git installsA Git install builds this package from source with its prepare script. DSH forwards the install to pnpm, and pnpm may block that script. If it does, the command prints the package/build key that pnpm requires. Copy that exact printed key into $DSH_HOME/profiles/web/pnpm-workspace.yaml, for example:
allowBuilds:
# Replace this with the exact key pnpm printed for this install.
<exact-key-printed-by-pnpm>: true
Then rerun the same dsh plugin --profile web add git+https://… command. Do not guess or substitute a package name: pnpm requires the exact key it printed.
The install command adds this package to dsh.profile.bundles. Its bundled cordis.patch.yml inserts the synthetic-web-search row and selects synthetic as the web search provider, replacing DSH's shipped deepseek-official selection. No DSH_WEB_SEARCH_PROVIDER environment variable is needed.
The row belongs in the web host profile, not an agent preset: ctx.web is process-wide and each provider must register once. examples/synthetic.cordis.yml shows the provider row; add the following selection override when mounting it manually:
- id: web
config:
searchProvider: synthetic
Restart the DSH web profile after installation. Do not start a separate Vite server; it does not update an existing DSH GUI.
Open Settings → Plugins → Plugin configuration → Synthetic web search, enter the API key, and select Save. DSH stores it in its credentials domain and does not return it to the browser after saving.
For headless use, the plugin also reads the launch environment reference (by default SYNTHETIC_API_KEY):
export SYNTHETIC_API_KEY='…'
Provider selection is intentionally unambiguous: installation pins web.config.searchProvider to synthetic. To use another provider later, apply a higher-precedence profile or --patch override with that provider's id. The existing @deepseek-ai/dsh-tool-web agent-preset row exposes web_search to the model.
| Key | Default | Meaning |
|---|---|---|
apiKey | (unset) | Literal API key for non-interactive composition. Prefer the card or environment reference; this secret is redacted from Settings responses. |
apiKeyEnv | SYNTHETIC_API_KEY | Credential reference used by the Settings card and launch environment. |
baseURL | https://api.synthetic.new | Synthetic API origin; the provider appends /v2/search. |
Remove the profile layer:
dsh plugin --profile web remove @auggieteo/dsh-synthetic-web-search
Restart the DSH web profile.
If no other configuration uses it, remove SYNTHETIC_API_KEY from the process environment and remove the stored credential through your normal DSH credentials management.
The provider sends the documented request:
POST https://api.synthetic.new/v2/search
Authorization: Bearer $SYNTHETIC_API_KEY
Accept: application/json
Content-Type: application/json
User-Agent: deepseek-harness-synthetic/0.1.0
{ "query": "…" }
It maps valid results into the Harness source vocabulary:
| Synthetic field | Harness field |
|---|---|
url | url |
title | title |
text | snippet |
published | publishedAt |
Malformed or non-URL entries are ignored. The provider does not create a generated answer (content) and returns truncated: false; the ctx.web seam applies the caller's maxResults cap. Network, redirect, HTTP, and response-shape failures surface as WEB_PROVIDER_ERROR; a missing API key surfaces as WEB_PROVIDER_CREDENTIAL_MISSING; aborted requests surface as WEB_ABORTED.
Synthetic's documented API currently exposes only query, so maxResults is intentionally not sent upstream.
0.5.0 supports DeepSeek Harness 0.1.1-rc.2, 0.1.2-rc.1, 0.1.5-rc.2, and 0.1.7-rc.2 with runtime detection — one build, no per-version install. The plugin reads the settings and card seams at load time, so the same lib/ activates on every supported version:
installSettingsSection/settingsNamespace pair; 0.1.2-rc.1 through 0.1.5-rc.2 move that wiring to the SettingsProvider.installSection method and validate the namespace as a plain string. The plugin imports the module by namespace and calls whichever shape it finds; both paths share identical semantics (composition entry as base layer and fallback).SettingsForms: a plugin's editable configuration is derived from the Config fields it marks .volatile(), addressed by profile entry id, and a plugin that ships its own page declines the derived one. The plugin marks its three Config fields volatile through a version-guarded call (a no-op on the schemastery shipped before 0.1.7), reads the live field references the Loader delivers from that release on, and calls ctx.settings.configure({ auto: false }, ctx.fiber) instead of registering a section. The harness imports a legacy settings.yaml section into the entry of the same id, so the old namespace name (web-search-synthetic) does not match this plugin's row id (synthetic-web-search): a pre-0.1.7 profile that had overridden the endpoint re-enters it once on the Plugins page. The API key lives in the credentials domain and is unaffected.ctx.settingsScope and the settings.plugin.item slot are gone. The card registers into the sidebar Plugins page's plugins.bundle.config slot, keyed by package name, and reads and writes through ctx.configForms. Both card paths are shipped: the plugin detects ctx.configForms at apply time and falls back to the pre-0.1.7 scope card when it is absent.ctx.connection.api to the ctx.remote service (positional arguments, { ok, value } envelope). The card resolves the credentials face per call: ctx.remote.credentials first, then the legacy ctx.connection.api face with its { refs } payloads and { result } envelope. This face is unchanged through 0.1.7-rc.2.synws-* classes) instead of mirroring upstream hashed names, so it stays styled on every version and follows its own release cadence.Everything else the plugin touches — the ctx.web seam and registerSearchProvider, WebError codes, credentialRef/credential resolution, the launch environment reference, invariants, schemastery role()s, the dsh.bundle.patch profile-layer mechanism with its - insert: op, the dsh.client manifest block, window.__ModuleLoader__, and the dsh.client.inject list (an id absent from a build's module graph is skipped, so the 0.1.7-only package is inert on older harnesses) — is unchanged through 0.1.7-rc.2 and needs no adaptation.
The public package name is @auggieteo/dsh-synthetic-web-search, replacing the former local @deepseek-ai/dsh-web-search-synthetic reference. The browser client registers both package ids, so legacy profile rows continue to load during migration. The bundle row id (synthetic-web-search) matches the id existing manual profile rows already use, so the plugin mounts once. The credential domain reference (SYNTHETIC_API_KEY) and the pre-0.1.7 Settings namespace (web-search-synthetic) remain unchanged, so existing credentials and persisted settings continue to apply on the harness versions that read them.
0.2.1 shipped a bundle row with id web-search-synthetic. If you installed 0.2.1 as a bundle and kept a manual - insert: block, the plugin mounted twice. Upgrade to 0.2.2 or newer, which aligns the bundle row id with the manual row id, then keep only one mount.
npm ci
npm run verify
npm run verify cleans generated output, type-checks, runs mocked provider tests, builds lib/ from source (including the browser client bundle), and checks the npm package contents with npm pack --dry-run.
To test a local checkout without touching another profile, point a throwaway profile at its absolute path:
dsh plugin --profile synthetic-smoke add /absolute/path/to/dsh-synthetic-web-search
Releases are automated. Publish a GitHub release tagged v<version>, where <version> matches package.json. The publish workflow installs with npm ci, checks the tag, tests, builds, and publishes to npm. A prerelease publishes under the npm dist-tag next. A stable release publishes under latest.
Thank you to the DeepSeek Harness team for the ctx.web capability seam and the Settings Plugins surfaces, and to Synthetic for the search API this provider adapts.
PRs accepted.
Small note: If editing the README, please conform to the standard-readme specification.