DeepSeek Harness 插件

dsh-ui-peak-rate

DSH web composer peak-rate badge: shows 2× when the session's model provider matches a configurable list during DeepSeek peak hours(英文原文)

跳到安装方式

来源信息

GitHub 仓库
haoliangwu/dsh-ui-peak-rate
最近更新
2026年8月17日
分类
记忆
GitHub stars
0
载体类型
plugin
目录证据
上游声明已找到 dsh.bundle
证据路径
package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-21

该证据由上游目录提供。本站没有安装、运行或安全审核这个插件。

安装

默认先复制一段 Prompt,让 Agent 读 GitHub 仓库和源码;需要自己装时再切到命令。

复制这段 Prompt,发给 DSH、Codex 或其他 Agent,让它先读 GitHub 仓库和源码。

请先不要安装或执行任何命令。阅读这个插件的 GitHub 仓库、README 和关键源码,然后用清楚、直接的方式回答以下问题,帮助我判断它是否适合我的需求:

1. 这个插件是什么,解决什么问题;
2. 适合哪些用户和典型使用场景;
3. 安装后如何使用,并给出一个最小使用示例;
4. 有哪些已知限制,以及隐私、安全、兼容性或维护风险;
5. 给出“推荐 / 有条件推荐 / 不推荐”的明确建议和理由。

请区分仓库明确说明、根据源码推断和未知信息。证据不足时请明确说明,不要猜测或照抄 README。

GitHub:https://github.com/haoliangwu/dsh-ui-peak-rate
插件名:dsh-ui-peak-rate
作者:haoliangwu

检查来源文件

安装前先看这个插件目录里的 README 和其他文件。

文件资源管理器3 个文件
README.md来源说明 · 只读预览

<h1 align="center">dsh-ui-peak-rate</h1>

<p align="center">DSH web composer 🔥 2× peak-rate badge — shows when the session's model selection matches a DeepSeek peak-rate route during DeepSeek peak hours.</p>

<p align="center"><img src="docs/peak-rate-badge.png" alt="Peak-rate badge in the composer trailing row" width="640"></p>

A web client plugin for DeepSeek Harness. It paints a 🔥 2× pill in the composer's trailing input row, just left of the model trigger, when both of these hold:

1. The session's current model selection matches the DeepSeek peak-rate policy (see [Match rule](#match-rule)). 2. The current time is peak-priced: a weekday (Monday–Friday, Beijing time) whose UTC hour is inside a DeepSeek peak window (by default 01:00–04:00 UTC or 06:00–10:00 UTC, configurable).

Weekends (Saturday and Sunday, Beijing time) are all-day off-peak per the billing rule effective 2026-08-23, so the badge never shows then.

Otherwise the badge is hidden entirely — no layout cost.

Install

dsh plugin --profile web add github:haoliangwu/dsh-ui-peak-rate

Built lib/ is committed, so the git install is one line — no prepare script, no allowBuilds permission. Restart dsh --profile web after install (bundle layer stacks compose at boot).

Configure

All three fields default to the DeepSeek peak-rate policy; override any of them in your profile's cordis.patch.yml (~/.dsh/profiles/web/cordis.patch.yml):

- id: dsh-ui-peak-rate
  config:
    # Provider ids whose sessions may show the badge (default: ['deepseek-official'])
    providers:
      - deepseek-official
    # Peak windows [startHour, endHour) UTC, left-closed right-open (default: [[1,4],[6,10]])
    peakWindows:
      - [1, 4]
      - [6, 10]
    # Peak multiplier vs off-peak rate (default: 2)
    multiplier: 2

An empty peakWindows: [] disables the badge entirely (always off-peak). Invalid windows (start >= end, start < 0, or end > 24) fail loud at load.

Disable the badge entirely:

- id: dsh-ui-peak-rate
  disabled: true

The host half reads Config (schemastery) and exposes it to the browser half through a Connection RPC channel (/peak-rate endpoint config). No transport carries host plugin Config into the browser context automatically; the RPC channel is the explicit transport.

Match rule

The badge shows when the session's current model selection satisfies both of:

  • state.current.provider ∈ Config.providers (provider match, default ['deepseek-official']), AND
  • state.current.model contains deepseek (case-insensitive).

The model-id check narrows the provider list so a non-DeepSeek model routed through a listed provider does not trigger the badge. To match a provider whose model ids do not contain deepseek, neither condition holds and the badge stays hidden — extend Config.providers only when the route actually serves DeepSeek peak-priced models.

How it works

  • Peak state is a pure client-side clock fact. isPeakRate(date, windows) returns true iff the date is a weekday (Beijing time, UTC+8) whose UTC hour is inside one of the configured windows (left-closed, right-open). Weekends are all-day off-peak. The weekend boundary follows Beijing time — the billing rule's stated timezone — so Beijing Saturday 00:00 (UTC Friday 16:00) and Beijing Monday 00:00 (UTC Sunday 16:00) are classified correctly, not by their UTC weekday. The component re-evaluates every 60 s through a setInterval cleared on unmount, and re-evaluates immediately when the config arrives.
  • The peak-rate policy is fetched once from the host through a Connection RPC channel. The host half registers ctx.connection.rpc.handle('/peak-rate', ...), reads Config (schemastery: providers, peakWindows, multiplier) from the profile's cordis.patch.yml, and returns it on the config endpoint. The browser half calls ctx.connection.rpc.call('/peak-rate', 'config', {}) once and exposes the result as a reactive source (useSyncExternalStore); the badge stays hidden until the fetch settles.
  • The badge and tooltip render from locale dictionaries with config values interpolated. The badge text is 🔥 {multiplier}×; the tooltip lists the formatted windows and multiplier ({windows} / {multiplier} placeholders, e.g. 01:00–04:00, 06:00–10:00).
  • The component reads the session's current selection through ctx.modelDirectories.directoryFor(sessionId).store (the same instance ModelSelect reads), subscribes via useSyncExternalStore, and applies the [match rule](#match-rule).
  • No model-visible output, no session events, no durable state. The plugin reads only the clock, the existing model-directory store, and the one-shot policy fetch. The peak schedule is a published 2026 constant; a DeepSeek schedule change requires a plugin update to the default peakWindows.

Build from source

pnpm install
pnpm build         # emits lib/index.js, lib/invariant.js, lib/client.js + sourcemaps

lib/ is committed to the repo so git installs work without a build step. After changing source, run pnpm build and commit the updated lib/.

License

MIT