Yichen Jiang
93e67201dd
Each official settings page now lives in a client package of its own: `ui-settings-shell`, `ui-settings-agent-loop`, `ui-settings-subagent` and `ui-settings-web-search` register into `plugins.item` while the Host serves their namespaces, through the new `settingsScope.whileServed` watch, each with its own dictionary and styles. The form model, the fields and the form move to `ui-primitives` as the shared settings kit, so a community package's browser half builds a page the same way. `ui-settings-plugins` keeps only the Built-in plugins section shell around the inventory tab. The companions hold Loader rows in `web-app` behind the section; the client catalog, config catalog and module graph regenerate; the settings-card cookbook walks through a companion package.
3.7 KiB
description, kind
| description | kind |
|---|---|
| Built-in plugins settings section for the dsh web client: the Settings navigation entry and the tab chrome that feature-owned tabs register into. | package-reference |
@deepseek-ai/dsh-client-ui-settings-plugins
English | 中文
Summary
Use the Built-in plugins settings section to inspect the plugins this deployment ships. The section is a shell: it owns the navigation entry and the tab row, and every tab in it is registered by another plugin — the read-only inventory ships one. Configuring a built-in plugin happens on the sidebar's Plugins page, where each official plugin's own companion package registers its page.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Open Built-in plugins in Settings. ui-settings-plugin-inventory contributes the inventory as the section's one tab, shown as the page itself; a second registered tab turns the row into tabs. A deployment whose composition contributes no tab shows the section's empty line.
To contribute a tab, register into settings.plugins.tab with an id, an order, and a localized label; the section renders the entries in order and mounts a tab on its first selection. Feature copy stays in the registering plugin's dictionary.
Understand the implementation
Implementation internals — click to expand
The section declares settings.plugins.tab, a root list slot whose labels become ordered tabs; a lone contribution renders as the page itself, and a tab stays mounted after its first selection so search and the inventory snapshot survive switching. The section's inject projects the slot's ledger into ordered rows whose labels follow the active locale, cached until the ledger version or the locale revision moves. The Host half is an empty apply, present only so the package holds a Loader row the client module system serves the browser half for.
Further Exploration
- ui-settings-plugin-inventory — the read-only inventory tab.
- ui-settings — the domain base declaring
settings.section. - ui-plugin-manager — the Plugins page where official plugins are configured.
- ui-settings-shell, ui-settings-agent-loop, ui-settings-subagent, ui-settings-web-search — the official configuration pages, one companion package each.
Model Experience
None, as the package is a browser-side settings surface that registers no model surface.
KV Cache effect
None; this package neither assembles nor sends a provider request.
Known Limitations and Deferred Work
- The section has no tab of its own — it renders its empty line until a feature plugin registers one; the shell cannot fill the section alone.
- Runtime invariant: No companion is published. The section owns no relationship beyond the slot ledger it projects.
Dev Note
Working context for maintainers — click to expand
None.