dsh-workspace-hub
DSH workspace hub: organize workspaces into color-coded folders in the sidebar (three-level drag reorder for folders/workspaces/sessions, inline edit, one-click expand/collapse, dual-channel search) with per-workspace and per-session token usage and cost stats from real session logs (official DeepSeek peak/off-peak pricing for any deepseek model, three spend calibers, hover detail cards, overview panel) plus OpenCode Go plan usage; data persists to host disk and refreshes live every 30 s.
DSH 工作区中枢：侧边栏将工作区按彩色分组管理（分组/工作区/会话三级拖拽排序、内联编辑、一键展开折叠、标题+消息双通道搜索），基于真实会话日志统计每工作区与每会话的 Token 与花费（任意 deepseek 模型自动按官方峰谷价计费、三种时段口径、悬停明细卡、总览面板），另含 OpenCode Go 额度；分组与结果持久化到本机磁盘，30 秒实时刷新。
How to install
dsh plugin add dsh-workspace-hub About
🗂️ dsh-workspace-hub — 工作区中枢 **DSH 工作区的一站式组织与洞察面板** — 分组归类、拖拽排序、内联编辑，配上 Token、花费与额度的实时统计，让每个工作区都一目了然。 --- ✨ 功能亮点 🗂️ 分组管理 **三层拖拽排序** — 分组卡片、工作区行、会话行随意拖放，带实时插入指示线，视觉与结果严格一致 **内联编辑** — 新建/重命名分组、工作区、会话全部就地完成，告别浏览器弹窗 **一键展开 / 折叠** — 全部分组一键收放，长列表不再翻到手酸 **🔍 消息搜索** — 标题 + 消息全文双通道，快速定位任意会话 **会话分叉 / 归档** — 生命周期操作一步到位 📊 Token 统计 **行内精简总量** — 工作区标题下方一眼看到消耗规模 **悬停明细卡** — 当前 / 含归档双口径，输入 / 输出 / 缓存读 / 缓存写四桶拆分，逐会话列表，按模型归因 **总览面板** — 合计、分组小计、工作区排行（条形占比）、逐会话明细 **🟢 实时刷新** — 每 30 秒自动静默刷新（标签页隐藏时自动暂停），聊天中的 token / 费用用量无需刷新页面即更新 💰 花费统计 **按模型 × 单价 × 时段** 精确计价，不是平均估算 **单价卡片设置** — 每个模型一张卡片，空闲 / 高峰两行三档单价 **🟢 deeps…
Recommendation signals
Meta
- License
- NOASSERTION
- Language
- JavaScript
- GitHub stars
- 2
- mo. downloads
- 420
- Last push
- 2026-08-22
- Created
- 2026-08-18
Basic safety check
- Findings
- None
- Sources
- curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
- Topics
- dsh-plugin, dsh-plugins
Related plugins
TokenLedger
zh667/TokenLedger
Sidebar usage panel that attributes tokens to the relay site that served each request, read from your existing provider config: today/month/all-time totals, per-site and per-model breakdowns, a year activity heatmap, and New API / Sub2API / DeepSeek balances.
dsh-context
bowenliang123/dsh-context
DSH context insight panel: Context dashboard + /context command + Context browser — one-stop context lifecycle management with categorized composition, content details, evolution trends, compaction/injection events, and stats.
dsh-usage-statistics-panel
HaoyueQin/dsh-usage-statistics-panel
Usage statistics settings panel: 26-week activity heatmap, daily token trend with a cache hit-rate curve, per-model donut and breakdown, time-range filters, summary cards, one-time historical backfill and lossless rebuild.
dsh-all-usage
ParticleLight/dsh-all-usage
Analyze usage across models, providers, workspaces, and time ranges — including custom start/end dates over the full retained history — with live cache-hit visibility and separate model and provider breakdowns. Includes hourly single-day trends, daily cross-day trends, a 53-week GitHub-style heatmap, usage streaks, model and workspace Token-share donut charts with Token, cost, and percentage details, independent combinable filters, cache-efficiency trends, DeepSeek account balance, workspace aliases, CSV export, and a durable ledger that preserves successfully flushed usage after session deletion — and after a workspace is deleted, where its recorded usage is summed into one Deleted row — and rebuilds incrementally — on restart, unchanged sessions are applied from the ledger without re-reading their logs (a per-session log revision is the change signal), and only changed/new events are folded. The workspace registry is kept fresh automatically through the DSH domain/changed probe: only added/removed workspaces are reprocessed incrementally, unchanged workspaces reuse their computed aggregates and ledger with zero rescan, and usage is strictly limited to DSH-registered workspaces (unregistered cwds are ignored). After a scan, lightweight revision status fetches full history only when the Host/data state changes and exposes non-sensitive sync health (revision reuse, rereads, ledger recovery, and failures). Token accounting is explicit: input is fresh (cache read/write and reasoning are separate buckets) and zero-usage replays never overwrite recorded usage. Chinese uses local time, English uses UTC; API access is loopback-only.