The seam answered one question — what is behind this environment-variable name — and that shape cannot hold what an authorization grant is: a multi-field, rotating value keyed by a provider id rather than by a POSIX identifier. The Models page already works around the gap by inventing a synthetic environment name (`MINIMAX_CN_API_KEY`) for a route the user added by hand, because the store's key must look like one. `CredentialKey` is `<scope>/<id>`, where the scope is the owning plugin's registered name. The owner is in the key because a `grant` payload is written in its owner's format: two plugins serving the same provider name would otherwise read each other's payload, and a record left by an uninstalled plugin could not be told from a live one. The `/` also keeps the grammar disjoint from `CredentialRef`, so the key spaces cannot collide. `CredentialRecord` is `api-key` (key and/or provider environment values) or `grant` (an opaque, owner-owned payload). The asymmetry is deliberate: an api key is the harness's own data, a grant is a package it carries for someone else. `modifyRecord` is the only write path because a correct write depends on the current value — a token refresh is read-decide-replace under one cross-process lock, without which two processes rotating one refresh token lose whichever wrote first. `.credentials.yaml` becomes a versioned two-section document. The pre-release flat layout is refused by name, with the entry count and the one edit needed, rather than read as an empty store — which would surface as an authentication failure on the first request instead of at load. A grant payload is admitted in both directions, so a value the document could not read back exactly as written is refused rather than stored lossily.
host/ — web-GUI host half
English | 中文
The host side of the dsh web GUI: the API gateway every client shape shares, and the plain HTTP server it rides on. The browser side lives in client/; the composed application is apps/cli booting the dsh-base bundle serving apps/web. All product packages.
| Package | Role | ctx key |
|---|---|---|
apiproxy/ |
Shared host API gateway and wire contract | ctx.apiProxy |
webserver/ |
HTTP route carrier | ctx.webServer |
frontend-static/ |
SPA dist server on the webserver fallback seat | consumes ctx.webServer |
directory-picker/ |
Workspace-directory picking seam | ctx.directoryPicker |
directory-picker-native/ |
Native directory-picker backend and browser interaction | registers ctx.directoryPicker |
directory-picker-browse/ |
In-app directory-browser backend and interaction | registers ctx.directoryPicker |
directory-picker-auto/ |
Host-adaptive picker composition | mounts a backend |
plugin-inventory/ |
Read-only projection of current Loader entries | Remote pluginInventory/list |
apiproxy remains transport-independent; client/connection supplies the browser/HTTP carrier. Picker implementations replace one another behind the shared seam.
The subsystem references: web-server.md and workspace.md (the picker seam).