@linxin666/dsh-web-start-ui

dsh-web-start-ui · Startup Animation for the DeepSeek Harness (DSH) Web GUI

English | 中文

 

 

Startup animation for DeepSeek Harness (DSH)

Launch video skins · On screen before the shell paints · Click or Esc to skip · Its own settings page

An extension for the DSH Web GUI and desktop client: the page opens on a launch video instead of a cold, half-assembled shell, and the curtain lifts when the video ends. It ships one skin, accepts your own uploads, and adds one first-level settings page (Settings → Startup animation). No DSH source change, no third-party request.

What it does

• Playing before the GUI paints. The host half contributes one inline script to the served index.html, so the video element exists and is fetching ~30 ms into navigation. Measured on a 0.2.0-rc.2 host with the shipped skin: element at 3 ms, metadata at 211 ms, playback at 622 ms, while the GUI's own first paint is at 191 ms — the animation is already covering it.
• Adopted, not restarted. The browser half takes over that same `` element, so the animation keeps its buffer and its currentTime instead of jumping back to the start.
• Lifts when the video ends (and not before the shell has painted, bounded by a hold cap). A skin the browser cannot decode lifts on a safety timer instead: a broken video never becomes a wall in front of the GUI.
• Two sources of skins. One is shipped in the package; more can be uploaded from the settings page and deleted there again. See Launch skins.
• Skip on demand. Click anywhere or press Escape to lift it immediately.
• Theme aware. It follows the shell's light/dark preference, remembers it for the next boot's early backdrop, and honours prefers-reduced-motion.

How it works

Half	What it does
Host (src/index.ts)	Serves the launch-skin catalog and the video bytes (src/host/routes.ts: list, select, upload, delete, and Range-capable asset GETs; mutations are loopback-only on top of the platform's own browser auth), and contributes the served index's early backdrop: a global with the selected skin's URLs plus one inline script that paints the backdrop — and starts the video — before the module graph is requested.
Browser (src/client/index.ts)	Adopts the `` the host started, wraps it in the curtain (the theme backdrop, the skip footnote, the outro), removes the early layer it is covering, and registers the settings section.

The handoff is deliberately narrow: the early layer is pointer-events: none, one z-index step below the real curtain, and it is removed the instant the curtain exists (the adopted video is moved out of it first) — the outro fades to transparent, so a leftover backdrop would otherwise reappear as the GUI came back. A browser half that never loads leaves no dark window behind: the served row arms its own 15 s removal timer.

Launch skins

A launch skin is a video: one directory holding a skin.json manifest plus the video (and an optional poster frame). Video is the only medium — there is no style engine — so with no skin selected nothing plays at all. Two sources, one shape:

Source	Lives in	Gets there by
Built-in	assets/launch// in this package	node scripts/add-launch-skin.mjs --name "..." (--poster, --duration, --name-en optional)
Custom	/launch-animations//	the settings page: pick a file, it uploads to the host and becomes selectable

The selected id is host state (/launch-animations/state.json), so every browser of one install opens on the same curtain — and the host can start the video before the module graph is even requested: the served index carries the skin's URLs plus a small inline script that creates the ``, sets src and calls play(). The browser half then adopts that very element instead of restarting it (measured on a 0.2.0-rc.2 host: element at ~100 ms, GUI first paint at ~230 ms, animated curtain ~600 ms).

Selection. A stored choice wins; with nothing stored (a fresh install, or an id whose skin was replaced) the first built-in skin plays. Choosing No skin stores an explicit null, so the fallback never overrides a choice. The asset route answers with an ETag, so a cached install revalidates with a 304 instead of re-downloading megabytes.

What ships today: assets/launch/qinghua — 青花瓷 · 水墨 (Blue-and-White · Ink), 12.28 s, 2024×1080 HEVC, ~16 MB, with a poster frame.

Codec note. That skin is HEVC (H.265), which browsers play through platform hardware decoding. Chrome's canPlayType('video/mp4; codecs="hvc1"') reports no support and yet plays it fine when the machine has the decoder (verified: metadata at 211 ms, full playback to 12.28 s). On a machine without HEVC decoding the video errors out, the safety timer lifts the curtain, and no animation appears. To reach every machine, add an H.264 skin instead — node scripts/bake-skin-video.py --width 1920 --crf 26 --tune animation re-encodes to H.264 and pulls a poster frame.

Suggested spec for a new skin — it is fetched on first use and played on every boot, so it is the one asset that can make the GUI slower to appear:

Container	H.264 mp4 (custom uploads also accept webm and mov)
Picture	1920×1080, no audio track
Length	a few seconds is plenty; the curtain waits for the whole video
Size	under 8 MB
Last frame	the curtain fades out of it, so end on a calm frame

Custom skins are deleted from the settings page; built-ins cannot be (they are package files).

Settings

Control	Values	Notes
Enabled	on / off	Off boots straight to the interface — and skips the early backdrop with it.
Launch skin	No skin · the built-in skin · every uploaded one	The video that opens DSH; upload and delete custom skins from the same page.
Replay	Once per session · Every load	session writes a sessionStorage marker.
Click to skip	on / off	Escape always lifts the curtain.
Preview	button	Plays the selected skin once, right now.
Reset	button	Drops the stored playback preferences and returns to the defaults.

Install

This plugin is standalone on purpose: it is not part of the @linxin666/dsh-web-all aggregate, so it never arrives with the family bundle — install it where you want a launch video, and remove it the same way.

1. Install the package

# web profile
dsh plugin --profile web add @linxin666/dsh-web-start-ui

# desktop client profile
dsh plugin --profile desktop add @linxin666/dsh-web-start-ui

# or from a local checkout / the standalone repository, while developing it
dsh plugin --profile web add link:

Cloned the standalone repository instead? lib/ is committed there, so the link: install above works as-is. After editing src/, run pnpm install && pnpm run build to refresh it.

2. Restart the host

Quit and reopen the desktop app, or restart dsh web. A plugin's host half is loaded at startup — that half serves the skin catalog and starts the video before the interface paints, so a reload is not enough.

3. Open the settings page

Settings → 启动动画 / Startup animation. The shipped skin (青花瓷 · 水墨) is selected by default; press 预览动画 / Preview to watch it right there, or pick another skin.

Day to day

I want to…	Do this
Use my own video	添加自定义皮肤 → pick an mp4 / webm / mov (≤ 256 MB); it uploads to the host and is selected
Play nothing at all	choose 不用皮肤
Stop it for good	the 启用启动动画 switch, or uninstall the package
See it again	预览动画
Play it only once per window	播放频率 → 每个会话一次
Skip a long one	click anywhere, or press Esc
Delete an uploaded skin	删除 on its tile

Where things live

Shipped skins	/node_modules/@linxin666/dsh-web-start-ui/assets/launch//
Your uploads	/launch-animations// (default ~/.dsh/launch-animations)
The selected skin	/launch-animations/state.json
Playback preferences	browser storage — see Preferences

Uninstall

dsh plugin --profile web remove @linxin666/dsh-web-start-ui

Delete /launch-animations as well if the uploaded videos should go too.

Preferences

Split in two, on purpose:

• Playback preferences live in the browser — dsh:boot-animation:v1 (localStorage: enabled, replay policy, click to skip), dsh:boot-animation:theme (localStorage: the theme the last curtain painted in, which is the early backdrop's only way to know it before the shell exists) and dsh:boot-animation:played (sessionStorage: the once-per-session marker).
• The selected skin and the skins themselves are host state — /launch-animations/state.json and /launch-animations// — so every browser of the install opens on the same curtain, and the host can start the video before the module graph is requested. Nothing here is written to the profile configuration.

Feedback

Scan the code to join the group — bug reports, questions and skin contributions all belong there. When a curtain misbehaves, please say which skin (the tile name), the browser or client version, and whether the animation appeared at all: those three decide whether it is the host route, the codec or the shell handoff.

License

Apache-2.0