Each scenario recommends 2–4 audited plugins. Permissions, maintenance, whether it actually activates — checked before you install.
Four checks per plugin — permissions, maintenance, dsh.bundle, tests/CI. Failures are flagged in the open, and star counts don't stand in for quality.
The official line is THERE WILL BE COMPATIBILITY-BREAKING CHANGES. We review every release and tell you whether it's safe to upgrade.
Unlike flat directories, every scenario page ships a ready-to-use install plan plus the pitfalls to avoid.
Recreate the @file references, annotations and fullscreen TUI you're used to, and import your full session history into dsh.
The three most common install failures — missing dsh.bundle, outdated install syntax, skipped restarts — checked one by one.
Audit what each request actually carries, and find out where the overrun comes from.
See what a plugin reads and where it connects — get a risk report before installing.
A pre-upgrade checklist plus our release reviews — check first, upgrade second.
See per-turn cost, TPS and other usage numbers in real time.
Planner/executor splits and second-model review to bring the bill down.
Bridge vision onto text-only models: screenshot OCR, UI reconstruction, pixel-level diffs.
Git tooling with guardrails, multi-identity management, automatic blame tracing.
An open slot: no solid DSH plugin exists yet. The first one to appear gets audited and listed.
Terminal TUIs, sidebar workbenches, themes and milestone trackers.
dsh is in developer preview and plugin quality is all over the map. Every listed plugin goes through four checks, with failures flagged in the open:
Maintenance, dsh.bundle and tests/CI are collected automatically every day. Permissions are reviewed by hand — and if a review is more than 60 days old while the repo has moved on, the verdict drops back to Pending automatically. No review, no claim. Audit methodology →