Repository navigation
Releases: BOWLUNA/dsh-custom-mode
Releases · BOWLUNA/dsh-custom-mode
Release list
v2.2.3
[2.2.3]
- Preserve flow-style, scalar, and alias
agent-presetssettings when choosing a default assistant. Recognize quoted section and default keys, so an existing choice is never overwritten and valid YAML is not corrupted. - Keep nested
!!jsconfiguration values in the host loader's expression format. Creator's skill directories now resolve instead of failing schema validation; disk composition text stays intact. - Use native Input and Button atoms for filtering and disclosure controls. Remove menu, selector, disabled-state, and danger-button repaints; document textareas follow the native InlineEditor surface and font while preserving manual save and ordinary newlines.
- Test the current default host
0.2.0-rc.2and the new preview0.2.1-alpha.2against their own shipped declarations. Tests no longer assume removed Codex/Claude subagent rows exist. - Add reproducible packed-install and runtime checks, covering every base mode, rendered settings, repeated operations, uninstall/reinstall, and user-data preservation. Release now waits for both compatibility and browser workflows; the browser matrix covers both channels and redacts startup tokens.
- Add read-only discovery adapters and checks for dshmarket, DSH Plugin Hub, and DSH Plugin Store. Stale, unreachable, and unverified directory entries remain explicit limitations; no external listing is submitted.
- Verify candidate installation, activation and removal through the real dshmarket and Plugin Hub UI paths. Store still hides this package under its upstream install-tested-only filter and offers no custom-source input; no Store approval is claimed.
- Make npm publish failures propagate through the release log pipeline with
pipefail; E403, OTP, successful publication and already-published conflict outcomes were verified without registry writes.
This release targets the Web profile, tested on both current channels. VMware/Electron desktop coverage remains unverified and is not claimed by this release. Store listing approval remains an external distribution limitation.
Install 2.2.3 and restart the profile's DSH process. No prompt or preset migration is required.
v2.2.2
[2.2.2]
Logic tree
- The settings page is two branches. This assistant keeps all five base modes selectable. New assistant keeps Coding, Writing, and Chat selectable, and shows the official modes with only Standard lit. The other four are dim and cannot be chosen there.
- A new assistant still starts on the official Standard mode. The dim row is the same rule, shown on the page.
What you need to do
Install 2.2.2 and restart dsh.
v2.2.1
[2.2.1]
Storefront
- README shows a centered 2×2 of four 800×400 screenshots: assistants, system prompt, base mode, plugin switches. No letterbox.
- npm keywords cover the English search terms and 自定义模式 / 系统提示词 / 提示词编辑.
- Header banner states the same sentence in English and Chinese.
What you need to do
Nothing, unless you want the pictures. Restart is not required for a README-only install, but installing 2.2.1 still needs a restart of dsh.
v2.2.0
[2.2.0]
The prompt you save is what a new session starts from
- When
settings.yamlhas noagent-presets.default, the plugin writescustom. A value you already set, includingstandard, stays. Standard, PTC, Minimal, and Creator remain in the menu. - Save sits directly under the system prompt. Plugin switches stay behind "Show plugin switches".
- Session logs named
session.v4.jsonl.zstdare read bytools/session-trace.mjs, as well assession.v3.jsonl.zstd. - The save message says the next model step rereads
prompt.md. It no longer says the current session keeps the old prompt. - Package description, keywords, and this README no longer claim a role-play preset.
What you need to do
Restart dsh after installing 2.2.0. If a new session should stay on Standard, set agent-presets.default: standard in settings.yaml before the first launch of this version, or change it back afterward.
v2.1.0
[2.1.0]
A stale settings save no longer discards a prompt written outside the page
- The page sends the newest history number as
baseN. Ifprompt.mdchanged after that revision, the save returnsconflictand does not write. The other text stays on disk and in history. Reload, then decide whether to overwrite. - A client that omits
baseNstill overwrites. The replaced text is kept in history. A numeric string is not abaseN. The prompt-only fallback uses the same rule. - Plugin rows use one height (
min-height: 74px). The browser gate reads its labels from the dictionary, and delete confirmation clicks the dialog that is outside.cpfe.
v2.0.1
[2.0.1]
The page fits one screen more closely
- Plugin rows no longer repeat On/Off next to the switch, and a row with no note does not keep an empty second line. Base-mode pills stay on one line.
- Sections are separated by the same hairline the settings pages use. New assistant sits with the assistant block, not after the switches.
- Upgrade notes: restart dsh after install. Existing assistants stay.
prompt.starter.mdis written only when you create an assistant.
v2.0.0
[2.0.0]
The settings page is the assistant, then its prompt
- Each assistant still has its own system prompt, one of the four shipped base modes, and plugin switches. Choosing nothing, or Coding, creates the same assistant as before.
- Writing and Chat are starters for a new assistant only. They do not change the assistant already on screen. Each stores the prompt it was created with, and Restore reads that file back.
- The page order is the current assistant first: prompt, name, save, base mode, plugin switches. New assistant is its own section at the end.
v1.13.0
[1.13.0]
Settings page reads as one settings page
- The tools disclosure is a single heading, Tools, with a chevron. It no longer says "Hide capabilities · Capabilities".
- Save sits in normal flow under the prompt. It no longer sticks over the editor. The filesystem path is no longer printed on the page.
- Section introductions are one line. Repeated explanations under the assistant list are gone. Fields use the same surface token as native inputs.
1.12.2
v1.12.1
[1.12.1]
Storefront and host alignment
- Colors and the code font use the host tokens (
--dsw-*,--ds-font-family-code), so dark mode, light mode and third-party themes that retint those variables apply to this page. - The page follows the shell language. The shell ships Chinese and English. A language pack that selects another language, with no dictionary here, shows English rather than the whole page in Chinese.
- The official one-click installer matches
peerDependenciesand includes prereleases. The current stable line0.2.0-rc.2and the preview line0.2.1-alpha.1are both inside the range. - The README no longer carries internal notes or token accounting.