oh-dsh

In the DeepSeek Harness ecosystem, choosing an interface is often a pain: terminal lovers want a lightweight TUI, browser users want an accessible Web UI, and desktop developers want a full workbench. Even worse, AI Agent capabilities and local development tools like terminal, files, Git, and browser are usually fragmented, with sessions, credentials, and plugin state scattered across different environments. Oh-DSH is built to solve exactly this interface dilemma and environment fragmentation.

It provides Desktop, Web, and TUI experiences from a single ohdsh command, sharing sessions, credentials, skins, and plugin cache across all three surfaces while keeping separate profiles. The built-in local development workbench organizes Workspace, PTY terminal, browser, file browser, Side chat, and Trajectory in one place. Git Review lets you comment directly on diff lines and handle branch checkout, commit, and push from the same sidebar. A cross-surface plugin marketplace lets you search, preview, and install plugins consistently across Desktop, Web, and TUI, while clearly indicating which interfaces each plugin actually works on—so you never assume an install is effective everywhere.

Oh-DSH also respects different deployment needs: full, Web-only, and TUI-only distributions are available on demand, each bundling a fixed version of DSH and Node runtime without requiring a separate environment. @oh-dsh/skins provides a unified theme for all three surfaces, adapted to each layout and readability. The built-in @oh-dsh/vision gives Desktop, Web, and TUI the same view_image tool for OCR, image understanding, and UI diagnosis on local images, HTTP(S) images, or image data URLs in the Workspace, with credentials and vision backend configurable in native settings.

If you live in SSH or pure terminal environments, TUI-only is a natural fit; if you prefer a browser or lightweight server deployment, Web-only keeps things minimal; and if you want a desktop workbench that brings AI Agent and local development tools together, the full build is ready to go. Unified configuration and data live under ~/.ohdsh, and you can switch the whole directory via OH_DSH_HOME—making it suitable for everything from personal experimentation to team standardization.