@mateobarbato/dsh-client-ui-peak-hour
DeepSeek Harness Web GUI 的编辑器上方高峰时段卡片，以及编辑器统计信息行中的下一高峰标签
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:MateoBarbato/deepseek-peak-hour-banner#832ac0887ffad08006f3bada020437665ae3b664Client Ui Peak Hour 以 @mateobarbato/dsh-client-ui-peak-hour 发布，当前版本为 1.0.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A DeepSeek Harness web-GUI plugin that keeps DeepSeek's peak-hour rates in sight, in two seats over one clock:
| State | Seat | Look |
|---|---|---|
| Peak | conversation.input.dock — the context strip above the composer, next to Todo / Goal / Queue | Amber card: ⚡ HORA PICO · tarifas al doble · Termina en 1 h 12 min · 04:00 UTC / 01:00 local |
| Off-peak | conversation.composer.dock — the composer footer, beside the shipped StatsPills row | Muted pill: ✓ Fuera de hora pico · próxima 22:00 local (en 1 h 12 min) |
Only one seat renders at a time, and each flips on its own at the next UTC boundary: the card sits above the composer exactly while the provider bills peak rates, and the schedule waits quietly in the footer the rest of the time.
Both strings are plain literals in lib/client.js and ship in Spanish; edit them to localize.
English | Español
Taken from the official pricing page (api-docs.deepseek.com/quick_start/pricing): off-peak rates are half of peak rates, and peak hours are 01:00–04:00 and 06:00–10:00 UTC, Monday through Friday. Every other hour is off-peak.
Windows are always evaluated in UTC, because that is what the provider bills in. Local clock time is only displayed, never used for the decision.
If DeepSeek ever changes the schedule, edit PEAK_WINDOWS_UTC in lib/client.js (offsets in minutes from UTC midnight) and reinstall.
web profile (dsh --profile web).patchReload: live (the shipped web profile is).The repository root is the plugin package, it declares itself a dsh.bundle, and its browser bundle is committed — so there is no build step and no build permission to grant.
git clone https://github.com/MateoBarbato/deepseek-peak-hour-banner.git
dsh plugin --profile web add ./deepseek-peak-hour-banner
dsh plugin forwards to pnpm in the profile directory, which links the checkout and appends the package to dsh.profile.bundles. The bundle patch (cordis.patch.yml) then inserts the plugin row, so nothing else is needed. Because the install is a link to your checkout, later edits to this repository are picked up on save — the host's client-HMR poll reloads the browser bundle within a second.
The same command accepts the other distribution forms, none of which need a build permission:
dsh plugin --profile web add @mateobarbato/dsh-client-ui-peak-hour # registry
dsh plugin --profile web add ./deepseek-peak-hour-banner-1.0.0.tgz # pnpm pack
dsh plugin --profile web add github:MateoBarbato/deepseek-peak-hour-banner
Verify the layer without booting, then restart the GUI (a bundle layer is composed at boot; only the profile patch hot-reloads):
dsh --profile web --dump-config # shows a "# == @mateobarbato/dsh-client-ui-peak-hour" layer
dsh plugin --profile web remove @mateobarbato/dsh-client-ui-peak-hour
| File | Role |
|---|---|
package.json | Declares dsh.bundle (the installable layer), dsh.client.platform: web, and the ./client export that dsh-client-modules discovers. |
cordis.patch.yml | The bundle layer: the insert row that mounts the plugin in a profile. |
lib/index.js | Host half: an empty apply(), present only so the row mounts in the host Loader tree. |
lib/client.js | Browser half: a classic script registering one lazy factory on window.__ModuleLoader__. |
test/schedule.test.mjs | Schedule test: window edges, the Friday→Monday gap, and a minute-by-minute scan. |
test/render.test.mjs | Render test: both seats server-rendered with real React under a frozen clock, one per state. |
Four contracts make this a plugin rather than a fork:
package.json declares dsh.bundle.patch, which answers "what does this package contribute?" with a patch layer. That is what makes dsh plugin add append the package to a profile's dsh.profile.bundles instead of installing it as an inert dependency.package.json declares dsh.client with platform: "web" and exports ./client, so the client-modules host half serves the bundle at /plugins/@mateobarbato/dsh-client-ui-peak-hour/client.js and puts it in window.__DSH_BOOT__.factory(require) → exports) whose exports are an ordinary Cordis plugin (apply + inject). react is a platform seed word, so no dsh.client.external entry is needed, and the factory body runs at materialization rather than at script load.--dsh-chat-content-width and it lines up with the composer card and the message action row instead of spanning the pane. The footer pill copies the StatsPills row instead: same column width, same centering, same --dsw-alias-label-tertiary colour and 13px scale, so it reads as one more stat rather than a second banner.StatsPillsStatsPills renders a root element in @deepseek-ai/dsh-client-ui-chat and exposes no slot inside it, so a plugin cannot add a child to that row — conversation.composer.dock is the slot that row occupies. Occupying it puts the pill in the same footer area and block, right after the stats, which is why the seat copies that row's geometry rather than nesting in it.
npm install # react + react-dom, used only by the render test
npm test # schedule logic + both seats rendered in both states
The browser half has no build step: lib/client.js is committed as-is. A linked install picks edits up on save — the host's client-HMR poll reloads the browser bundle within a second, and a page reload is the fallback. Only a change to cordis.patch.yml needs a restart, because bundle layers are composed at boot.
The package is ready for npm publish: the name is scoped to its author, files ships lib/, the patch and the docs, and there is no build output to produce (or pnpm pack if you would rather hand out a tarball).
Verified on dsh 0.1.5-rc.1 (web profile): the schedule logic and both seats are covered by the test suite, and the package composes into a profile's entry list as a bundle layer through the real Cordis patch engine. There is no end-to-end browser test.