A Week Reading DSH's Source: The Two Rules That Won Me Over

Description and use

DSH enables easy swapping of models, tools, and environments via configuration, and fully traces every run, simplifying debugging and extension.

Problem

Choosing an agent framework that is modular, traceable, and easy to extend was difficult; many frameworks lock in models or require deep code changes to swap tools.

Outcome

DSH’s plugin‑centric design and full run traceability allow developers to swap models, tools, and sandboxes via configuration, debug agent behavior step‑by‑step, and extend functionality with community plugins without modifying core code.

Workflow

• 1. Read DSH source and docs to understand plugin architecture.
• 2. Verify that swapping a provider (e.g., filesystem) only requires changing config.
• 3. Confirm that every model interaction is logged and reconstructible.
• 4. Install DSH via npx or clone repo and run pnpm dsh web.
• 5. Handle Node version and build traps (Node ≥22.19, run pnpm run build).
• 6. Add plugins with pnpm dsh plugin --profile web add <plugin> and restart server with --patch.
• 7. Verify plugin activation with pnpm dsh web --dump-config.
• 8. Explore marketplace plugins like dsh-web-ui, dsh-auto-mode, modlens, dsh-memory.

Evidence

everything is a plugin and every run is traceable

Source

swapping out one fs provider moves the entire Bash / PTY / LSP stack into a remote sandbox

Source