← Back to list

dsh-smart-scenario-router

DeepSeek Harness Other Low risk

Routes dsh requests by conversation scenario and retries with fallback models when requests fail.

根据对话场景选择模型,并在请求失败时按候选链进行回退。

How to install

DeepSeek Harness dsh plugin add github:xobexo/dsh-smart-scenario-router

About

dsh-smart-scenario-router 为 DeepSeek Harness(dsh)提供基于对话场景的模型路由。插件会根据用户消息选择合适的模型,并在请求失败时按候选链自动回退。 功能 根据消息内容识别以下场景: 项目拆解 / 架构设计 插件查找 / 工具推荐 代码审查 代码变更对比 代码编写 / 调试 复杂推理 / 科研 / Agent 日常对话 / 快速问答 极速高并发 / 批量抽取 多模态(图文输入) 长文本 / 数据分析 优先使用国产模型,配置的 GPT 模型作为兜底。 请求失败时自动尝试当前场景的下一个模型。 低置信度的消息会使用 deepseek-v4-flash-0731 进行场景判断。 在 dsh Web 设置页显示模型池、场景映射和当前路由状态。 模型池配置会通过 dsh settings 持久化保存。 安装 要求: DeepSeek Harness >= 0.1.1-rc.1 Node.js 和 pnpm 已在 dsh 中配置至少一个可用的模型 Provider 直接从 GitHub 安装: powershell npx -y @deepseek-ai/dsh plugin --profile web add github:xobexo/dsh-smart-scenario-router 也可以使用完整仓库地址: powershell npx -y…

Recommendation signals

42 Tool quality · Based on stars, downloads, maintenance, security and docs
– User interest · Adjusted by in-site views, install copies and download clicks
42 Overall
0views
0unique visitors
0install copies
0download clicks
0outbound clicks

Meta

License
MIT
Language
JavaScript
GitHub stars
0
mo. downloads
–
Last push
2026-09-01
Created
2026-08-27

Links

GitHub ↗ Report issue ↗

Basic safety check

Findings
curated 收录但无 npm 包/安装命令
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
dsh-plugin, dsh-plugins

Related plugins

DeepSeek Harness
Score73

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.

☆ 202 ↓ 1.4K Other ↗
DeepSeek Harness
Score71

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.

☆ 1.5K ↓ 79.7K Other ↗
DeepSeek Harness
Score69

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.

☆ 9 ↓ 3.3K Other ↗
DeepSeek Harness
Score68

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.

☆ 8 ↓ 2.8K Other ↗