History

Yichen Jiang fc8f992cde fix(web): address onboarding review feedback		2026-07-30 18:56:56 +08:00
..
src	fix(web): address onboarding review feedback	2026-07-30 18:56:56 +08:00
tests	feat(web): configure DeepSeek during onboarding	2026-07-30 12:41:09 +08:00
package.json	feat(web): configure DeepSeek during onboarding	2026-07-30 12:41:09 +08:00
README.i18n.yaml	Merge remote-tracking branch 'origin/worktree-llm-web-config' into worktree/onboarding-deepseek-config	2026-07-30 18:43:06 +08:00
README.md	docs: record DeepSeek onboarding credential flow	2026-07-30 12:41:32 +08:00
README.zh.md	Merge remote-tracking branch 'origin/worktree-llm-web-config' into worktree/onboarding-deepseek-config	2026-07-30 18:43:06 +08:00
tsconfig.json	refactor(gui): copy-free settings shell; ui-settings-general owns ownerless copy	2026-07-26 12:40:17 +08:00
tsdown.config.ts	feat(gui): settings panel with locale and theme preferences	2026-07-26 00:28:43 +08:00

README.md

@deepseek-ai/dsh-client-ui-settings

English | 中文

Settings shell plugin: a pure composition face. It occupies sidebar.settings with the trigger chrome and modal settings panel, and declares the slots registrants fill: settings.trigger / settings.header / settings.close (chrome content), settings.section (one page per feature), and settings.onboarding (feature-owned overlays on the empty Hero). The shell ships no copy and reads no locale state — all text arrives from registrants (ui-settings-general owns chrome and General; features own their sections, rows, and onboarding overlays).

The shell supplies onboarding registrants only two navigation facts: whether the session surface is the empty Hero and an openSection(id) callback that opens the panel on a registered section. Registrants own capability readiness, dismissal, copy, and mutations; the shell therefore does not become a second configuration fact source.

Model Experience

None, as the settings shell serves browser UI composition; nothing here reaches a model request.

KV Cache effect

None; this package neither assembles nor sends a provider request.

Known Limitations and Deferred Work

Panel is browser-preference scope only — host-side settings surfaces (permission mode, tool-call mode) have no RPC backing yet; their skeletons live in ui-settings-general.