Turtle
38c7a9fbf4
* feat(release): publish package source, declaration maps, and documentation Every release member publishes its TypeScript source and the declaration maps that resolve into it, and @deepseek-ai/dsh publishes the repository Markdown documentation staged from docs/ at prepack time. The ./src/* export most members already declared now resolves for an installed consumer, and a consumer editor follows a declaration to the implementation. Bundled JavaScript maps stay unpublished; the vendored family and the Desktop runtime file policy are unchanged. Rationale: .agents/notes/implemented/process/2026-10-08-published-source-and-docs.md * feat(release): publish JavaScript maps and compress bundles Every emitted JavaScript map ships beside the bundle it describes, and the workspace build and the client preset compress bundles without mangling identifiers. The documentation payload now mirrors the website publication manifest and is removed again by `postpack`; Desktop and the Python executable exclude the published source, documentation, and maps; `clean` removes a staged copy. Typert's publication contract gains the Remote declaration map. * fix(release): keep node bundles readable for the worker image The browser worker image lowers `yield*` only as a whole statement and rewrites `for await` loops by their source layout, so compressed node-side entries either fail that lowering or lower to unparseable code. Only the browser bundles keep compression, which removes about a third of their text. The bundle-purity assertion now matches the module-loader call regardless of the quote style compression picks, and the release-pack fixture exercises the installed package's new documentation requirement. * feat(release): publish the whole documentation tree `@deepseek-ai/dsh` copies `docs/` in full instead of the website's page set: the maintainer documents, the generated migration records, the translation guidelines, and the `*.i18n.yaml` consistency records ship with the installed package, so the documentation's own links resolve without a checkout. * feat(release): publish the upgrade guides with the documentation The staged documentation keeps the website's page set and adds every `docs/upgrade-guide/` document, which is what an installed reader consults when a released change breaks something. The rest of the maintainer tree stays out. * test(release): expect source and maps in master's new payload cases * feat(release): keep installed docs and source readable in Desktop Desktop keeps the published src/ and docs/ trees inside app.asar, and every model shell call receives DSH_INSTALL_DIR and DSH_NODE_EXECUTABLE so an agent can read them through Electron's Node mode. Staging also generates docs/upgrade-guide/README.md, an index of the upgrade guides grouped by the release they upgrade from. Minified client bundles print string literals with backticks: the worker image packer now recognizes those chunk requests, client license banners are prepended after minification so their text survives, and the affected artifact tests accept either quote. * test(desktop): read archived docs through the Windows PowerShell form Regenerate the config catalog for the shifted shell-env source line. * test(desktop): wait for the GUI-subsystem Electron process from PowerShell * build(release): publish source and maps from the message-quotes package * build(release): publish source and maps from packages new on master * build(release): publish source and maps from the tool-office package
description, kind
| description | kind |
|---|---|
| The deployment default model selection for users and maintainers choosing, configuring, or debugging which model freshly created agents start on. | package-reference |
@deepseek-ai/dsh-agent-default-model
English | 中文
Summary
Give newly created agents a shared default provider and model when their sessions do not specify one. Provider, model, and reasoning effort are live Config fields. Saved selections update the active profile patch and apply to subsequent reads; per-session selection belongs to the Agent model API.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Mount this package wherever agents are created without an explicit model route. The service answers one question — which model should a fresh agent use? — so entry points that create agents consult it instead of re-implementing a default.
Configure the default
The composition requires a provider and model. Consumers read the live references even when no configuration editor is mounted.
- name: '@deepseek-ai/dsh-agent-default-model'
config:
provider: deepseek
model: deepseek-chat
| Field | Default | Meaning |
|---|---|---|
provider |
required | Registered provider route for fresh agents |
model |
required | Provider-owned model id for fresh agents |
The generated configuration catalog lists every accepted field. reasoningEffort is optional; saving a selection without it removes that field from the profile’s complete config override.
Read and change the default
currentSelection() returns a detached { provider, model, reasoningEffort? } for a newly created agent; saveSelection() stores the complete selection for later agents.
const selection = ctx.agentDefaultModel.currentSelection()
await ctx.agentDefaultModel.saveSelection({ provider, model, reasoningEffort: 'high' })
Without a configuration editor, saveSelection() is a no-op. The service does not validate catalog membership; the consumer opening a model request owns availability diagnostics.
Understand the implementation
Implementation internals — click to expand
This section explains how the service realizes the behavior above; the observable contract is covered in Use this package.
Design concept
The service retains its validated Config references and samples them in currentSelection(). saveSelection() captures the submitted values and serializes profile writes in submission order, including overlapping callers. Each caller observes its own write failure; a rejected write does not prevent later saves. Session-specific selection takes precedence in the consumer.
Source map
| File | Role |
|---|---|
src/index.ts |
Live default selection and profile-backed writes |
Behavior notes
currentSelection() returns a detached selection. A captured selection stays stable while later operations read updated Config references.
Further Exploration
The package-level contract is enough for most consumers; read these when you need the surrounding domain.
- Core subsystem — the
Agenthandle andAgentOptionsroute selection. - agent-loop package — how agents resolve provider and model at request time.
- Generated configuration catalog — every accepted config field and its source declaration.
- Core group map — how the core packages compose.
Model Experience
Indirectly, through the ModelSelection the service supplies to an entry point; request assembly and the provider adapters own the model-visible request.
KV Cache effect
Changing the default affects only agents that subsequently resolve from it. An existing session whose request log already names a selection keeps that selection, so this service does not invalidate its established prefix.
Known Limitations and Deferred Work
These limits define the service's scope. They are current package constraints, not a task backlog.
- One process-wide default — the service owns a single default; per-session model selection belongs to the Agent model API.
- Persistence requires a profile configuration editor — without it, saving a default does not retain the selection.
Dev Note
Working context for maintainers — click to expand
None.