DSCODE Lets Multiple DeepSeek Coding Agents Collaborate on one Mac
DSCODE wraps DeepSeek with a persistent shell, sub-agents that can hand off tasks, and an independent reviewer that approves changes from your instructions.
- DSCODE is an MIT-licensed terminal coding agent for DeepSeek models, now at ~1,000+ GitHub stars.
- Multiple sessions on the same machine can list, read and send tasks to each other through a persisted mailbox.
- Ultra mode spawns sub-agents in isolated Git worktrees with independently chosen reasoning effort per child.
- Every code change is reviewed by a separate read-only model before the turn ends, with /review for manual passes.
- Installs via npm, a one-line installer, or prebuilt tarball; macOS 14+ and Node 22.19+ required.
- Supports DeepSeek, GLM, Kimi, Qwen directly and any OpenRouter model that can call tools.
DSCODE connects coding-agent sessions on one machine
DSCODE is an MIT-licensed terminal coding harness that lets multiple agent sessions on the same Mac discover, read, and message one another. Built on the DeepSeek Harness, it provides a terminal interface, CLI, and scripting entry point backed by one runtime and a pinned, reproducible installation.
Its coordination layer supports workflows that single-session agents handle poorly. One session can implement a feature, another can inspect the diff, and a separate reviewer can evaluate permissions from the user’s instructions. Persistent shells, isolated Git worktrees, and automatic code review keep those handoffs within the same local harness.
| Capability | Implementation |
|---|---|
| Interfaces | TUI, CLI, and scripting entry point |
| Session state | Persistent shell with retained working directory, environment variables, and background jobs |
| Coordination | Local session discovery, messaging, mailboxes, and transcript access |
| Delegation | Sub-agents with configurable effort and optional Git worktrees |
| Review | Separate read-only model for code changes and permission requests |
| License | MIT; model-provider usage is billed separately |
One shell keeps session state
Each DSCODE session owns a persistent shell that reads and writes files, runs tests, and preserves state across turns. The working directory, environment variables, and background jobs remain available, reducing the setup churn caused by launching a fresh subprocess for each action.
This story is for Pro members
You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.
Comments
