DeepSeek Harness (native)

dsh-paseo adds a native provider to Paseo for DeepSeek Harness (dsh), so a Paseo agent runs as a DSH session instead of an ACP client. The conversation stays in Paseo's normal agent view, and the plugin adds no screens of its own. It is a community plugin, not an official DeepSeek or Paseo product.

Each Paseo agent session starts one dsh --profile paseo child process on the daemon machine and talks to it over a local stdio bridge. The process runs as your operating system user with the daemon's environment, so the credentials and permission policy are the ones DSH already uses; the plugin adds no sandbox of its own. Model and reasoning-effort choices come from the catalog DSH reports for the profile, so they follow your DSH configuration.

DeepSeek Harness must be installed and logged in on the daemon machine, with dsh on the daemon's PATH or set through the provider command override. The plugin needs Paseo 0.9.2 or newer and Node.js 22 or newer on the daemon, and DSH 0.2.1-rc.2 is the tested line. On first use it provisions ~/.dsh/profiles/paseo, and it never overwrites an existing profile file, so local edits to cordis.patch.yml survive reloads.

Composer features are passed to DSH rather than emulated. Attached images are admitted into DSH's attachment store, / commands and user-invocable skills come from DSH's registry, and steering, plan mode, question cards and permission prompts render as normal Paseo items. The session menu can switch the agent preset and permission mode when the profile declares them, the composer shows the context window and current occupancy that DSH reports, and each answer carries a small line with its first-token latency and output speed. Sessions persist by DSH session id, so a reopened agent resumes its context, and Paseo can list and import existing DSH sessions; an imported session replays its messages into the timeline.

Images flow one way. The model receives attached images, but Paseo's transcript renders an image only from an https:// Markdown URL, so a picture produced on the daemon has to be published to a URL first. Local paths, file:// URIs and base64 data URLs do not display.

Known limits: there is one dsh process per session, so each agent costs a process. Reloading the plugin or restarting the daemon ends a running turn, and the session has to be resumed. The provider id is deepseek-harness-native, which keeps it separate from an ACP deepseek-harness provider when both are installed. Windows and native iOS and Android clients are untested.