engineering / agent

DSCODE

A macOS terminal coding agent built on DeepSeek Harness, with a persistent shell, sessions that can message each other and a separate review model.

Repository owner qiz029

Not rated yet
0 comments

Like 0 Save

Published 11 Oct 2026Listing updated 12 Oct 2026

At a glance

Purpose: A macOS terminal coding agent built on DeepSeek Harness, with a persistent shell, sessions that can message each other and a separate review model.
Runs in: Local agent with shell
Operating systems: macOS
Needs: Runtime: Node 22.19+ (22.x) or 24+, Git; Chrome for browsing; Needs internet: Yes; Needs accounts or API keys beyond your agent: Not stated
Files and data: Reads files: Yes; Writes files: Yes; Sends data to other services: Yes
Tool type: Agent
Delivery: From GitHub
Version: Latest on the main branch
Access: Code on GitHub
Compatibility: According to the README: macOS 14 or newer, Node.js 22.19 or newer on 22.x or Node.js 24 or newer, npm, Git, and Google Chrome for browser tasks. The README lists npm, Homebrew, a one-line install script, release tarballs for Apple silicon and Intel, and a source checkout. The README describes DeepSeek with an API key or account sign-in, OpenRouter, OpenCode Go, and custom Chat Completions, Responses or Anthropic Messages endpoints. The README says dscode acp connects ACP clients and additional MCP servers use config/mcp.local.yml. The README lists six interface languages. The README says it distributes the experimental Desktop package separately from the terminal packages.
External costs: According to the README, you connect your own model access: a DeepSeek API key or DeepSeek account sign-in, an OpenRouter key, an OpenCode Go subscription, or a custom endpoint with an optional key. The README states no prices. It says the footer shows cost, DeepSeek balance and cache figures. It says /review-usage shows the extra tokens and time spent on automatic review, and that memory model usage is tracked separately. The model provider you connect may charge for usage.
Permissions: The README describes persistent shell edits, patches, tests and background jobs. The README describes browser automation with dedicated persistent profiles, connections to existing Chrome and experimental extension sharing of selected tabs. The README says Computer Use permissions are granted separately in macOS and additional MCP servers use config/mcp.local.yml. The README describes approved Gmail sending, /delegate merging/staging child results and unattended cron, delay and supervised-script triggers; trigger install writes a launchd LaunchAgent. The README says project hooks load by default and ancestor skills and instructions are read toward home; DSCODE_PROJECT_HOOKS=0 limits hooks to the installation file, and DSCODE_SKILL_ANCESTORS=0 limits skill discovery to project and user roots. The README says workspace-write mode sends applicable approval requests to a model for review by default; /permission ask switches to human approval.
Usage terms: MIT License, as stated in the repository. See its LICENSE file for the exact terms.

Code on GitHub

qiz029/dscode

MIT

JavaScript1,028 stars4 forksLast pushed 12 Oct 2026 UTC

A DeepSeek coding agent harness: persistent shell, Ultra subagents, auto approval, Chrome MCP and session telemetry

Topics: agentic ai-agent cli code-review coding-agent deepseek deepseek-harness developer-tools

Public GitHub data fetched 13 Oct 2026 UTC · 0 days old

Skill folders in this repository (1)

Folders that contain a SKILL.md file, from GitHub's file list on 13 Oct 2026 UTC.

plugins/browser

View on GitHub ↗

What it does

According to the README, DSCODE is a terminal coding agent for macOS built on DeepSeek Harness. The README says its persistent shell reads and writes code and runs tests, with the TUI, CLI and scripts sharing a session runtime. The README describes sessions reading, messaging and handing tasks to one another.

The README lists dscode sessions, send, read and watch for interaction from another terminal, and dscode exec for scripts and CI. The README describes /btw as a side question in a read-only child session, /review as Git-diff review by a separate read-only model, /delegate as coordinated work in isolated Git worktrees, and /permission as selecting automatic review or human approval.

The README also describes cross-session memory, unattended triggers, email integration, browser tools and MCP servers. The README names DeepSeek, OpenRouter, OpenCode Go and custom endpoint routes.

Who it is for

Developers on macOS who want a terminal coding agent that works with DeepSeek and other model providers and can coordinate several sessions on one machine.

Example tasks

Run dscode exec "prompt" in a script or in CI.
Hand a task to another session with dscode send <session-id> --steer "review the change in parser.ts and reply".
Ask a side question inside the TUI with the /btw command.
Inside the TUI, plan a task on a board and run child agents in isolated Git worktrees with /delegate <task>.
Inside the TUI, switch between automatic review and human approval with /permission auto-review and /permission ask.

Getting started

The README says to install with npm install -g @toddzheng024/dscode, change into your project folder with cd /path/to/project and run dscode. The README says first launch installs a pinned preset from DSH Plugin Hub. The README instructs you to enter /login inside DSCODE and paste your DeepSeek API key into the hidden input. The README says to enter /provider openrouter to use OpenRouter. The README also lists Homebrew, a one-line install script, a release tarball and a source checkout. The README has the exact commands. The README offers global npm, Homebrew and curl-to-sh installs. The README says tar installs default to ~/.local/bin/dscode, npm/Hub state to ~/.local/share/dscode-hub, credentials to ~/.dscode/ and language settings to ~/.dsh/dsh-code/language.json.

Limitations

According to the README, DSCODE requires macOS 14 or newer, Node.js 22.19 or newer on 22.x or Node.js 24 or newer, npm and Git, with Google Chrome for browser tasks. The README says first launch installs a pinned preset from DSH Plugin Hub and model access requires a key or supported sign-in. The README describes DeepSeek, GLM, Kimi, Qwen and MiMo as its tuned models, with Anthropic, OpenAI, Google and xAI flagships supported on a best-effort basis. The README labels selected-tab extension sharing, the Desktop package, its browser preview and its native Computer Use adapter experimental; the Desktop plugin appears under a Community label. The README says native window observation and input still await qualification with macOS Accessibility permission, screenshot understanding needs an image-capable model, and Desktop scheduling delivery requires Desktop to stay open. The README says source, tar and npm/Hub installations use different data directories without migrating sessions or credentials between them. The README says dscode update requires no running DSCODE sessions. The README says a failed unattended trigger run does not notify anyone yet. The repository can change at any time; check its README before you install.

Data practices

The README says DeepSeek keys are stored in ~/.dscode/credentials.yaml with 0600 permissions and DEEPSEEK_API_KEY takes precedence; OpenRouter keys use the same storage route. The README says sessions, credentials and statistics use installation-dependent data directories. The README describes sessions reading and messaging other sessions, with session cards showing the project, workspace and topics of recent user requests. The README says code-change review sends a Git diff, or changes since a snapshot outside Git, to a separate read-only model. The README describes background cross-session memory extraction, per-session or global disabling and separately tracked model usage. The README says image-capable custom models can receive screenshots and attachments when enabled, with text-only input by default. The README says OpenCode Go sessions search the web through Exa. The README says the TUI checks npm for updates at startup. The GitHub description names session telemetry, while the README describes local session metrics, logs and traces without specifying external telemetry collection or telemetry opt-out variables. The README describes using your DeepSeek or OpenRouter API key, an OpenCode Go subscription login, or a custom endpoint with an optional key. The README says /account signs in through the system browser, stores the grant locally and reads DeepSeek account identity and recharge and bonus balances; DSCODE_ACCOUNT_LOGIN=0 removes the account-login callback server.