Plugins

MCP server manager (stdio / streamable-http): per-working-directory project and global config tiers; project-level MCP collapsed into 4 atomic tools through a middleware layer by default (`middleware: all` folds in global servers too, hot-switchable in the settings page); workspace isolation prevents cross-project interference; configs keep `${ENV}` references only, with no plaintext secrets on disk; runtime registration API for other plugins to inject MCP servers.

In-session cd for DeepSeek Harness: re-base relative paths on the fly (the file tools and the bash/pwsh default workdir follow) or move the session to another workspace for real — a `cd {"workspace": true, "confirmed": true}` call the user has agreed to, or the user's own `/cd <directory>` command, relocates the session's stored log, sandbox root, AGENTS.md and skill discovery and sidebar grouping. Per-session, persisted across restarts, without moving the session for a plain re-base.

Bridges the AtomCode terminal AI coding assistant already signed in on this machine into DeepSeek Harness as two side tools: atomcode_ask (a side-conversation relay with per-working-directory session continuity) and atomcode_review (a one-shot, bounded code review with structured findings). atomcode_ask needs no API key and takes over no model — it reuses the AtomCode session already signed in on this machine. atomcode_review additionally requires a direct provider (standard API with an explicit api_key) configured in DSH; without one it refuses before calling. The settings card adds a read-only CodingPlan quota read-out, and each tool names its own model default.

dsh-TUI /term: open a system terminal in a workspace folder — blank opens the working-directory root, a fragment fuzzy-matches folders (unlimited candidates, managed picker), with ordered per-platform launcher chains for Windows / macOS / Linux (incl. WSL