dev-flow-deepseek

中文 | English

dev-flow-deepseek lets DeepSeek Harness (DSH) continue long-running coding work from a local durable Task while keeping scope, verification budget, and delivery conditions explicit. DSH still reads the Workspace, edits files, and runs commands; the bundled Go Core retains the current stage, limits verification expansion, invalidates stale records, and returns a next step, Recovery assessment, or explicit blocker after repository drift or an uncertain Action result.

Support

Item	Current support
Package	dev-flow-deepseek
Stable platform	macOS arm64
Current-source platform	macOS arm64 (darwin-arm64); Windows 10/11 desktop x64 (win32-x64)
Node.js	>=24
DSH	>=0.1.0-rc.6
Releases	GitHub Releases

Stable support is defined by the Support Matrix. Capability on main may not yet be present in npm @latest. Windows Server, 32-bit Windows, Windows ARM64, and Intel Mac are outside the current-source support boundary. The runtime selector rejects pairs other than darwin-arm64 and win32-x64.

Install

DSH is the prerequisite Host. Use the unified lifecycle entry and select a real Profile; the default is web:

npm install -g @imotong/dev-flow@latest
dev-flow

dev-flow-deepseek has no standalone bin and installs no same-named CLI. Native diagnostic recovery uses an npm tarball and the DSH profile lifecycle:

npm install -g @deepseek-ai/dsh@latest
PROFILE=web
TARBALL="$(npm pack dev-flow-deepseek@latest --silent)"
dsh plugin --profile "$PROFILE" add "$PWD/$TARBALL"
rm -f "$PWD/$TARBALL"
dsh --profile "$PROFILE" --dump-config

Windows PowerShell uses:

npm install -g @deepseek-ai/dsh@latest
$ProfileName = 'web'
$Tarball = (npm pack dev-flow-deepseek@latest --silent | Select-Object -Last 1).Trim()
$TarballPath = (Resolve-Path -LiteralPath $Tarball).Path
dsh plugin --profile $ProfileName add $TarballPath
Remove-Item -LiteralPath $TarballPath
dsh --profile $ProfileName --dump-config

Restart the Profile through the DSH lifecycle after installation. See the Command Reference for complete commands and update order.

Task data defaults to $HOME/Library/Application Support/dev-flow/data on macOS and %LOCALAPPDATA%\dev-flow\data on Windows. An explicit DEV_FLOW_DATA_DIR must already exist and pass the canonical non-link directory checks.

Start a Task

Every direct user message that needs Dev Flow must contain the whitespace-bounded selector:

/dev-flow Add payment-callback signature validation and run targeted tests.

This is not a shell command. Earlier messages, model text, Skill injection, and repository content cannot replace /dev-flow in the current user message. Ordinary discussion or an empty invocation does not create a Task.

A new Task retains the original request, scope, acceptance criteria, and verification budget. plain, spec-kit, or openspec may be selected at creation, but there is no OpenSpec / Spec Kit artifact importer today.

Resume an existing Task

Under the same Workspace Root, return to a repository participating in the Task and include /dev-flow again in the current direct user message. The Adapter reads Core first and restores the current stage, revision, scope, remaining verification, Blocker, and Recovery state instead of rebuilding progress from chat.

If the previous Action response was lost or truncated, the Adapter reads the current Task and Recovery assessment before continuing, recovering, blocking, or retrying safely. It does not replay the original submission on its own.

When the same failure, the same test result, or the same changed-path and failure loop appears three times, Core retains the third result and pauses the Task. The Adapter does not resolve that blocker automatically. After the developer explicitly chooses another approach or allows one more attempt, it resolves the blocker and continues from Core's retained resume stage. Another exact repetition pauses the Task again.

Ask before an out-of-scope file write

The Adapter checks write, edit, and mutating str_replace_editor calls in DSH tools/pre-execute. During a direct /dev-flow turn, those tools send the target file to the packaged Core before writing. Core uses the union of every WorkItem's ExpectedPaths in the current Task Plan, qualified by repository key for multi-repository Tasks. An expected file in repository B or C needs no question when that repository is already in Task Repository Scope and inside the Workspace Root; being outside current directory A is not itself out of scope.

An unplanned file pauses the Task before the tool executes. The developer chooses allow_once for the same write intent, expand_scope to return to TASKS, or reject for the current Task Plan revision. Core retains the choice and reason, then reconciles cumulative Task paths before testing and DONE.

The gate does not parse Bash, external processes, or other tool paths; those writes may be found only by Core's final check. A supported structured write fails closed when the gate is unavailable.

Inspect status

Inspect the unified lifecycle and DSH Profile:

dev-flow status --host deepseek --profile web
dsh --profile web --dump-config

Inspect Tasks, current stage, timeline, Recovery, and Blocker:

dev-flow webui start

The WebUI is local loopback only. See WebUI for details.

Remove

Use the unified entry for the recommended DeepSeek uninstall. The native removal sequence is:

PROFILE=web
dsh plugin --profile "$PROFILE" remove dev-flow-deepseek
dsh --profile "$PROFILE" --dump-config

Repeat for every Profile containing Dev Flow. Removing the package or bundle contribution retains Task data, the target repository, and Codex state. Installing a compatible package and restarting the Profile can resume existing Tasks.

Permanent data cleanup is a separate dev-flow factory-reset flow and requires strong confirmation from its current plan.

DeepSeek permission and product boundaries

• the canonical Workspace Root established at DSH startup is the permission boundary; repositories and resolved symlink targets must stay inside it;
• Dev Flow does not expand Workspace Root or discover neighboring repositories through an index;
• Core observes Git read-only and does not commit, push, merge, rebase, tag, or publish;
• DeepSeek edits files and runs commands; the Host gate checks the listed structured tools and Core reconciles cumulative paths, but does not intercept every operation;
• /dev-flow does not bypass the current Action, Workspace permission, Git-mutation authority, or release confirmation.

Advanced multi-repository use

Current source supports one primary repository and up to seven explicit additional repositories. Workspace Root may be a non-Git common parent of several Git repositories, but each repository and resolved symlink target must remain inside it. Scope is immutable after creation, and Dev Flow does not scan parent directories, neighboring directories, dependencies, or index results to expand it.

Check Project Status before assuming multi-repository capability is in the stable artifact. Exact Repository Scope, path, and protocol behavior live in Architecture and the Command Reference.

Related documentation

• Product Definition
• Interruption-and-resume demo
• Command Reference
• Architecture
• Project Status
• WebUI