Repository navigation
DSCODE 0.7.49
DSCODE 0.7.49
The terminal moves to Harness 0.2.1-rc.2, the release DeepSeek recommends for DeepSeek-V4.1-Flash-1017, and the OpenRouter and OpenCode Go routes stop pointing deepseek-flash at the retired V4 Flash. Background memory no longer fails on its own output limit.
DeepSeek V4.1 Flash 1017
DeepSeek updated deepseek-flash to DeepSeek-V4.1-Flash-1017 on 2026-10-17. The official route needs no change: the id, the 1M context, the low/high/max efforts and the prices are unchanged, and the live /models listing confirms them. Two other routes still mapped the official model to DeepSeek V4 Flash, which DeepSeek retired on 2026-09-10:
- OpenRouter.
/provider openrouterfromdeepseek-flashnow lands ondeepseek/deepseek-v4.1-flash-1017, the id OpenRouter lists for this build at DeepSeek's own rates. It used to land ondeepseek/deepseek-v4-flash, the text-only V4 Flash that OpenRouter still serves. The new id is also the route's default and replaces V4 Flash in the/modelpicker. Sessions on V4 Flash or the Septemberdeepseek/deepseek-v4.1-flashkeep running and switch back todeepseek-flash. - OpenCode Go. Go no longer lists
deepseek-v4-flashordeepseek-v4-flash-vision-exp, so a switch fromdeepseek-flashlanded on a model Go does not serve. It now lands ondeepseek-v4.1-flashand switches back todeepseek-flash. The two retired rows are gone from the Go catalog.
On OpenRouter, every DeepSeek V4.x id also received the effort spelling of the April V4 Flash and V4 Pro, which take none/high/xhigh: low went out as high and Max and Ultra as xhigh. V4.1 Flash, the 1017 build and the dated V4 snapshots list DeepSeek's own none/low/high/max, so they now receive those names, and only the two April ids keep the old spelling. This has affected deepseek/deepseek-v4.1-flash since it was added.
Whether Go's deepseek-v4.1-flash already serves the 1017 build cannot be read from its listing.
Harness 0.2.1-rc.2
The terminal's DSH packages move from 0.2.0-rc.2 to 0.2.1-rc.2, with cordis 4.0.5, schemastery 3.18.5 and Computer Use 0.3.4, the first Computer Use release that accepts this Harness. dsh-invariants, dsh-experimental-schedule-bundle and dsh-subagent-in-process-driver were not republished and are dropped; dsh-hooks-codex, which dsh no longer brings along, is now a direct dependency because DSCODE's hooks use it.
The Desktop package stays on 0.2.0-rc.2, the runtime of the official Desktop app. The runtime patches recognise which layout they are given, so the Desktop build applies its 0.2.0 patches unchanged.
Upstream changes that DSCODE adapts to:
-
Delegation.
subagentandsubagent_forkstart every child in the background and returnstarted subagent /name (id)at once; the runtime notifies the parent when the child settles. There is no longer a call that waits for the result, andrun_in_backgroundis gone. Child names, the child-onlyreasoning_effortonsubagent_forkandworktree: trueare carried onto the new tool. A worktree child now gets its directory through upstream's owncwd, andworktreeandcwdcannot be combined. The Desktop package keeps foreground calls. -
Working directory. The model is told its directory as runtime context, which also reports later changes, and the
{{cwd}}prompt variable no longer exists. The DSCODE persona and the terminal's identity line drop their "Your working directory is" sentence; the Desktop build restores it for runtimes without that context. -
Instructions above the project.
dsh-agent-instructionsreads the user-global file only from the processDSH_HOMEand ignores a row'sdshHome. DSCODE points that value at a file that also holds theAGENTS.md/CLAUDE.mdfiles above the project root, one per session on a shared Host, so a runtime patch honours it again. Without it those instructions, and their/reload, were lost. -
Credentials. The upstream store now ranks its file above an exported variable and lets a variable be overwritten. DSCODE keeps the order it documents:
DEEPSEEK_API_KEYand the other exported keys win and are read-only. The browser evaluation's key lookup follows the same order. -
Local carrier. The Gateway and the shared
/apihandler take the calling Peer instead of a connection-wide operator, so the socket and the TCP listener now speak through one owner Peer. Without it the host's forwarded-event stream, which every attached terminal holds, failed to open, and API calls reached the Gateway without a Peer. -
Effort for titles. The DeepSeek adapter no longer forces session-title requests to
off; the title provider picks that effort itself. DSCODE's Ultra mapping (ultrasent asmax) is unchanged. -
Smaller: the TUI's empty invariant companion is removed with the package it registered with, and the stale
tool-ralphrow that patched nothing is removed from the terminal composition. -
Concurrent Host starts. When its launch loses the lock and no Host answers yet, a start launches again. A relaunch spawned just before the winner answered could reach the lock only after the winner was stopped, and then served with that earlier start's settings. On release CI the idle-exit check met such a Host with the default ten-minute idle time, and Linux timed out stopping one. Sampling
verify-host.mjsfive times per runner reproduced it once on macOS and once on Linux, and a sloweddscode host servereproduced it every time locally. Two changes close it. Each launch carries an id thathost/statusreports, and once a Host answers the start ends the process group of every launch of its own that is not that Host; the answering Host holds the lock, so such a launch cannot be serving.dscode host servealso takes the lock before the Harness boots and hands the locked descriptor down, so a losing launch exits at once with code 3 and the lock lives exactly as long as the Host.verify-host.mjsnow prints the answering Host's status, the state directory's processes and the Host log when a lifecycle step times out. -
Linux packages.
node-addon-require-builtin, which the plugin loader uses, moved from 0.1.6 to 0.1.9 with the new Harness and now ships separate glibc and musl native packages that declare their libc. The Linux packages are cross-built on macOS, where npm cannot match a declared libc and skipped the glibc build, so the release's Linux arm64 qualification found no native module and the Host did not start. The build now asks npm for glibc packages, which is what the Linux packages support. The packages grew from about 190 MB to 220–240 MB with the new Harness; the standalone check's install step now allows 180 seconds, as its update step does, after the Intel macOS runner passed the previous 60.
Upstream also brings fixes DSCODE did not have to adapt: empty assistant text blocks and empty assistant messages are no longer sent to DeepSeek, and a request extension that is not accepted after a 2xx response is logged instead of failing the request.
Background memory
Consolidation asked for at most 12,000 output tokens, while its own contract allows a 60,000-character handbook, and DeepSeek counts reasoning against the same limit. A real consolidation at high effort hit the limit after 48 seconds, so the run failed, published nothing and repeated on the next schedule. Each stage now has its own limit (24,000 tokens for an extraction, 64,000 for a consolidation), the request timeout is 180 seconds instead of 90, and a response cut off at the limit is reported as such. /memories status shows the reason with the failure instead of only "Background memory update failed".
The timeout still bounds a consolidation that would use its whole budget at the observed 250 tokens per second.
Verification
On macOS (arm64), npm run check passed: lint, both TypeScript configurations, 1,268 unit and component cases with 80.07% first-party .mjs line coverage, every integration verifier, the package checks and 63 offline evaluations. npm run doctor passed, including the DSCODE probe's worktree child, background fork worktree, child efforts and invalid-effort refusal on the new activation tool.
The Desktop line was checked against a separate 0.2.0-rc.2 runtime: the Desktop preset built with its 0.2.0 patches and the restored directory sentence, and verify-desktop-delegation.mjs passed its generate, resume and unload phases, foreground calls included.
Three live requests went through the upgraded runtime to the official deepseek-flash (1017): a plain reply at high effort, a shell tool call at Ultra, and a delegation at Ultra in which a child named probe ran a command and its report reached the parent. In that last run the parent waited with sleep before answering, which is how a model may now wait for a child.
The Checks workflow also failed on Node 22.19 since 0.7.48: Node 22's test runner ended the reconnect case in tests/remote-runtime.test.mjs while its only pending work was the unref'd reconnect pause. The case now keeps the event loop alive itself; the pause stays unref'd so a quitting terminal never waits on it.
New or changed cases: tests/memory.test.mjs checks each stage's limit and the reported reason; tests/child-effort.test.mjs, tests/dscode.test.mjs and the package verifier check the activation patches; tests/credentials.test.mjs and the browser route test keep environment precedence; the provider, OpenRouter and OpenCode Go tests and verify-login-runtime.mjs check the new DeepSeek counterparts and the effort spelling per V4.x id.
Not covered by an automated or live case:
- the OpenRouter and OpenCode Go switches and the corrected effort names with real keys, and pricing of the 1017 id's off-peak windows on OpenRouter (the fallback table uses the peak rate);
- a live consolidation completing within the new limit;
- a stale Host launch under a slow start: it was reproduced by temporarily delaying
dscode host serve(three failures without the fix, three passes with it) and by ten CI samples after the fix, but no committed case forces the delay; - the interactive TUI against a live model;
- Linux and Intel macOS locally (release CI qualifies those packages; all four packages were built and the Apple Silicon one passed
verify-standalone.mjson this machine); - the official Desktop app itself.