Vision Router vs Vision Toolkit
These two listings overlap in this directory — they share a category or a use case, so they are candidates for the same job. Below is every field this directory checked, side by side: verification level, security scan, compatibility target and install command. Under the table: editorial notes on when to pick each side, and when neither is the right install.
Vision Router
ysr666
Eyes for text-only agents — an opt-in vision turn with pixel-level tools, and an anonymous keyless fallback that is not private.
Read the listingVision Toolkit
Anionex
A vision toolbox for text-only models covering image QA, long screenshot OCR, UI restoration and grounding.
Read the listing| Field | Vision Router | Vision Toolkit |
|---|---|---|
| Verification | L3 · Install spec | L3 · Install spec |
| Security scan | Unverified | Unverified |
| Health | Active | Active |
| dshTarget | 0.1.0-rc.8 through 0.1.5-rc.2 | >=0.1.0-rc.8 <0.2.0 |
| Last checked | 2026-09-18 | 2026-09-18 |
| Licence | MIT | MIT |
| Language | JavaScript | TypeScript |
| Stars (context only) | 1,106 | 882 |
| Categories | Tools & Capabilities, Models & Reasoning | Tools & Capabilities |
| Use cases | Vision & OCR | Vision & OCR |
| Install command | dsh plugin --profile web add dsh-vision-router | dsh plugin --profile web add @anionex/dsh-vision-toolkit |
Every row is a public field of the two listings. This page does not score plugin quality.
Scenario notes
Same audience, different product shape. VisionRouter adds vision into the conversation as turns and pixel tools, with a public keyless fallback. Vision-Toolkit is a broader toolbox — image QA, long-screenshot OCR, UI restoration, grounding — delivered as the native integration of a separate upstream project and declaring a harness target range. Decide by whether you need turn-level vision or a multi-tool vision chain.
When to pick Vision Router
Choose VisionRouter for conversational vision: “look at this crop,” “diff these two screenshots,” without adopting another upstream stack. It fits agents that only occasionally need eyes and want the lowest ceremony.
When to pick Vision Toolkit
Choose Vision-Toolkit when long screenshots and structured OCR are the actual workload, or when you want QA, restoration and grounding behind one install. Prefer it when a single upstream package tracks the harness target and you want that compatibility claim on the listing.
When neither fits
If both are already installed for trial, keep one vision contract — duplicate JSON shapes will fork your prompts and parsers. Security posture on anonymous endpoints applies to both; scanned status does not mean either was run in a sandbox.
Which to pick
- Both are at verification L3, so the difference is not how far the install was checked.
- They declare different harness targets (0.1.0-rc.8 through 0.1.5-rc.2 vs >=0.1.0-rc.8 <0.2.0); the older target may simply not have caught up with the current preview line.
Questions
- Are Vision Router and Vision Toolkit interchangeable?
- They overlap in what they do (they share at least one category or use case), but they differ in install path and how far they were checked: Vision Router is L3, Vision Toolkit is L3. Confirm the install command in the table above, then try it in an isolated profile.
- Which one is more current?
- Vision Router was checked more recently (2026-09-18 against 2026-09-18). That date is when this directory last verified the listing, not when the plugin last shipped a release.
- Can I install both?
- Sometimes — if they do not fight for the same tool name or UI slot. Vision Router is unverified and declares 0.1.0-rc.8 through 0.1.5-rc.2; Vision Toolkit is unverified and declares >=0.1.0-rc.8 <0.2.0. A later install that re-registers the same capability can silently override the first. Safer path: try each in an isolated profile, compare the registered tools, then combine only what does not collide.