Provides a workspace file tree panel for DeepSeek Harness Web, with one-click toggle in the conversation page header. Supports creating and renaming files/directories, and adding paths to the conversation draft.
ⓘ This plugin is a sub-package of the op7418/pilot-harness monorepo — stars and activity count the whole repository.
- Language
- TypeScript
- License
- MIT
- Branch
- main
Install
$ dsh plugin --profile web add github:op7418/pilot-harness#path:packages/workspace/ui-worktreeRun 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/workspace/ui-worktree 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 Description
pilot-harness (package name @deepseek-ai/dsh-ui-worktree, Cordis plugin ID pilot-worktree) is the workspace file tree panel for DeepSeek Harness Web edition. A "Files" toggle button appears in the conversation page header; when clicked, a real-layout file directory tree appears on the right side, facilitating browsing the current project, creating/renaming files/directories, and quickly adding file paths to the conversation draft in the @path format.
Core Features
- Adds a "Files" toggle button in the session header, opens the right-side file tree sidebar and automatically narrows the conversation area width
- Lists the current Workspace's directory tree with nested expansion and directory/file sorting
- Displays the count of visible files in the Workspace root directory (automatically skips
.git,.DS_Store,node_modules, symbolic links) - Each file/folder row provides a three-dot menu: open with local app, append
@pathto current session draft, rename - Toolbar supports creating new files, new directories, and full refresh
- Reads
.git/HEADdirectly viasummary=branchpath to display the current Git branch in the workspace sidebar summary (detached HEAD shows short commit prefix, non-Git projects don't show this line)
Technical Implementation
- Language: TypeScript + React (TSX components)
- Key Dependencies:
@deepseek-ai/cordis,@deepseek-ai/dsh-client-runtime,@deepseek-ai/dsh-client-connection,@deepseek-ai/dsh-workspace - Architecture Pattern: Dual-plugin —
src/index.tsregisters Host-side/pilot-worktreeRPC (loopback authorization),src/client/index.tsregisters browser-side React component and injects into host via cordis patch - Entry Files:
src/index.ts(Host RPC registration) /src/client/index.ts(browser component registration) /cordis.patch.yml(cordis assembly patch)
Use Cases
People who want to directly browse workspace files, reference multiple paths, or quickly create/organize project directories while chatting with AI. For example, when developers discuss code with AI and want to reference specific paths like src/auth/login.ts, or when they need to create files/directories without leaving the conversation page and immediately let AI see them.
Prerequisites & Compatibility
| Dependency | Minimum Version | Description |
|---|---|---|
| DSH (Host) | Undeclared (requires Pilot Harness v0.1.0+) | Host must expose three rendering slots: conversation.session.header.utilities, shell.right-sidebar, sidebar.workspaces.session.detail |
| Node.js | ^22.19.0 || >=24.0.0 | From root package.json engines.node |
| Platform | Cross-platform | Source code header only references built-in modules like node:fs/promises, no os/cpu restrictions declared |
| Native Modules | None | Only uses Node built-in fs/promises, path, no native dependencies like node-pty |
Installation
dsh plugin --profile web add github:op7418/pilot-harness/packages/workspace/ui-worktree
Configuration
This plugin requires no additional configuration. All interaction parameters (workspace ID, relative path, operation type) are dynamically passed through RPC requests. The source code exposes no Config fields that users can adjust in cordis.yml.
FAQ
Q: Does this plugin depend on Electron or desktop client?
A: No, it doesn't. It's a regular Web profile plugin. Browser-side and Host-side communicate via loopback-authorized Connection RPC, no Electron dependency. Native "open file" calls go through the host runtime's loopback-protected openPath route, not bypassing browser security boundaries.
Q: Can't see Files button or right sidebar after installation?
A: Upstream Harness version must support the three rendering slot contracts — conversation.session.header.utilities, shell.right-sidebar, sidebar.workspaces.session.detail. Pilot Harness v0.1.0 already includes these contracts; older Harness versions can load the plugin but cannot render the UI.
Q: Can I delete files?
A: No. Deletion is an irreversible operation. The plugin intentionally exposes only three directory operations: new file, new directory, rename. To delete files, please use system file manager or command line tools.
Q: Some files not visible in the panel?
A: The plugin actively skips .git, .DS_Store, node_modules, symbolic links, and unconventional file types (like sockets, block devices). Single directory enumeration cap is 5,000 items, Workspace root recursive count cap is 20,000 visible files — exceeding shows "truncated" instead of unlimited reading.
Q: Can I access files remotely?
A: No. RPC channel uses strict loopback authorization, no trusted-host exception. Even adding LAN origin to Harness's trustedHosts setting won't grant remote filesystem access — remote Web scenarios require a separate authentication transport layer not provided by this plugin.
Q: How to confirm successful installation?
A: After installation, restart Web profile, then run dsh --profile web --dump-config, confirm pilot-worktree entry appears in output.
Q: How to uninstall?
A: Run dsh plugin --profile web remove @deepseek-ai/dsh-ui-worktree. After restarting Web profile, the Files control in header and right sidebar will disappear together.
Q: When adding file to conversation draft, will AI really "see" this path?
A: Only appends @path text to user draft. Whether to send is determined by conversation package; plugin doesn't inject hidden model context, doesn't add tool schemas, and doesn't write Session events.
Difficulty Level
Beginner — after one installation command with no configuration, Files button appears in session header; ordinary users can directly use browsing, create, rename, and path reference.
Known Issues & Limitations
- Workspace root recursion statistics stop after 20,000 visible files, marked as truncated count
- Single directory enumeration stops after 5,000 items and marks as truncated, avoiding buffering entire super-large directory at once
- Intentionally no delete operation (irreversible); currently supported directory changes only include new file, new directory, rename
- Name validation rejects Windows reserved device names (CON/PRN/AUX/NUL/COM1-9/LPT1-9 etc.), alternate data stream syntax, names ending with dot; rename won't overwrite existing entries, target conflict reports error
- Native title bar dragging and native directory selection box are desktop shell capabilities, pure browser combination cannot obtain
- File RPC strictly loopback authorized, no trusted-host exception; LAN remote access not supported
- Doesn't expose Git subdirectory details, dependency directories, platform metadata, and symbolic links
- Older upstream Harness (missing three rendering slot contracts) can load bundle but cannot display Files control or right sidebar
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/workspace/ui-worktree)Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.