DSH shared base profile bundle, inserts 100+ base plugin lines at once via cordis.patch.yml as the first layer for all profiles.
- Language
- TypeScript
- License
- MIT
- Branch
- main
Install
$ dsh plugin --profile web add @deepseek-ai/dsh-baseRun the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial
Install via your agent
Install the DeepSeek Harness plugin op7418/pilot-harness/packages/bundle/base for me: review the repository at https://github.com/op7418/pilot-harness first, then run the install command and verify the plugin loads successfully.
Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.
One-line Summary
This is DSH's shared base profile bundle. It contains no runtime code itself; instead, it uses a single cordis.patch.yml to lay out all of DSH's default foundational plugin rows (model adapters, tools, persistence, strategies, settings/credentials, telemetry, host-level subagent providers) onto an empty profile root in one go, serving as the first patch layer for every profile.
Core Capabilities
- One-time mounting of DSH's default model layer: DeepSeek official adapter, Pi-AI multi-provider adapter (mounted by default but waits for
llm-pi-ai:settings to enable),deepseek-v4-flashdefault model selection - Mounting agent, session, tool registry and settings/credential management: session persistence (JSONL), attachment disk-write, settings hot-reload, credential parsing
- Enabling built-in tool sets: bash/pwsh tools (one per platform), file system read/write, glob search, web search (DeepSeek search), Todo, SubAgent, Goal, Workflow, Ralph, Skill, etc.
- Enabling strategies and sandbox: workspace-write / read-only / danger-full-access three-tier permission presets, sandbox strategy, user approval, file watching strategy, token-meter, spill strategy
- Platform-gating two shell stacks: bash enabled on non-win32, pwsh enabled only on win32; each platform mounts exactly one shell stack
- Mounted but session telemetry disabled by default; requires
DSH_TELEMETRY_MODEenvironment variable to explicitly enable; SQLite full-text search also disabled by default
Technical Implementation
- Language: TypeScript (
src/index.tsis empty export, no runtime API) - Key Dependencies: 100+
@deepseek-ai/dsh-*packages in repository workspace (LLM/Agent/Session/FS/Sandbox/Tools/SubAgent, etc.), plus@deepseek-ai/cordis,@deepseek-ai/cordis-plugin-hmr,@deepseek-ai/cordis-plugin-timer - Architecture Pattern: Not a code plugin, but a profile bundle;
package.json'sdsh.bundle.patchmanifest field points tocordis.patch.yml, which the profile composer reads and inserts the foundational plugin rows into an empty profile root via "whole-row config replacement"; subsequent bundle layers (web-app, headless, etc.) and usercordis.patch.ymloverride these rows by ID - Entry Files:
cordis.patch.yml(the actual effective "content"), plussrc/index.ts(empty export placeholder),src/invariant.ts(invariant companion with no runtime checks)
Use Cases
This is the first layer carried by all DSH profiles (headless, web-app, user-defined profiles, etc.) by default; when you need to build custom agents, CLI mode, web mode, or workflows on top of DSH, the base bundle already has all the essential core capabilities (model layer, agent loop, session, tools, permissions, sandbox, persistence) installed—no need to individually integrate each dsh-* package. The base bundle is typically not installed standalone; it takes effect together with any upper-layer profile bundle (headless, web-app, etc.).
Prerequisites & Compatibility
| Dependency | Minimum Version | Description |
|---|---|---|
| DSH Framework | 0.1.0-rc.7 same generation | Released in sync with other @deepseek-ai/dsh-* packages in repository workspace |
| Node.js | ^22.19.0 || >=24.0.0 | See engines.node in root package.json |
| macOS / Linux | — | bash-sandbox, tool-bash enabled; pwsh rows disabled |
| Windows | — | pwsh-sandbox, tool-pwsh enabled; bash rows disabled, can be restored via profile override |
| Platform Restriction | Cross-platform | Same patch file auto-gates two shell stacks by process.platform |
| Native Modules | None | No native modules introduced; win32 sandbox chain provided separately by @deepseek-ai/dsh-sandbox-windows-acl |
Installation
dsh plugin --profile web add github:op7418/pilot-harness/packages/bundle/base
Configuration
The base bundle itself has no "user-level" configuration switches; it hardcodes or binds to environment variables the config of several plugin rows via the patch file. Environment variables appearing in the patch file and their defaults are as follows:
| Environment Variable / Config Source | Value | Description |
|---|---|---|
DSH_TELEMETRY_MODE | Default DISABLED | Controls session telemetry mode; set to FULL or FEEDBACK_ONLY to actually report |
DSH_TELEMETRY_OTLP_URL | Default https://harness-telemetry.deepseeksvc.com/v1/logs | OTLP/HTTP reporting endpoint |
DSH_TELEMETRY_DISABLED | Any non-empty value | Setting to non-empty disables telemetry (including '0', 'false'); launcher rewrites this to disabled |
DSH_PERMISSION_MODE | Default workspace-write | Global permission mode;可选 read-only / workspace-write / danger-full-access |
DEEPSEEK_API_KEY | Required (production) | Credentials needed for session title parsing, web search, and chat model calls; resolved on-demand by dsh-credentials-local |
| agent-default-model's provider/model | deepseek-official / deepseek-v4-flash | Default agent model and adapter; can be overridden in user settings.yaml |
| session-title-llm title length | Target 5 words / 10 CJK chars | Length target and upper limit for auto-generated session titles |
| bash-sandbox timeout | 60000 ms | Default timeout for bash command execution |
| Tool result trimming | Threshold 8192 chars, first 4096 + last 1024 | Trimming window for tool returns that are too long before entering conversation |
| Ralph subagent max rounds | 64 | Maximum iteration rounds for Ralph tool |
FAQ
Q: After installing the base bundle, what else do I need?
A: The base bundle only provides the "foundation"—the core shared by all profiles; it doesn't expose CLI entry points. To use CLI, append dsh-headless to the profile's dsh.profile.bundles; for a web interface, append dsh-web-app. These upper-layer profiles have already overlaid specific configurations on the patch; base is just the bottom layer.
Q: Can I override the default model on top of base?
A: Yes, but you must use "whole-row replacement": in the profile or home's cordis.patch.yml, write an insert row with the same ID agent-default-model, restate the provider and model fields to replace the entire row that base wrote. You can also directly modify the llm-deepseek: section in settings.yaml via the web UI settings page, which takes effect after restart.
Q: On Windows I want to use bash tools instead of pwsh, what should I do?
A: In the profile or home's cordis.patch.yml, write two modifications simultaneously: rewrite pwsh-sandbox and tool-pwsh to disabled: true, then delete or set to false the disabled field for bash-sandbox and tool-bash. Both commands register the same bash service; an incomplete recipe will throw an error directly at load time.
Q: How to enable the content search that's off by default?
A: The session-query-sqlite mounted in base has openAt: never by default, and the SQLite file won't be opened. Override this row in a subsequent profile layer, set openAt to first-search or startup, and provide a persistent path—full-text search will then be enabled.
Q: After uninstalling or resetting base, will existing session records be lost?
A: No. Base doesn't directly persist data; sessions are written by dsh-session-persistence-jsonl to $DSH_HOME/sessions/, and attachments are written to the attachment backend directory. Uninstalling or rewriting base won't delete these directories; however, if you also disable session-persistence-jsonl or attachment-local, new sessions will land elsewhere, while old sessions can still be read by search-enabled profiles.
Q: What to do when errors like "row is disabled by config" appear at startup?
A: Usually caused by illegal disable configuration in user-layer cordis.patch.yml, or conflict with base's platform gating. Check whether the user patch has incomplete overrides for bash/pwsh/sandbox rows (see the Windows bash restoration note), and confirm whether DSH_PERMISSION_MODE takes a value not registered in the permission presets.
Getting Started
Beginner — The base bundle has no user-level API, requires no coding and no separate configuration; regular users install it once via dsh plugin add and it's automatically applied by upper-layer profiles; custom developers only need to understand cordis.patch.yml and "whole-row replacement" semantics to make modifications.
Known Issues & Limitations
- Patch replaces entire row config, no deep merge: Profiles must restate all fields they want to preserve for that row; there's no per-field merge layer (see
packages/bundle/base/README.md:21) - Windows temp directory authorization is per-session private: workspace-write restricts writes to workspace + session's own temp subdirectory (
<temp>\dsh-<hash>), restricted subprocesses' TMP/TEMP are rewritten; read-only grants no temp write permissions. See@deepseek-ai/dsh-sandbox-windows-aclfor details - Won't auto-mount Codex / Claude Code provider: Base's dependency list doesn't include
@deepseek-ai/dsh-subagent-codexand@deepseek-ai/dsh-subagent-claude-code; whichever is needed must be opt-in by that profile individually - Same patch file gates two shell stacks by platform: bash row disabled on win32, pwsh row disabled on POSIX; only complete pair modifications can switch stacks
Pilot Harness
English | 中文
A CodePilot-inspired desktop client and plugin suite for DeepSeek Harness.
Run the DeepSeek Harness plugin runtime as a focused native app, manage providers and multimodal models visually, and keep desktop additions isolated as ordinary Harness plugins.
Quick start · Plugins · Architecture · MIT License
Why Pilot Harness
DeepSeek Harness has a powerful “everything is a plugin” architecture, but its default experience is designed around a CLI-launched Web UI. Pilot Harness keeps that runtime model and adds the parts expected from a daily desktop product:
- A real desktop app — Electron packages the local Harness runtime for macOS, Windows, and Linux, owns native window behavior, and provides a recovery screen when startup needs attention.
- A calmer CodePilot-inspired interface — consistent tokens, radii, menus, hover states, settings cards, Markdown, conversation/trajectory navigation, and platform-aware title bars.
- Provider and model management — connect supported providers, declare an OpenAI-compatible endpoint, manage credentials separately from settings, browse the live model catalog, and identify image-capable models.
- Workspace context without clutter — project-aware conversation rows show branch, state, reminder summary, mode, and model details, while Files opens as a true right sidebar.
- Plugin-first extensions — the theme, Worktree sidebar, Schedule summary, and Session-log export remain Cordis/DeepSeek Harness rows rather than desktop-only business logic.
- Reversible customization — disabling the CodePilot theme row removes its product mark and visual overrides so the stock Harness presentation can take over again.
Pilot Harness does not replace the DeepSeek Harness agent loop, Session log, tool pipeline, provider contracts, or RPC implementation. Electron owns packaging and native integration; the composed Harness plugin tree remains the application runtime.
Quick Start
Download the installer for your system from GitHub Releases:
| Platform | Download | Install and handle the security prompt |
|---|---|---|
| macOS (Apple Silicon) | DMG installer ZIP app | Open the DMG, drag pilot-harness.app into Applications, and launch it normally. A formal Release is published only after its Developer ID signature has been verified. Because notarization is not enabled yet, Gatekeeper may still block the first launch; in that case open System Settings → Privacy & Security, click Open Anyway, then confirm Open. Do not run xattr or disable Gatekeeper for a formal Release. If macOS reports that the signed app is damaged, delete it, verify the Release checksum, and download it again instead of bypassing the warning. Apple's security instructions. |
| Windows (x64) | EXE installer | Run the EXE. If Microsoft Defender SmartScreen says Windows protected your PC, first confirm that the file came from this Release, then choose More info → Run anyway. Do not disable SmartScreen globally. A managed computer may hide this option; contact its administrator instead. Microsoft's SmartScreen explanation. |
| Linux (x64) | AppImage DEB RPM | DEB: sudo apt install ./Pilot-Harness-Linux-amd64.debRPM: sudo dnf install ./Pilot-Harness-Linux-x86_64.rpmAppImage: chmod +x Pilot-Harness-Linux-x86_64.AppImage, then ./Pilot-Harness-Linux-x86_64.AppImage. If the file manager blocks execution, enable Allow executing file as program in file properties. The preview packages are unsigned, so only accept a package-manager warning after confirming the official Release source. |
The table links to formal end-user Releases, not the seven-day Actions preview artifacts. Formal macOS files must pass Developer ID verification before publication; while they remain unnotarized, the only expected extra step is Open Anyway in System Settings. Preview macOS artifacts are ad-hoc signed for CI verification and are not the normal installation path. Once notarization is enabled, the Open Anyway step should normally disappear and this guide must be updated with the release pipeline. Windows and Linux preview installers remain unsigned. Only override an operating-system warning for files downloaded from this repository's official GitHub Release; do not turn off platform security globally.
After installation, open Pilot Harness, select a Workspace, then go to Settings → Providers to connect a provider and choose one of its available models. No separate DeepSeek Harness installation is required for the desktop app. Source setup and packaging instructions live in Development, not in the user installation path.
What is included
| Area | What Pilot Harness adds | Ownership |
|---|---|---|
| Desktop shell | Native window, local runtime lifecycle, directory dialog, recovery, installers, and platform icons | Electron app |
| Visual system | CodePilot-inspired design tokens and component contracts | @deepseek-ai/dsh-client-ui-codepilot-theme |
| Workspace Files | Right sidebar, file count, branch summary, row actions, and @path insertion | @deepseek-ai/dsh-ui-worktree |
| Reminder summary | Active reminder count and nearest scheduled time in Session hover details | @deepseek-ai/dsh-ui-schedule-summary |
| Session export | Per-Session ZIP export from the Trajectory toolbar and /export | @deepseek-ai/dsh-session-log-export |
| Providers and models | Configurable adapter, credential/settings UI, live catalog, and multimodal labels | Existing Harness plugins plus the Pilot Harness desktop profile |
The provider/model experience is deliberately a profile composition, not a new provider implementation. It mounts existing adapter, Settings, and Credentials contracts, then replaces the desktop placeholder only after a real provider advertises a usable model.
Use the plugins independently
The desktop client already includes every plugin below. If you use a local DeepSeek Harness Web profile instead, install only the feature you want with one command; each release asset is a prebuilt dsh.bundle, so no repository clone, YAML patch, or local build is required.
CodePilot theme
dsh plugin --profile web add https://github.com/op7418/pilot-harness/releases/latest/download/deepseek-ai-dsh-client-ui-codepilot-theme-0.1.0-rc.5.tgz
Applies the Pilot Harness visual system and product mark. Removing the plugin restores the stock Harness presentation. See theme details.
Files sidebar
dsh plugin --profile web add https://github.com/op7418/pilot-harness/releases/latest/download/deepseek-ai-dsh-ui-worktree-0.1.0-rc.5.tgz
Adds the Workspace-confined right file sidebar, file count, branch summary, row actions, and @path insertion. See Files plugin details.
Reminder summary
dsh plugin --profile web add https://github.com/op7418/pilot-harness/releases/latest/download/deepseek-ai-dsh-ui-schedule-summary-0.1.0-rc.5.tgz
Adds active-reminder metadata to Session hover details while the upstream Schedule plugin remains the reminder authority. See reminder plugin details.
Session-log export
dsh plugin --profile web add https://github.com/op7418/pilot-harness/releases/latest/download/deepseek-ai-dsh-session-log-export-0.1.0-rc.7.tgz
Adds per-Session ZIP export to the Trajectory toolbar and the /export command. See export plugin details.
Restart the Web profile after installation and use dsh --profile web --dump-config to confirm the added row. Files and Reminder summary require the Pilot Harness UI slot contracts included in Pilot Harness v0.1.0; older upstream Harness builds can install their bundles but cannot render those two UI contributions.
Remove a plugin with the same package name shown in its details page, for example:
dsh plugin --profile web remove @deepseek-ai/dsh-ui-worktree
Development
git clone https://github.com/op7418/pilot-harness.git
cd pilot-harness
pnpm install
pnpm run desktop:dev
Run the desktop checks with:
pnpm run desktop:test
pnpm --filter @deepseek-ai/dsh-desktop run typecheck
pnpm --filter @deepseek-ai/dsh-desktop run test:e2e
Official installers are never built or uploaded from a developer machine. Every verified push to main, and a manual workflow dispatch without a release tag, produces seven-day Actions preview artifacts on native macOS, Windows, and Linux runners. A version-matched v* tag starts the formal path, verifies the platform artifacts and macOS Developer ID signature, generates SHA256SUMS.txt, and publishes the GitHub Release.
The Sync DeepSeek Harness upstream workflow checks the newest non-draft official release every day at 09:00 Asia/Shanghai. A clean update is merged without force-pushing, verified, committed to main, and dispatched to the same native release pipeline as v<upstream-version>-pilot.1. A merge conflict opens or refreshes a GitHub Issue and stops before changing main; missing macOS signing secrets also open an issue and leave the verified source synchronized without publishing an unsigned release. Rerunning the workflow after resolving either condition resumes the pending release.
For the underlying system, read the DeepSeek Harness architecture, development guide, and desktop architecture.
Upstream, attribution, and trademark notice
Pilot Harness is an independent community project derived from the MIT-licensed DeepSeek Harness and visually inspired by CodePilot. It is not an official DeepSeek product and is not endorsed by or affiliated with DeepSeek. “DeepSeek”, “DeepSeek Harness”, and “CodePilot” remain the property of their respective owners.
License
Pilot Harness is available under the MIT License. Third-party software and licenses are listed in THIRD_PARTY_NOTICES.md.
Read the usage guide →
Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.
Listing badge
[](https://deepseek-plugin.org/plugins/op7418/pilot-harness/packages/bundle/base)Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.