DSH plugin compatibility matrix
Every listing in this directory declares the DeepSeek Harness release it was checked against (`dshTarget`). This page unrolls that field: 33 plugins across 2 declared targets, with the verification level, scan status and maintenance health beside each one.
updated
- Listings
- 33
- Declared targets
- 2
- Scanned
- 0/33
- Run tested (L5)
- 0/33
Targeting rc.6 (25 plugins)
| Plugin | Verification | Scan | Health | Last checked |
|---|---|---|---|---|
| Archify tt-a1i | L1 Found | unverified | active | |
| DSH Desktop anywhere-labs | L1 Found | unverified | active | |
| DSH Web zhu1090093659 | L3 Install spec | unverified | active | |
| Ouroboros Q00 | L3 Install spec | unverified | active | |
| Modlens liustack | L3 Install spec | unverified | active | |
| Better Sidebar omdsh-dev | L3 Install spec | unverified | active | |
| DSH Market dsh-market | L3 Install spec | unverified | active | |
| OpenBiliClaw whiteguo233 | L3 Install spec | unverified | active | |
| DSH TUI ccch1mneyyy | L3 Install spec | unverified | active | |
| Deep Whale Small-tailqwq | L1 Found | unverified | active | |
| DSH Context bowenliang123 | L3 Install spec | unverified | active | |
| Aegis GanyuanRan | L3 Install spec | unverified | active | |
| Vision Router ysr666 | L3 Install spec | unverified | active | |
| Vision Toolkit Anionex | L3 Install spec | unverified | active | |
| Sandbase Harness sandbaseai | L3 Install spec | unverified | active | |
| DSH Browser Lum1104 | L3 Install spec | unverified | active | |
| Mnemon mnemon-dev | L3 Install spec | unverified | active | |
| GenUI omdsh-dev | L3 Install spec | unverified | active | |
| Modsearch liustack | L3 Install spec | unverified | active | |
| DSH Free Search DDDMUC | L3 Install spec | unverified | active | |
| Memento PerryLink | L3 Install spec | unverified | active | |
| DSH Imagegen dickpy | L3 Install spec | unverified | active | |
| DSH SSH Ops caoyiwei850 | L3 Install spec | unverified | active | |
| DSH Office Tools kw78 | L3 Install spec | unverified | active | |
| Background Agents PerryLink | L3 Install spec | unverified | active |
Targeting rc.5 (8 plugins)
| Plugin | Verification | Scan | Health | Last checked |
|---|---|---|---|---|
| Agent Teams NanmiCoder | L3 Install spec | unverified | active | |
| DSH Pocket shaobeichen | L3 Install spec | unverified | active | |
| deepseek-design Devin-AXIS | L1 Found | unverified | active | |
| dshcode whitelonng | L3 Install spec | unverified | active | |
| DSH Ads Nagi-ovo | L3 Install spec | unverified | active | |
| At File FSMargoo | L3 Install spec | unverified | active | |
| MisakaNet Ikalus1988 | L3 Install spec | unverified | active | |
| Deepread xiehuan123 | L3 Install spec | unverified | active |
How to read this matrix
dshTarget is the compatibility target the plugin author declares. It records that a release was checked, not that the plugin keeps working after upstream ships something new.
The verification level records how far the install path was exercised; the scan status records whether automated static analysis has run. Neither is a manual security audit.
Read the three columns together: L5 + scanned + active is a combination worth trying, while L3 + pending means reading the source yourself before you install.
Related pages
Compatibility questions
- Will a plugin with dshTarget rc.5 work on rc.6?
- Usually, but do not assume it. The field records the release the author checked; across releases the plugin still installs. If it fails to load or misbehaves after an upgrade, check whether upstream changed the manifest or bundle layout, then pin back to the declared release.
- Why do most plugins point at rc.6?
- 0 listings have been taken all the way to L5 (installed and actually run), and authors align new releases to the newest target. A listing on an older target is not broken, just checked earlier.
- Does this matrix replace testing it myself?
- No. The columns are check records, not a compatibility guarantee. Before installing, still read the listing’s permission surface and install command, and try it in an isolated profile first.