dsh-status-rotator

Give DSH's running status your own voice: custom phrases, typewriter output, day/night gradients, danmaku and an optional animated whale tail. Includes 1221 phrases across 14 theme packs.

English | 中文 · Quick start · Features · Whale-tail animations · Configuration · Changelog

!Custom phrases type out and rotate beside an animated whale tail, with different gradient palettes in light and dark themes.

The actual plugin running in a minimal DSH host, with sample phrases and an enlarged status row. Phrase rotation · Typewriter · Day/night gradients · Optional whale tail. Static preview.

Quick start

dsh plugin --profile web add dsh-status-rotator   # 1. install (the package ships its own bundle manifest)
dsh plugin --profile desktop add dsh-status-rotator   # for desktop: same, just use the desktop profile
dsh web                                            # 2. restart once, first install only

1. Open Settings → Status Texts (bottom left): toggle theme packs, edit phrases, tune the gradient and danmaku — every change saves and applies live, no refresh.

Never a blank line: config.labelSource (default "phrases") decides the text; with an empty bank the plugin's line falls back to the host text instead of rendering an empty row. Set it to "host" to drop rotation and get the verbatim 0.1.6 .turnStatus look (weight 500, inline-flex, 26px, shimmer, clock after 15s).

Feature Overview

Core

• Status text replacement — swaps the host line (Deep diving... / Deep diving for 12s on 0.1.7) for your phrases, rotating every intervalMs and typed out (typeSpeedMs, 0 disables);
• Phase awareness — thinking / running / long groups switch on turn duration, no need to wait for a rotation;
• Weighted random — phrase entries may carry a weight (weightedRandom: false = fully uniform);
• Anti-repeat shuffle bag — a phrase never comes back until the bag is empty, remembered per language + phase and optionally across page reloads;
• Optional whale tail — whaleTail (off by default) keeps the DeepSeek whale-tail icon of the 0.2.0 running row and animates it with the rainbow gradient; a separate switch can wag it in step with tok/s or at a fixed speed;
• Non-invasive targeting — located by role="status" + aria-live="polite" (old hosts), button[data-turn-process] (0.1.7+) or div[data-chat-running] (0.2.0+); never touches chat code blocks, other aria-live regions or the host clock.

• Phrases separate from code, modular packs — everything lives in JSON, grouped into named packs (packs[] / enabledPacks[]) that the settings page toggles and edits;
• Conditional phrases & easter eggs — a when rule (tool / retry / pending / phase / hour / firstTurn) shows a phrase only in the state it describes, and rarity lets one in on a fraction of draws;
• Template placeholders — {elapsed} {phase} {phaseLabel} {locale} {date} {time} plus live fields {model} {provider} {tps} {pending} {tools} {running} — see Template Placeholders;
• Observation channel — shows the structured llm/retry signals of the host as a small badge (⟳ 3/5 by default) with {retry} {retryMax} {retryProvider} {retryCode} {detail}; nothing is shown on hosts without an event window;
• Multilingual — follows Settings → Language live, unknown languages fall back to Chinese;
• Community phrase bot — issue form + validation + auto-PR, with branches rebuilt on main automatically (see Contributing Phrases).

• Rainbow gradient — day / night palettes follow the interface theme (or force one with mode); colors and speed configurable, one switch off;
• Danmaku — phrases fly across the page (including bilibili-style top/bottom), with size, color, opacity and z-index options; optional hover-pause, click-to-copy, per-phase colours, adaptive density and pointer avoidance;
• Appearance themes — font, size, glow, text animation (breathe / glitch) and a status-line activity indicator, bundled into one-click theme packs;
• Tab title — rotates document.title through your templates (off by default; only writes back a title it took over);
• Presets & schedule — multiple named banks, switched by hand or by weekday/time window.

• Auto-loading + push — the node half serves the config over HTTP and pushes a change notification over SSE the moment anything changes, so open pages apply edits without a refresh or restart (hosts without SSE keep the polling fallback);
• Conflict-safe writes — the config route hands out an ETag and requires If-Match on writes, so two tabs cannot silently overwrite each other;
• Persistence — saved settings go to $DSH_HOME/status-rotator/config.json, which belongs to no package and survives upgrades;
• Settings page — edit everything from Settings → Status Texts, applied on save;
• Extendable from other plugins — ctx.statusRotator lets another plugin register packs, placeholders and dynamic phrase sources without touching this plugin's source (see Extending it from another plugin).

Installation

Two ways to install: the recommended dsh plugin add command, or the manual copy. Either way, restart dsh web once after the first install.

Option A: dsh plugin add (recommended)

The plugin's package.json declares a dsh.bundle.patch manifest, so it is recognized automatically after install — no extra flags needed. The command syntax is dsh plugin --profile add (e.g. --profile web):

• From npm (easiest): dsh plugin --profile web add dsh-status-rotator ← always installs the latest release
• For DSH Desktop: dsh plugin --profile desktop add dsh-status-rotator (the desktop build's profile is desktop)
• From a clone: dsh plugin --profile web add ./dsh-status-rotator
• From a release package: download dsh-status-rotator-.zip from the Release page (it contains a ready-to-use plugin directory with config.json — not an npm tarball), unzip it, then dsh plugin --profile web add /path/to/dsh-status-rotator.

Option B: manual install

1. Put this project directory under your profile's node_modules (default C:\Users\\.dsh\profiles\node_modules\dsh-status-rotator\);
2. Insert the following into the profile's cordis.patch.yml:

- insert:
       - id: status-rotator
         name: dsh-status-rotator

1. Run node gen-config.cjs to initialize the local config.json (copied from config.example.json);
2. Restart dsh web and hard-refresh the browser with Ctrl+F5.

First run

On first start the plugin serves, in order: your saved settings ($DSH_HOME/status-rotator/config.json) → the package config.json → config.example.json (what an npm install has: all 1221 default phrases live inside it, see Phrase Bank). Two more layers join in: the auto-updated bank (every 6 hours, see Auto-updating the bank) and the optional external bank ($DSH_HOME/status-rotator/phrases.json, highest priority, see Hot-reloadable external bank). Edit files directly (hot-reloaded while a page is open) or use the Settings → Status Texts page of DSH.

How It Works

Phase Awareness

Phrases are split into three groups based on turn progress (determined by whether a clock has appeared in the status element and its reading):

| Phase | Trigger | Default duration | |---|---|---| | thinking | Turn just started, no clock | 0 ~ 15s | | running | Clock visible, under the limit | 15s ~ longAfterMs | | long | Clock past longAfterMs | ≥ 60s |

Phase changes swap the phrase immediately without waiting for the rotation interval. If a phase has no phrase group, it falls back automatically (running → thinking → any non-empty group).

Zero-Intrusion Targeting

The status label is located by role="status" + aria-live="polite" (dsh ≤0.1.6) or button[data-turn-process] (0.1.7+), so code snippets in the chat history and other aria-live regions are never touched. On 0.1.7+ the plugin does exactly three things: insert its own line in the composer seat, hide the header copy, and read the header label for the duration — the host clock is only read, while phase and elapsed come from the session snapshot.

Status line text source (label source)

config.labelSource decides what the status line says; both host generations honour it:

| Value | Status line text | When to use it | | --- | --- | --- | | "phrases" (default) | one phrase from the bank, rotating per phase | the plugin's normal behaviour | | "host" | the host text only: Deep diving... / 深度求索中 | when you want the pure 0.1.6 look with no meme phrases |

• Never a blank line: when the bank is empty (no config.json, or a preset cleared the texts), "phrases" mode falls back to the host text instead of leaving an empty row with only the clock;
• "host" copies the 0.1.6 look as well: the plugin line matches .turnStatus property for property (weight 500, height: calc(26px + …), inline-flex, same shimmer and prefers-reduced-motion fallback) and .turnStatusClock (13px, tabular-nums, 8px gap, weight 400), with the clock on the old schedule (elapsedMs >= 15s) and the text written in one go rather than typed; old hosts (≤0.1.6) are not touched at all in "host" mode;
• A matching dropdown lives on the settings page (Status line text source), and {"labelSource": "host"} can be written into config.json or a preset.

Phrase Bank

The default bank ships 1221 phrases, split into 14 theme packs (the core phrases table is empty — everything lives in packs). Ten packs are enabled by default; the two star packs are shipped but off by default — turn them on from Settings → Status Texts → Phrase packs:

| Pack | zh | en | Total | Default | | --- | --- | --- | --- | --- | | deepseek DeepSeek 专场 | 107 | 111 | 218 | on | | coding 写代码日常 | 87 | 81 | 168 | on | | daily 日常 | 77 | 64 | 141 | on | | internet-memes 网络梗 | 57 | 34 | 91 | on | | sysadmin 系统管理 | 41 | 38 | 79 | on | | slacking 摸鱼 | 40 | 33 | 73 | on | | math-physics 数学与物理 | 35 | 22 | 57 | on | | western-ai 西方 AI 圈 | 20 | 22 | 42 | on | | reverse-proxy 反代 | 19 | 21 | 40 | on | | china-ai 中国 AI 圈 | 22 | 14 | 36 | on | | star-ask 求 star | 11 | 12 | 23 | off | | star-route 星标者路由 | 92 | 92 | 184 | off | | total | 674 | 547 | 1221 | 945 on / 276 off |

• Most entries are zh/en mirrored pairs; recent community submissions are often zh-only — choose zh + en (both) in the submission form to get each phrase in both languages;
• 5 weighted showcase entries (see Weighted Random) — most phrases are plain weight-1 strings;
• The bank grows through the community phrase-submission form: validated and merged submissions are credited in CONTRIBUTORS.md;
• The numbers are computed from config.example.json by node scripts/sync-bank-counts.cjs (the submission bot and the star-pack refresh call it automatically; run it once after editing the bank by hand); run node scripts/check-bank-memes.mjs locally to audit the current bank (duplicates, lengths, ellipsis, series share).

| Pack | What it is | | --- | --- | | star-ask 求 star | pure star-ask phrases, e.g. 正在向你讨一个 star… / Begging for a star… | | star-route 星标者路由 | one phrase per current stargazer — 正在路由 写代码… / Routing to write code…, so the rotation literally routes every star-giver to work |

They ship disabled because begging is a matter of taste, not because they are broken: flip them on in Settings → Status Texts → Phrase packs. The Star packs workflow refreshes the stargazer list (weekly, when its own files change, or on demand) with the repo GITHUB_TOKEN, landing through a bot PR that is merged automatically once Test is green; the job is skipped in forks (their token cannot read stargazers of this repository) and STAR_TOKEN overrides it. Locally: node scripts/update-star-pack.cjs --token .

Phrase Packs

The bank is composable from named packs layered on top of the core phrases table:

{
    "packs": [
        { "id": "community",
          "label": { "zh": "社区投稿", "en": "Community" },
          "phrases": { "zh": { "running": ["正在试用词库包…"] } } }
    ],
    "enabledPacks": ["community"]   // absent = all packs enabled; [] = core bank only
}

• Enabled packs merge into the effective bank in order, deduped by text — an entry already present in the core bank (or an earlier pack) is skipped, keeping its weight;
• enabledPacks absent/null = all packs on; [] = core bank only. Unknown ids in the list are ignored;
• Packs support the exact same entries as the core bank (strings or {text, weight}, per-phase groups, placeholders);
• The settings page shows every pack with a per-pack enable toggle and a pack editor target: pick a pack and the phrase library editor reads/writes that pack's phrases;
• The default config ships 12 packs (deepseek / western-ai / china-ai / coding / reverse-proxy / sysadmin / math-physics / slacking / internet-memes / daily / star-ask / star-route); community is created with the first submission, and enabledPacks pins which packs start enabled.
• The phrase-submission form has a 目标词库包 picker (same pack ids plus community as the default landing spot): submissions land in the chosen pack, and a community pack is created on first use — the core bank stays untouched, so you can disable or prune community content in one place;
• Old configs without packs keep working untouched.

Weighted Random

Entries are picked by weight. Write a phrase as "text | 3" (or { "text": "text", "weight": 3 }) for weight 3; no weight = 1, capped at 1000, invalid values count as 1. weightedRandom: false goes back to fully uniform. Five showcase entries in the bank use weights.

Anti-repeat (shuffle bag)

Since v0.31.0 the status line remembers what it just said per language + phase, with a shuffle bag instead of the old "avoid the previous phrase" rule:

• A phrase is never repeated until the bag is empty — with 40 phrases in a phase you get 40 different lines in a row, not a lottery that can hand you the same one twice;
• When the bag is refilled, the last recentLimit phrases are held back, so a cycle boundary cannot repeat either;
• Weights still apply inside the bag (a weight-9 phrase tends to come up early in each cycle);
• persist: true keeps the memory in browser storage, so a page reload does not immediately show the same line again.

"antiRepeat": { "recentLimit": 3, "persist": false }

recentLimit is 0–50 (0 = bag only, no cross-cycle memory). Everything is editable from Settings → Status Texts → Behavior → Anti-repeat.

Conditional phrases (when) and rarity

A phrase can be restricted to the state it actually describes, so it appears exactly when it is true instead of competing with the other 1200 lines. Add a when object (or the | when:… suffix in the settings editor):

"phrases": { "zh": { "running": [
    "正在写代码…",
    { "text": "正在敲命令…", "weight": 2, "when": { "tool": "bash" } },
    { "text": "正在满世界翻…",     "when": { "tool": "web_search" } },
    { "text": "又失败了,再试一次…", "when": { "retry": true } },
    { "text": "等你点头…",         "when": { "pending": true } },
    { "text": "夜深了…",           "when": { "hour": [22, 6] } },
    { "text": "初次见面…",         "when": { "firstTurn": true } },
    { "text": "传说级的一句…",      "rarity": 0.01 }
] } }

| Condition | Type | Meaning | |---|---|---| | tool | string / string[] / "" | a tool with that name is running ("" = any tool) | | retry | boolean | a retry is in flight | | pending | boolean / number | dsh is waiting for your answer (number = at least that many) | | phase | string / string[] | thinking / running / long / idle | | hour | [from, to] | local hour window, may cross midnight ([22, 6]) | | firstTurn | boolean | the first turn of this session |

• All listed conditions must hold (AND). { "tool": "bash", "phase": "long" } needs both;
• A matching conditional phrase wins the draw: if any phrase's conditions hold, the pick is made from those — otherwise a bash phrase would be buried under a thousand unconditional ones. When nothing matches, the unconditional phrases are used as usual, so the line is never empty;
• rarity (0, 1] is an easter egg: the phrase only takes part in that fraction of draws. 0.01 = 1%;
• Conditions are judged from the live engine ({tools} / retry / {pending} / phase); on a host without those APIs the conditional phrases simply never appear and the unconditional ones carry on.

正在写代码…
正在敲命令… | 2 | when:tool=bash
正在满世界翻… | when:tool=web_search
又失败了,再试一次… | when:retry
夜深了… | when:hour=22-6
传说级的一句… | rarity:0.01

when: takes tool=bash (join several with +, * = any tool), retry, pending, phase=long, hour=22-6, firstTurn; separate several conditions with , to require all of them. A | inside the phrase itself is left alone, and the round trip is exact — opening and saving the settings page never drops a condition.

Template Placeholders

Any phrase (and any title template) may contain placeholders, replaced at render time:

| Placeholder | Meaning | Example | |---|---|---| | {elapsed} | elapsed time of the current turn, localized like the clock | 正在写代码 1分02秒… | | {phase} | phase id: thinking / running / long / idle | running | | {phaseLabel} | localized short label of the phase | 运行中 | | {model} | model of the current session (live engine, — when unknown) | deepseek-chat | | {provider} | provider route of the current session (live engine) | deepseek | | {tps} | streaming tokens/s estimate (live engine) | 12 | | {pending} | interactions waiting for an answer — approvals and questions share this one counter (live engine) | 1 | | {tools} | running tool names joined with + (live engine) | bash+web_search | | {running} | run / idle (live engine) | run | | {retry} | retry attempt in the current step (live engine; empty when none) | 3 | | {retryMax} | the retry policy's cap (may be empty on older hosts / always mode) | 5 | | {retryProvider} | provider that triggered the retry (provider-neutral, passed through verbatim) | deepseek-official | | {retryCode} | short failure code (safe token ≤32 chars; URLs, paths and raw messages are never rendered) | sampling_error | | {retryStarted} | 1 once the retried attempt is actually running (after llm/retry-started), else empty | 1 | | {detail} | the whole observation badge, rendered from config.details.badge | ⟳ 3/5 | | {locale} | current UI language (zh / en) | zh | | {date} | local date YYYY-MM-DD | 2026-08-07 | | {time} | local time HH:MM:SS | 12:34:56 |

Placeholders that change over time ({elapsed} {date} {time} {tps} {pending} {tools} {model} {provider} {retry} {detail}) refresh live every liveTickMs (default 1000 ms; 0 = once per rotation). Unknown placeholders are left as-is, so {...} is safe in a phrase. Values come from a real-time status engine subscribing to the session snapshot, the pending list, model RPC and the session event window, with a DOM clock fallback — without the session API, {model} / {provider} / {tps} / {tools} stay — and {pending} stays 0. The current session id is resolved as sessions.list.current (≤0.1.6) → localStorage['dsh.sessions.current'] (0.1.7+) → the DOM's [data-sidebar-right-session].

Observation channel (see deepseek-harness discussion #3669): that thread points out that subagent retries and transport fallback hide behind Deep diving…, and that the missing half is a structured data channel. The plugin consumes protocol events only (llm/retry / llm/retry-started from binding.eventSource) — no log scraping, no wording inference; the vocabulary stays provider-neutral (provider / code passed through, never enumerating product-specific codes); with no event window it simply shows nothing. The badge template lives in config.details.badge (empty string = placeholders only, no badge):

"details": { "enabled": true, "badge": "⟳ {retry}/{max}" }

"phrases": { "zh": { "thinking": ["正在写代码 {elapsed}…", "正在{phaseLabel}中 ({elapsed})…"] } }

{pending} and the session's approval policy

{pending} counts the session's pending interactions — the same list the UI renders as composer takeovers — with approvals and questions sharing one counter, so either one makes it 1 while it waits. dsh publishes at most one interaction per session, so in practice this is a 0 / 1 flag, not a queue length; it is event-driven, re-rendering the label the moment an interaction appears or disappears.

What approvals contribute depends entirely on the session's own permission preset (sandbox mode + approval policy, switched with /permission) — the plugin neither reads nor changes that setting:

• ask — a sensitive action asks first, and its approval request counts while it waits: {pending} turns 1 as the approval panel appears and back to 0 once you click;
• never — approval prompts are disabled: dsh rejects such an action up front, the client never builds a panel, and approvals contribute nothing. Note what the counter does not say: a rejection is not a pending interaction, so {pending} can never report "an action was rejected";
• questions are a different domain and stay pending regardless of the policy, so {pending} can still show 1 under never while dsh waits for an answer (a plan review, for instance).

Rainbow Gradient

Status text is drawn with an animated rainbow gradient by default (text only, not the clock). Since v0.22.0 there are two palettes — night (dark) and day (light) — following the interface theme (mode: "auto"; "day" / "night" forces one) and re-coloring live; direction is "rtl" (default) or "ltr" to match the typewriter (issue #41). Disable or recolor it in the config:

"gradient": {
    "enabled": false,                          // false to disable; true for default colors
    "mode": "auto",                            // auto follows the interface light/dark theme; day / night forces one
    "direction": "rtl",                        // rtl right-to-left (default); ltr left-to-right (matches the typewriter)
    "colors": ["#ff5f6d", "#00ff88", "#4da6ff"], // night (dark theme) color sequence (at least 2, first/last cycle)
    "dayColors": ["#d92b4b", "#0e7490", "#6d28d9"], // day (light theme) color sequence (at least 2, first/last cycle)
    "speed": 4                                 // animation speed (seconds per cycle)
}

Existing configs that only set colors keep using it in both themes (nothing changes on upgrade); add dayColors to get a separate light-theme palette.

Appearance themes

Everything that used to be limited to the gradient and the font weight now has a full set of ingredients, plus a theme gallery that sets them all in one click (Settings → Status Texts → Appearance → Appearance theme).

"appearance": {
    "fontFamily": "",        // empty = follow the interface; letters/digits/spaces/commas/quotes/hyphens only
    "fontSize": 0,           // px; 0 = follow the host, clamped to 8-96
    "glow": false,           // soft halo around the text
    "glowColor": "",         // empty = first colour of the gradient palette
    "animation": "none",     // none | breathe | glitch
    "spinner": "none"        // none | ring | bar
}

• Every default means "change nothing" — a config without this block renders exactly as before;
• The theme gallery ships five packs (classic / neon / terminal / candy / glitch); picking one writes both the appearance and the gradient palette, and every field stays editable afterwards;
• animation and spinner are attached to the plugin's own text span as CSS classes, so the host's own text and clock are never touched; breathe and glitch are dropped under prefers-reduced-motion;
• The activity indicator shows "work is happening", not a percentage - the host exposes no turn progress;
• fontFamily is written into CSS, so it is validated against a strict whitelist (letters, digits, spaces, commas, quotes, hyphens) and anything else is rejected rather than escaped.

Danmaku

Optional: every phrase can also spawn as video-site-style bullet-screen comments flying from right to left across the page (by default behind the UI — the layer is squeezed between the app background and the chat content, visible in the gaps):

"danmaku": {
    "enabled": true,
    "intervalMs": 2500,        // spawn interval (ms); smaller = more of a flood
    "speedMs": 18000,          // time to cross the screen, right → left (ms); larger = slower
    "fontSizeMin": 14,         // min random font size (px)
    "fontSizeMax": 30,         // max random font size (px)
    "rainbow": true,           // rainbow mode: each bullet picks a random color from colors
    "colors": ["#ff5f6d", "#00ff88", "#4da6ff"], // palette (at least 1)
    "color": "#ffffff",        // solid color used when rainbow = false
    "opacity": 0.3,            // global opacity (0.05 ~ 1); each bullet jitters between 75% and 100% of it
    "maxCount": 12,            // max concurrent bullets on screen
    "zIndex": -1,              // negative = behind the UI (default), non-negative = above the UI
    "scope": "all",            // "all" = every phrase of the current language; "phase" = current phase only (with fallback)
    "marginTop": 16,           // top padding of the bullet band (px)
    "marginBottom": 160,       // bottom padding (px), keeps the input area clear
    // ── new in v0.19: top / bottom (bilibili-style) danmaku ──
    "types": {                  // per-type switch + relative weight; scroll = the original type
        "scroll": { "enabled": true, "weight": 2 },
        "top":    { "enabled": true, "weight": 1 },
        "bottom": { "enabled": true, "weight": 1 }
    },
    "mode": "scroll",           // optional: force ONE type for every bullet (scroll/top/bottom, or 1/4/5); omit = weighted
    "fixed": {                  // top/bottom style — the single place to change them all
        "fontSize": 25,          // px
        "color": "#ffffff",      // solid colour used when rainbow = false
        "shadow": "1px 0 1px rgba(0,0,0,.85),-1px 0 1px rgba(0,0,0,.85),0 1px 1px rgba(0,0,0,.85),0 -1px 1px rgba(0,0,0,.85)",
        "marginTop": 16,         // distance from the top edge of the play area (px)
        "marginBottom": 160,     // distance from the bottom edge (px)
        "gap": 4,                // stacking gap between bullets (px)
        "durationMs": 4500,      // how long one bullet stays on screen (ms)
        "maxCount": 3,           // max bullets of the SAME type at once
        "zIndex": 10,            // front layer: 10 sits above the chat, below the shell overlay (20)
        "reserveBands": true,     // scrolling bullets keep out of the top/bottom lanes (no overlapping text)
        "anchorBottomToHost": true, // bottom bullets sit above the input area (its status line), not merely marginBottom away
        "overflow": "drop"       // full → drop this spawn (same strategy as scrolling danmaku)
    }
}

• With zIndex < 0 (default) the layer is mounted inside the element painting the app background (normally the conversation surface), so bullets sit between that background and the chat content — visible in the gaps and behind the conversation, never covering bubbles or the sidebar. Hidden by an opaque theme background? Set a non-negative zIndex to float above the UI; the layer never intercepts pointers.
• Mount point is re-resolved on every spawn (the fix behind v0.15.2 / v0.16.1): the app frame is found through the shell marker data-shell-overlay, and the innermost element inside it that paints an opaque background and covers most of the conversation column becomes the host (it gets isolation: isolate). Before the shell renders, the layer briefly falls back to document.body at a visible z-index and moves into place as soon as the target appears. Still invisible? Turn on debug and look for danmaku layer mounted inside the background panel.
• Bullets support the same placeholders as phrases ({elapsed} {model} {phase}…), rendered with live values at spawn time; danmaku: false disables the feature, and fontSizeMin / fontSizeMax set the random size range (auto-corrected, clamped to 8–96 px).
• danmaku: false disables it entirely. fontSizeMin / fontSizeMax set the random size range (auto-corrected if reversed, clamped to 8–96 px).

Danmaku extras

Five optional behaviours, all off by default (Settings → Status Texts → Appearance → Danmaku):

| Option | What it does | |---|---| | hoverPause | Hovering a scrolling bullet freezes it; moving away resumes it from where it stopped (the remaining flight time is recomputed) | | clickCopy | Clicking a bullet copies its text; with no clipboard API nothing happens rather than pretending it worked | | phaseColors | { "thinking": "#5fd4ff", "running": "#7dff7d", "long": "#ffc371" } - colour each bullet by the current phase | | adaptDensity | Spawns get sparser as the on-screen count approaches maxCount, and almost stop while the page is hidden | | avoidPointer | Bullets land away from the pointer's height band |

:warning: hoverPause and clickCopy turn the danmaku layer into a pointer target, which is the opposite of the "the layer never intercepts pointers" guarantee. They are therefore opt-in, and only the bullets themselves take pointer events - the layer keeps pointer-events: none.

Sending your own line - ctx.statusRotator.sendDanmaku(text) (the registration API) flies a line across immediately, and the settings page has an input for it. While the settings dialog mask is up the danmaku layer is paused, so the line is queued and sent once the mask goes away instead of being silently lost.

Coexisting with host dialogs: pause behind the mask (since v0.25)

The dsh settings dialog mask is a full-viewport backdrop-filter: blur(2px) layer: with the danmaku layer still translating behind it, the browser recomputes a full-screen blur every frame and the dialog flickers (issue #60). With pauseBehindMask (default true) a hit stops the danmaku outright — layer and in-flight bullets torn down, spawn timer cleared, host isolation restored — rebuilding everything the moment the mask goes away. Detection hit-tests the four corners plus the centre (one probe per 250 ms, rescanAll every 2 s as a safety net); small backdrop-filter surfaces (menus, cards, tooltips) never match.

Top / bottom danmaku (bilibili-style, since v0.19)

danmaku.types gives the three types (scrolling / top / bottom) an enabled flag and a relative weight, and danmaku.fixed collects their styling (font size, single color, stroke, gap, hold time, same-type cap, z-index, reserveBands to keep scrolling bullets out of the top/bottom lanes, anchorBottomToHost to pin bottom bullets above the input area).

• mode forces every bullet to one type (scroll / top / bottom, or bilibili 1 / 4 / 5); leave it out to distribute by weight;
• Top/bottom bullets default to white text with a stroke and their own size and hold time — all of it lives in danmaku.fixed;
• ⚠️ The default distribution changed: with no types in your config all three are on (scroll 2 : top 1 : bottom 1); for the pre-v0.19 look set "top": { "enabled": false } and "bottom": { "enabled": false } (or flip them off on the settings page).

Browser Tab Title

Optional and off by default. When on, the browser tab title rotates through your templates while a turn is running:

"title": {
    "enabled": true,
    "templates": ["⏳ {phaseLabel} {elapsed}", "🤔 {phaseLabel}… {elapsed}"], // rotated every intervalMs
    "idleTemplate": "💤 dsh 空闲",   // "" = hand the title back to the host when idle
    "intervalMs": 8000
}

Templates support the same placeholders as phrases. When no turn is active the title shows idleTemplate; with idleTemplate: "" (or enabled: false) the plugin hands the title back to the host. title: false disables it entirely.

Editable from the settings page (since v0.27.0): DSH → Settings → Status Texts → Behavior has a Tab title group — an on/off switch, the templates (one per line), the idle title and the rotation interval. Saving writes it into the plugin's config store with everything else, so it survives plugin upgrades and you never have to hand-edit config.json.

It only writes a title it took over itself: the plugin touches document.title only while that title is its own. If it never took one over — or already handed it back — it does not touch it at all, including the session title the host writes ( — DeepSeek Harness) and titles written by other plugins. Turning the switch off hands back the last host-written title and stops touching the title for good.

Fixed in v0.27.0. The old rule was "if the current title differs from the value cached at start-up, write it back", which overwrote any other writer — classically oh-my-dsh's brand rename (it rewrites a trailing DeepSeek Harness to Oh My DSH). The value read back could never equal the value written, so the title was rewritten every tick (scripts/title-coexistence-test.html measures 10 rewrites in 2.6 s with the session title wiped off the tab; 1 write after the fix).

Presets & Scheduling

A preset is a named bank snapshot (optionally with its own config), switched from the settings page or automatically by schedule rules:

"presets": [{ "id": "night", "name": "Night", "phrases": { "zh": { "thinking": ["夜深了…"] } } }],
"activePreset": null,
"schedule": [{ "preset": "night", "days": [1,2,3,4,5], "from": "22:00", "to": "06:00" }]

• days runs 0 (Sunday) to 6 (Saturday); from / to may cross midnight (22:00 → 06:00);
• While a window matches, that preset is active; outside it the plugin returns to activePreset. The Automation tab has a visual editor and shows the effective preset live;
• Keys a preset leaves out fall back to the global config.

Extending it from another plugin

Since v0.31.0 the browser half publishes a registration API on the host context, so another plugin can contribute content without touching this plugin's source:

// in the other plugin's client half
export const inject = ["statusRotator"];   // or ctx.get("statusRotator") when it is optional
export function apply(ctx) {
    const api = ctx.statusRotator;
    api.registerPack({ id: "my-pack", label: { zh: "我的词库", en: "My pack" },
                       phrases: { zh: { running: ["正在替我干活…"] } } });
    api.registerPlaceholder("myState", () => "3 项");
    api.registerPhraseProvider({ id: "my-provider", provide: (site) => (
        site.phase === "long" ? [{ text: "第三方条件句…", when: { phase: "long" } }] : []
    ) });
}

| Call | Adds | |---|---| | registerPlaceholder(name, resolve, { live }?) | a {name} placeholder usable in phrases and title templates | | registerPhraseProvider(fn \| { id, provide }) | a dynamic phrase source, re-read on every rotation | | registerPack({ id, label?, phrases }) | a named bank, merged exactly like a document pack | | sendDanmaku(text) | fly one of your own lines across as a scrolling bullet (queued while the host mask pauses the layer) |

• All three return an unregister function — call it when your plugin unloads, and your content goes away with it;
• Registering the same name/id twice, or claiming a built-in placeholder name (elapsed, pending, phase, …), throws; a provider that throws on its first call, or returns something that is not entries, throws at registration. Failures are explicit — never "silently nothing appears";
• A provider that only breaks later is recorded in status().failures, warned about once, and skipped for that pick; the status line keeps running;
• Providers receive { locale, phase } and return an array of entries (the same shapes as the bank: a plain string or { text, weight, when, rarity }), or a { thinking, running, long } table. An empty array is a valid "nothing right now";
• External content goes through the same pipeline as the shipped bank — pack dedup by text, when / rarity, the shuffle bag — and never enters the config document: registering writes no config, and a settings save neither persists nor drops it;
• api.status() reports what is registered and which keys have failed; api.version is currently 1 and would increment on a breaking change.

Configuration

Phrases are fully separated from the source code and live in JSON config files. There are two config files at the project root:

• config.example.json — the complete template committed to the repo: default config + all phrases (bilingual, split into three phases);
• config.json — your local personalized config, initialized by node gen-config.cjs (only created when missing, never overwrites your changes). It's in .gitignore, so edit freely without polluting git.

Writing the config from outside (ETag / If-Match)

Every GET carries an ETag; send it back as If-Match and a write based on a stale copy is rejected instead of clobbering the other writer:

| Request | Result | |---|---| | PUT without If-Match | 200 — an unconditional write. Preconditions are the client's choice in HTTP, so existing scripts keep working; they simply get no concurrency protection | | PUT with a stale If-Match | 409 conflict, with the current ETag in the body — the write is rejected instead of clobbering the other writer | | PUT with the current If-Match | 200, and the response carries the new ETag | | PUT with If-Match: * | 200 — an explicit "overwrite whatever is there" for scripts | | GET with If-None-Match | 304 when nothing changed (no body) |

Read → write with the ETag you were given; on 409 re-read and re-apply. The settings page always sends it, so two tabs of the settings page can never silently overwrite each other; on a conflict it tells you the save was rejected and reloads the latest config instead of leaving the editor showing an edit the server never accepted.

Hot-reloadable external bank

Since v0.20.0 the node half also reads an optional phrase bank file outside the package — $DSH_HOME/status-rotator/phrases.json by default, overridable with the DSH_STATUS_ROTATOR_BANK environment variable (absolute path, or relative to the process working directory). It is plain JSON with the same shape as config.example.json, but you only need the keys you want to override — the minimal file is one pack and one phase:

{ "packs": [{ "id": "china-ai", "phrases": { "zh": { "thinking": ["正在飞唐杰马…"] } } }] }

The node half inspects the file on every request: when it changes it is re-read and re-parsed (an mtimeNs + size fast path, then a content comparison, so a rewrite within the same timestamp tick is still caught), and the server-side change detector turns that into a push within a couple of seconds — no process restart, no reinstall, no republished npm package, and no waiting for a client poll. Rules:

• only packs / phrases are taken from that file; a config key inside it is ignored, so runtime options stay under the settings page / config.json;
• the bank is the highest-precedence phrase layer: the effective document is merged as bundled config.example.json → config.json → auto-updated bank → user config store → external bank, and packs are merged per id, so declaring one pack leaves the other 11 untouched. To hand a pack back to the settings page, delete that pack from the bank file (bank content is never recorded as your change in the config store or the compatibility mirror, so the bundled / upstream copy comes straight back);
• the built-in bank stays the fallback: with no such file the plugin behaves exactly as before, and a corrupt file keeps the last successfully loaded copy in service while recording the error (externalBankStatus());
• verify it on a single process: node scripts/verify-phrase-hot-reload.cjs applies the plugin, starts a real HTTP server, GETs the route, rewrites the bank file twice and GETs again — all without a restart.

Auto-updating the bank

Since v0.21.0 the node half fetches the repo main config.example.json every 6 hours (jsDelivr by default, for reachability) and caches it at $DSH_HOME/status-rotator/bank.remote.json. The response is validated like any other layer, only packs / phrases are kept, and the cache is rewritten atomically only when the content actually changed — so merged submissions and the weekly star-pack refresh reach a running install without a restart, a reinstall or another npm release.

• DSH_STATUS_ROTATOR_BANK_URL — upstream address (your own mirror works); off or empty disables it;
• DSH_STATUS_ROTATOR_BANK_INTERVAL_MS — interval in ms (0 disables); unset = 6 hours.

Persistent storage (v0.6.1, and since v0.26.1 really in the plugin data directory): saved edits go to $DSH_HOME/status-rotator/config.json (path overridable with DSH_STATUS_ROTATOR_CONFIG) — next to the bank files, belonging to no package, so upgrades never touch it.

• Two silent failures came before: the config once lived in the plugin directory (replaced on upgrade), and the official dsh settings store turned out to have no register() on 0.1.7-rc.1, which killed that path and reset settings again (issue #51). Since v0.26.1 persistence no longer depends on the shape of the host settings API.
• The plugin-directory config.json stays as a compatibility mirror (written on save, and hand edits are absorbed into the store while the file still exists — checked on every GET, at the latest one reloadIntervalMs).
• The store holds only the diff against the bundled defaults; loading merges bundled default → config.json → auto-updated bank → user config store → external bank. Arrays with id (packs, presets) are compared per id and every save recomputes the diff from scratch, so reverting a value to its default simply removes it from the store (old installs converge too: 82,966 B → 1,586 B measured, no entries lost).

Version history lives in CHANGELOG.md. After upgrading, restart dsh web once so the node half picks up new code; a page refresh is enough on the client side.

```json { "config": { "intervalMs": 10000, "typeSpeedMs": 30, "longAfterMs": 60000, "reloadIntervalMs": 15000, "liveTickMs": 1000, "labelSource": "phrases", "weightedRandom": true, "debug": false, "fontWeight": "inherit", "gradient": { "e

... (README truncated for length)