dsh-credential-manager
DeepSeek Harness 的命名用户凭据：面向模型的凭据工具、通过 ctx.credentials 接口访问的机密信息、DSH_CM_* Shell 变量，以及“设置 → 凭据”页面
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:accpowered/dsh-credential-manager#82fe9c1f4f9d3b0600eadfb48de26da382c85d55Credential Manager 以 dsh-credential-manager 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 简体中文
Named user credentials for DeepSeek Harness: let the model use your API keys, tokens, and logins by reference — secret values never enter the conversation.
One credential is one flat record holding exactly one secret value. The model creates empty placeholder records with its credential_create tool; you enter the secret value in Settings → Credentials. Every configured secret is injected into each model shell execution as a DSH_CM_<ID> environment variable, resolved per execution, so the value reaches commands without ever being printed into the transcript.
| Piece | Kind | Purpose |
|---|---|---|
credential-manager | host service plugin | Metadata sidecar (storage domain), secret values behind the ctx.credentials seam, DSH_CM_* shell-env injection |
tool-credential-manager | host tools plugin | Model-facing tools credential_list / credential_create / credential_read / credential_update_note + a system-prompt policy section |
| Settings → Credentials | web client plugin (dsh.client) | The page where you enter/manage secret values; talks to the host over a self-mounted Typert Remote namespace |
From GitHub (builds on install via its prepare script; pnpm will ask you to allow the build once):
dsh plugin --profile web add github:accpowered/dsh-credential-manager
If pnpm prints an allowBuilds prompt, add the printed key under allowBuilds in the profile's pnpm-workspace.yaml and re-run the add — this is install-time code execution permission, so only allow sources you trust (pinning a commit, github:accpowered/dsh-credential-manager#<sha>, is recommended).
From a local checkout:
dsh plugin --profile web add ./dsh-credential-manager
Restart dsh web (or your profile) and hard-refresh the browser.
The bundle patch (cordis.patch.yml) inserts two host rows; the dsh.client declaration makes the web plane serve the settings page automatically:
- insert:
- id: credential-manager
name: dsh-credential-manager
- id: tool-credential-manager
name: dsh-credential-manager/tools
No harness source is modified:
ctx.remote.$mount seam — no api/remotes edit needed.TypertRemoteService; the gateway discovers its @Remote methods dynamically (SRC markers), so no code generation step is required to deploy.Stock-upstream note: the upstream api/remotes forwarded-event allowlist does not include credential-manager/updated, so the settings page does not receive live push invalidations from other surfaces; it still converges through authoritative mutation replies and connection-reset refetches. If you run a harness that forwards the event, the page lights up live automatically.
Both host rows work with zero configuration; every knob carries a schema default. To tune, restate the row in your profile's cordis.patch.yml (a patch replaces the row's whole config):
- id: credential-manager
name: dsh-credential-manager
config:
maxNoteBytes: 8192 # UTF-8 byte cap for one user/LLM note field
- id: tool-credential-manager
name: dsh-credential-manager/tools
config:
promptOrder: 116 # ordering weight of the system-prompt policy section
To mount only the service and the settings page (no model-facing tools), delete the tool-credential-manager row from the bundle patch.
credential_create with a name only (never a value) and asks you to fill it in.DSH_CM_<ID> variable in bash/pwsh commands: curl -H "Authorization: Bearer $DSH_CM_MYAPI" ....credential_read exists as a deliberate last-resort escape hatch for non-shell use; the harness instructs the model to prefer the variable path.Expired credentials keep working (the expiry day is informational) but are flagged in the page and in credential_list so the model can tell you to rotate them.
dsh plugin --profile web remove dsh-credential-manager
The service, tools, system-prompt section, settings page, and Remote namespace all detach with the plugin fiber. Persisted metadata rows (storages/credential_manager.json in the harness home) and stored secret values are left untouched.
pnpm install
pnpm build # tsc declarations + tsdown (node lib + browser client bundle)
pnpm test # vitest: service CRUD / seam confinement / tool mapping
Layout: src/index.ts (host service, default export), src/tools.ts (tools plugin), src/types.ts + src/spec.ts (wire types + storage domain), src/client/ (settings page; remote.ts is the hand-maintained Typert Remote contribution — keep it in sync with the service's @Remote methods).
MIT