CLI tool
yjh051108/dsh-routing-suite avatar
yjh051108/dsh-routing-suite

dsh-routing-suite: three DSH components that install three different ways

dsh-routing-suite — injector + router-standard kit: install the runtime injector first, then the task-aware reasoning-mode router preset (measured P1-P23).

7,029 stars198 forksJavaScriptMIT

At a glance

What is it?
A single DSH plugin repository carrying a runtime injector, a reasoning-mode router preset and a graded task protocol. The plugin command installs the injector; the presets are copied by install.ps1 or by hand, and graded mode ships as a tarball.
Who is it for?
Adopt the injector and the router preset if you already run DSH and can live with a preview host, because the preset copy step is manual and the notes state that breaking changes are coming. Leave graded mode alone if you need one settled artifact, since the two tarball names given for it do not agree.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 58 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • yjh051108/dsh-routing-suite7,029 ★ · -125
Star history
Repository2026-09-102026-11-15
yjh051108/dsh-routing-suite7.2k7k

-125 Stars in the last 66 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

One repository, three components, three install paths

The repository name suggests a bundle, and it is one in the source tree but not in the install. `injector/`, `preset/` and `graded/` are ordinary directories checked into the repo, moved off submodules by the migration recorded in docs/FLATTEN-MIGRATION.md. What the one-command path actually fetches is the injector:

powershell
dsh plugin --profile web add github:yjh051108/dsh-routing-suite

The router presets are not on that path. `preset/router-standard` and `preset/router-spec` are copied into your profile directory either by `.\install.ps1` after cloning, which the README says assembles the injector, copies the presets and checks the layout, or by hand, and graded mode ships as a tarball you add separately. Read the single command as step one of three. Note too that package.json names the package `@dsh-external/dsh-super-injector` at version 0.3.3, and its `files` array ships only `injector/lib` and `injector/scripts`, so nothing from `preset/` or `graded/` travels inside the npm tarball.

Flat copy or DSH discovers nothing

DSH scans only the first level beneath `.agent-presets`, so the copy has to be flat. Two lines per preset do it:

powershell
$target = Join-Path $env:USERPROFILE '.dsh\.agent-presets\router-standard'
Copy-Item -Recurse .\preset\router-standard $target

The same pair of lines runs for `router-spec`. The named mistake is copying the `preset` directory as a whole, which adds an extra nesting level so DSH cannot discover the preset at all. After copying, DSH has to be restarted, and Router Standard or Router Spec (experimental) only becomes selectable in a new session. `router-pro` is listed as planned and was not part of v0.3.0, so a session list offering three router options would not match this repository's state.

The first user message is now captured before the router arms

v0.3.0 changed how the opening turn of a session gets classified. The route now captures the first real user message through `agent/inbox/claimed` before assembly finishes, so the very first request is routed by task type. Before that change every session's first turn fell through to weak, where the model does its own classification. That gap matters most in short sessions and in an opening prompt that sets the tone for everything after it, because in those cases the band was effectively the model's own choice rather than the preset's.

Guidance rides along in agent/pre-step instead of costing a second call

Near-range guidance is injected after every user message, and v0.3.0 moved that injection to `agent/pre-step`. Two things changed with it. The guidance now travels in the same request as the user message, so it lands on the real chain instead of a path the assembled plugin never takes. And it no longer causes an extra API call per turn, which the release notes describe as having doubled the cost of each round beforehand. If you are working from older write-ups of this preset and budgeting two calls per turn, that figure belongs to the behaviour before v0.3.0.

Four bands, and one of them is labelled a trap

The router sorts incoming work into spec for planning and collective work, react for execution, weak where the model classifies the task itself, and mixed, which the preset summary names as a trap to be avoided. Which persona text a band receives depends on the model: a Pro model gets a spec sentence plus few-shot examples, reported as +5.0 discrimination, while Flash gets neutral plus classify, reported as +5.7. Those two numbers are the preset's own P1 to P23 summary, not an outside measurement.

The same summary reports near-range guidance hitting a 92 to 94 percent cache rate, 96 percent routing and 100 percent convergence, plus static persona anchors for review, convergence and off-topic drift that it credits with moving open-task completion from 0 percent to 100 percent. Plan mode survives the routing because only the persona section is replaced.

dev_router_mode lets the agent change its own routing

Three tools let the agent inspect and adjust this from inside a session: `dev_router_status` to read the current state, `dev_router_mode` to change it, and `dev_mode_subagent` for the subagent case. The injector contributes its own set on the same pattern, covering injection, hot reload, uninstall, promoting a side-mounted module and route self-healing.

The consequence is that a session can drift away from the band you expected, and the correction is a tool call rather than a file edit. Whether you want an agent rewriting its own routing mid-task is a policy decision, and nothing in the repository documentation frames it as one.

MIT in the README, BSD-3-Clause in package.json

Two different licenses are stated in one repository. The README says MIT and credits xiaobright/modeltest for the V4.1b evaluation and xiaobright/dsh-anchored-standard for the anchoring mechanism. package.json declares `license` as BSD-3-Clause and sets `private` to true. The repository's LICENSE file is reported by GitHub as MIT, matching the README, but package.json still disagrees, so treat that as open rather than picking the convenient answer.

The runtime requirements are narrower than the license story. `engines` asks for Node 22 or newer. Peer dependencies ask for `@deepseek-ai/dsh-tools` from 0.0.1-rc up to but not including 2, `cordis` from 4.0.0-rc up to but not including 5, and `schemastery` at ^3.18.0. The declared DSH target is `>=0.1.0-rc.6 <0.2.0`, and the README states plainly that DSH is a developer preview where breaking changes are expected.

graded mode installs from a tarball and audits itself with measure.mjs

graded mode is the least finished of the three, and its installation instructions are the least consistent. Its protocol runs from brainstorming through multiple-choice alignment, a north star decision, a written plan, injection by spec, check-ins, a group wrap-up and a final acceptance, backed by six tools, three modes, a red team gate and an audit endpoint. Installation is by tarball, and two different filenames are given for it: `graded/dsh-external-dsh-graded-mode-0.0.1-rc1.tgz` and `graded/dsh-graded-mode-3.2.0.tgz`. Which one a fresh clone holds is not stated.

The measurement side is what you can check yourself. `graded/scripts/measure.mjs` recomputes the reported session metrics from your own transcript and is documented as printing numbers only:

powershell
node scripts/measure.mjs 你的会话.jsonl

The study notes behind those numbers claim that without the protocol chain the late segments of a long task show one tool call and no image reads, while the protocol chain stays active throughout. The write-ups present this as a research slot rather than a settled result.

Editorial conclusion

Adopt the injector and the router preset if you already run DSH and can live with a preview host, because the preset copy step is manual and the notes state that breaking changes are coming. Leave graded mode alone if you need one settled artifact, since the two tarball names given for it do not agree. Before installing anything, read the two license statements side by side and confirm your DSH build falls inside >=0.1.0-rc.6 <0.2.0.

Frequently asked questions

What does DSH stand for in dsh-routing-suite?

The repository never spells the acronym out. What it does show is that DSH is the host agent runtime: peer dependencies name `@deepseek-ai/dsh-tools`, installation goes through `dsh plugin`, and the package keywords list deepseek-harness. The README also states that DSH is a developer preview.

Does dsh-routing-suite need a restart after the presets are copied?

Yes. The install steps end with restarting DSH, and Router Standard or Router Spec (experimental) only becomes selectable in a new session. The manual path also needs a flat copy into `.agent-presets`, because DSH scans only the first level of subdirectories.

Which DSH versions does dsh-routing-suite target?

The declared target range is `>=0.1.0-rc.6 <0.2.0`, with rc.8, 0.1.1-rc.2 and 0.1.2-alpha.1 already followed. Node 22 or newer is required, and DSH is described as a developer preview where breaking changes are expected.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. yjh051108/dsh-routing-suite on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/yjh051108-dsh-routing-suite.svg)](https://hysenlabs.com/projects/yjh051108-dsh-routing-suite)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/yjh051108-dsh-routing-suite.svg)](https://hysenlabs.com/projects/yjh051108-dsh-routing-suite)

Was this useful?