Files
deepseek-harness/packages/core/agent-default-model
turtle1999 caa7111f28 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
2026-10-08 15:30:35 +08:00
..

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 remains owned by the entry point.

Table of Contents


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.


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 remains the entry point's responsibility.
  • 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.