dsh-plugin-model-config
DeepSeek Harness Web 设置 > 模型页面的完整模型配置编辑器：部署的模型配置架构声明的每个字段，而不仅仅是随附 UI 暴露的少数几个字段。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:liutian11451-png/dsh-plugin-model-config#999b378a81fcaa689f26a1ebd6f668c23da34311Plugin Model Config 以 dsh-plugin-model-config 发布，当前版本为 1.0.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →English | 中文
AI-generated code. This package was written by an AI agent (DeepSeek Harness, model
deepseek-flash) in a human-directed session, and published by the human who ran it. Review it before you install it, and especially before you allow itspreparescript to run on your machine. See AI disclosure for exactly what has and has not been verified.
A model-configuration control for the DeepSeek Harness web Settings → Models page: inside each provider's own card, one row per setting, ready to edit.
The shipped Models card already shows a provider's route, credential and model catalog. What it has no control for is the rest of the provider's configuration — for the DeepSeek adapter that is thinking mode, reasoning effort, the context-window and token defaults, the four image budgets, the four file and quota limits, and the timeouts.
This plugin adds those settings as rows inside the provider's own card: each row is the setting's name on the left and its control on the right, so the block reads like the settings form it sits in.
| Schema node | Control |
|---|---|
number | number box (carrying the schema's min, max, step), e.g. context window |
boolean | Yes/No switch |
| union of literals | select |
string | text box (a credential reference is labelled as one) |
Structural values are left to the card that already owns them: the model catalog, a nested retry policy, and anything the schema declares as a dict or an unmodelled node are document-shaped configuration, not settings rows, and the shipped card already edits the catalog.
Nothing about the setting list is hardcoded. The namespaces come from the deployment's own llm.listConfigurableProviders() and the settings come from each namespace's serialized schema, so a setting added to an adapter — or a whole adapter this plugin has never seen — appears as a row with no change here.
dsh plugin --profile web add dsh-plugin-model-config
Substitute your profile name for web if you run a different one. The package declares dsh.bundle, so dsh plugin registers its patch layer in the profile automatically. Restart dsh web and reload the page: the build payload is composed at boot, so a reload alone is not enough the first time.
dsh plugin --profile web add github:liutian11451-png/dsh-plugin-model-config
A git install fetches sources, not built artifacts, so the package ships a prepare script that builds lib/ from src/ with plain tsdown — no sibling repository, no type checking. pnpm ≥10 refuses to run a git dependency's prepare until you allow it, so the first add fails with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED and prints the exact key to add. For a git install that key names the resolved tarball, not the bare package name:
allowBuilds:
dsh-plugin-model-config@https://codeload.github.com/liutian11451-png/dsh-plugin-model-config/tar.gz/<commit-sha>: true
Copy the line pnpm prints verbatim — it carries the commit the install resolved to — then re-run the add. Treat that allowance as permission to execute this package's code on your machine at install time, and pin a commit (github:liutian11451-png/dsh-plugin-model-config#<sha>) so a later push cannot silently change what runs.
One caveat when moving an existing install: if the plugin was previously installed from a local directory, remove that first. A leftover link in the profile's node_modules collides with the incoming git install and pnpm fails with an EPERM symlink error during import.
To avoid asking users for the allowance altogether, publish to npm or ship a tarball from pnpm pack — neither needs build permission.
A settings provider must be mounted (@deepseek-ai/dsh-settings-file is part of the standard preset — it is what gives settings.describe anything to answer). A deployment whose settings provider is read-only renders the controls disabled and says so.
Each row reads the namespace's resolved value (schema defaults → composition base → user layer) for display, and writes only the user layer, one path at a time, through settings.mutate(ns, ops, expectedRevision). A row is shown as overridden exactly when the raw user section carries that path — presence, not equality, is the harness's own rule — so resetting a setting is an unset, never a write of the default back. A write that loses a revision race is reported instead of overwriting.
package.json # dsh.bundle + dsh.client manifests
cordis.patch.yml # inserts this package's loader row
src/index.ts # node half (inert)
src/client/index.ts # browser half: one keyed seat entry per namespace
src/client/fields.ts # the schema walker
src/client/ProviderRows.tsx # the setting rows and the write plumbing
src/client/locales.ts # zh/en dictionaries, including the setting names
tsdown.config.ts # consumer-side build
smoke.mjs # loader-contract smoke test
The node half is deliberately empty. The harness client module registry discovers dsh.client packages by walking the host Loader's rows, so the package needs one mounted row as its carrier; that is all the row is for.
The plugin registers into settings.models.provider-card, the seat the Models section exposes for exactly this: a card's adapter extension area, dispatched by the card that owns the namespace. That seat is keyed and matched exactly (options.key against the card's entryKey), so the plugin registers one entry per configurable namespace — a single entry would render nothing anywhere. No file of the DeepSeek Harness repository is modified.
pnpm install
pnpm build # emits lib/index.js and lib/client.js
pnpm typecheck
pnpm test # the walker contract, the rows, and dictionary coverage
node smoke.mjs # evaluates the built browser half against a stub shell
headers/queryParams maps and any unmodelled node are handled by the card that already owns them (the catalog) or not at all. A row is a scalar a person sets with one control; a document-shaped value is not.llm-pi-ai nests profiles under providers; each profile is sliced out for its own card, and the profile's own schema decides which settings appear.role('secret') value never rides the wire, so no row can show or set it; use the credential surface the adapter documents.platform: web; there is no terminal-surface equivalent.This package was written by an AI agent, not by a person typing the code. It was produced by DeepSeek Harness running the deepseek-flash model in a session directed by its human publisher (@liutian11451-png), on 2026-09-12. The human chose the feature, approved the approach, and reported the behaviour; the agent read the harness sources to establish the settings, slot, and schema contracts, then wrote the source, tests, build configuration, and documentation in this repository. The same disclosure is recorded in machine-readable form under aiDisclosure in package.json.
Treat the code accordingly: read it before you install it, and treat the allowBuilds permission a git install asks for as permission to run unreviewed generated code on your machine.
pnpm test — 34 tests: the schema walker's mapping of every node kind in both envelope shapes, the row filter, the rows themselves (control kind per schema type, resolved values, overrides, reset), the write path (op shape, revision, nested profile paths, conflict handling), and dictionary coverage against the schema fixturespnpm typecheck — cleannode smoke.mjs — loader-contract assertions against the built artifact, including that apply registers one keyed settings.models.provider-card entry per configurable namespace, which is the wiring the page silently depends onnode drive-ui.mjs <url>: Edge over the DevTools protocol, no dependencies). On a live deployment it confirmed the block renders inside the DeepSeek card — the 模型配置 heading, sixteen numbered settings showing their resolved values, and thinking/reasoningEffort as closed selects — and that editing one number persisted it to the settings document.Three faults were found this way and fixed:
remote.settings and remote.llm were read without being declared in inject, so the whole loader entry failed (cannot get property "remote.settings" without inject).{ uid, refs }) whose nested schemas are integer ids; the walker read those ids as nodes, so it found no fields and rendered nothing. Both shapes are now fixtures, and a test asserts they agree.value or in meta.default depending on how the union was written; reading only the first turned a closed set into a JSON editor.llm-pi-ai dict-typed layout was reasoned from the settings document. Its slicing path is covered at the component level, but no live card for it was inspected.MIT