DeepSeek Harness for Paseo

Use the official DeepSeek Harness in Paseo — with native context resume and complete tool results.

A community-maintained Paseo 0.8 provider plugin, not a replacement agent loop or an official DeepSeek/Paseo endorsement. It runs dsh --profile acp; Paseo owns the chat UI. No custom client surface or patched Paseo app is required.

Install · Compatibility · Verification · Code review

[!IMPORTANT] Requirements: Paseo 0.8.x, daemon Node.js 22.19.0 or newer, and a separately installed official DeepSeek Harness executable. The supported and tested DSH versions are 0.1.5-rc.1 and 0.1.5-rc.2. The executable must be able to run dsh --version and dsh --profile acp.

What it does

• Registers provider ID deepseek-harness with Paseo.
• Launches the official ACP profile directly, without a shell and without a headless flag.
• Uses Paseo's public runAcpProvider shim for ACP lifecycle, permissions, prompts, timeline mapping, usage and configuration.
• Presents DSH's live model and reasoning-effort options without rewriting their wire IDs. DSH model IDs are opaque JSON strings.
• Passes configured MCP servers, images, environment variables and working directories to DSH session runtimes.
• Keeps complete raw tool output. The adapter maps an ACP tool update whose output is represented by typed content blocks, but has no rawOutput, to rawOutput: { content: ... } without flattening or truncating it.

Install prerequisites

Install a verified official DSH version on the daemon machine, then check that the daemon can find the executable on its PATH:

npm install -g --ignore-scripts @deepseek-ai/dsh@0.1.5-rc.2
dsh --version

Configure a DeepSeek key through official DSH Settings → Models (dsh web), or its documented environment/configuration mechanism. The official local store is $DSH_HOME/.credentials.yaml, with owner-only permissions on POSIX. See the official model configuration guide.

The plugin does not download, install, update or restart DSH. DSH itself owns credentials and provider configuration. Credentials may be supplied through DSH's normal configuration or environment; the plugin does not read DSH credential files, mirror sessions, or read private DSH transcripts.

By default the plugin resolves the executable as dsh. Set DSH_PASEO_COMMAND in the daemon's environment to an executable path to use another installation; setting it only in an unrelated terminal does not update a running desktop-managed daemon. This is a path, not a shell command string. DSH_PASEO_PROFILE defaults to acp; any override must still expose the ACP stdio protocol, not the web/TUI profile. Custom profiles are untested. Capability/catalog/session-list probes use the daemon environment. Session runtimes receive that environment merged with per-session Paseo overrides, so variables such as DSH_HOME are preserved for the session. The parent process environment is never mutated.

The verified runtime compositions use CLI 0.1.5-rc.1 or 0.1.5-rc.2 with @deepseek-ai/dsh-acp 0.1.5-rc.2 and ACP SDK 1.4.0. The plugin probes the CLI version and explicitly accepts only the two DSH versions listed above; it does not claim compatibility with other package closures.

ACP compatibility and limitations

DSH advertises session/resume but not ACP's older top-level loadSession capability. Paseo 0.8's public ACP shim uses session/load when it sees persistence. A small typed stdio adapter therefore does the following:

1. After initialize, if the peer has session/resume and does not have loadSession, it exposes loadSession only to the private shim-facing stream.
2. It translates that stream's session/load request to session/resume, keeping the same session ID, cwd, MCP servers, request ID and other fields.
3. It does not synthesize transcript replay. The shim emits restoration: "core" and Paseo owns the displayed history; DSH resumes context without replaying old updates.
4. It never retries with a new session after a resume error.

All other ACP frames pass through unchanged except for the narrow tool-output projection described above. Existing rawOutput wins, including null. Permission, error, cancellation, image, MCP, response and notification payloads are not flattened or discarded. The provider deliberately does not advertise or implement raw token deltas, commands, steering, plans, terminals, elicitation, client filesystem operations or other unsupported DSH surfaces. DSH model and reasoning configuration is exposed when the ACP server advertises it. The public ACP shim emits complete timeline snapshots; this plugin does not claim token-level or UI streaming.

The plugin has no local persistence layer, no daemon-side DSH session mirror, no custom persona or provider preset, and no permission-policy override. Activity or another Paseo client may choose how to preview a complete tool result; this provider does not truncate it.

The native Paseo timeline works without another plugin. Optional Readable Agent Activity adds bounded readable previews; that separate renderer requires Full detail.

Known side effects and boundaries: catalog discovery uses ACP session/new and can leave empty sessions in DSH's native session list. DSH profile settings remain authoritative; the generic ACP shim does not inject Paseo's extra systemPrompt. Real vision/MCP services, custom profiles, Windows and native iOS/Android clients have not been exercised. See verification.

Paseo installation

Review this trusted, unsandboxed plugin and install the directory or public repository on the intended daemon. For a repository installation:

paseo plugin add geoqiao/paseo-deepseek-harness --ref v0.1.0-beta.2 --host <your-host>
paseo plugin ls --host <your-host>

Select DeepSeek Harness when creating an agent in Paseo. Model and thinking choices come from the installed DSH profile. Plugins and DSH tools are trusted, unsandboxed code; file permissions do not hide credentials from tools running as your OS user. This adapter does not add a security sandbox.

The source manifest requires >=0.8.0 <0.9.0. Do not restart the daemon for this plugin. Follow Paseo's global plugin-enable and per-installation enable/disable rules; an existing disabled installation should remain disabled unless the user explicitly enables it.

Development and test entry point

The production entry is index.server.ts. The reusable server-side factory is server/provider.ts:

• createDeepSeekHarnessProvider(options?) returns a public ProviderRegistration plus an idempotent async dispose();
• createProvider is an alias;
• createDshAcpStream and createAcpCompatibilityStream are exported from server/dsh-compatibility.ts for focused ACP and lifecycle tests.

This makes an independent temporary script able to call the same ProviderRegistration.connect, send, onEvent and close path used by Paseo. Call await provider.dispose() when the owner stops, including if a connection is still being established or the host has already started closing it. The production entry does this in its async cleanup. Supply a key only in the child environment when performing an opt-in real-model check; do not persist it in this repository.

From this directory:

npm ci --ignore-scripts --legacy-peer-deps --no-audit --no-fund
npm run typecheck
npm run lint
npm test

The tests use the installed public Paseo 0.8 SDK, public runAcpProvider, ACP SDK 1.4.0 framing, and a fake ACP peer process. They cover catalog discovery, model and thinking options, multi-turn prompts, configuration, persistence resume, tool output fidelity, images, MCP, permissions, errors, cancellation, EOF and startup cleanup, concurrent environment/cwd isolation, unsupported capabilities, direct stream guards, and public-provider close during version probe, initialize, and prompt. Real DSH/model credentials are intentionally not part of the automated fixture.

Verification record

Automated checks use npm run typecheck, npm run lint and npm test. The verification record distinguishes fake-peer protocol tests, real official-API calls, actual daemon integration and untested clients.

A separate live check in the parent workspace exercised this production provider factory through the public Paseo SDK and the official DSH ACP peer. It ran three real-inference rounds for each of CLI 0.1.5-rc.1 and 0.1.5-rc.2 (the recorded four-model/v4-flash, reasoning-off checks passed), including two-turn memory, file write/read, a complete tool-output tail over 8,000 characters, and recovery of the same persistence context after both the provider and DSH processes restarted. Five usage events were received in each run; emitted events validated with the public ProviderEventSchema. Both installation closures resolved to DSH ACP 0.1.5-rc.2 and ACP SDK 1.4.0.

Separately, an installed macOS Paseo 0.8.0 daemon completed real turns and kept tool-output tails, prior displayed history and DSH context through a plugin disable/enable cycle. An initial host IPC shutdown race was fixed by explicit async cleanup ownership; the repeated installed cycle had no new IPC errors, and the following real turn retained context and history. The current 32-test suite includes pending-connect and close-ordering regressions; exact evidence is tracked in verification. The post-release review adds diagnostic-redaction, timeout, missing-workspace and defensive-input regressions without changing the ACP mappings. These are backend tests, not a desktop UI matrix or mobile-device test. Official DSH does not provide raw token deltas, provider-specific commands, steering, transcript replay, or its own plan/ terminal UI surfaces; those are not claimed by this plugin. Credentials and private session contents are not stored in the repository.

Community catalog

Submitted to paseo.cafe in PR #87. Pending maintainer review — not yet accepted or listed. The entry uses the provider category and flags prerequisites, beta compatibility, safety, persistence semantics, unsupported surfaces and verification limits. Its source is docs/catalog-entry.json; publication of this plugin and acceptance into the community catalog are separate actions.

License

MIT. DeepSeek Harness and its official packages remain under their own licenses.