Provides an `/export` slash command and session header button for DSH web, downloading the current Session as a ZIP file containing sub-sessions and attachments.
ⓘ 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/session-query/session-log-exportRun 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/session-query/session-log-export 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-Sentence Positioning
Provides one-click Session log download for DSH Web: adds an "Export Logs" button in the session header and recognizes the /export slash command in conversations, triggering the browser to download a ZIP file containing the current Session, sub-sessions, and attachments.
Core Capabilities
- Register the
/exportslash command and route the user's download intent to the browser-side download controller - Render a 111×32 "Export Logs" button in the session header toolbar, sharing the same download flow with the slash command
- Automatically perform HEAD pre-check to confirm Host-side
/api/session.exportavailability before handing over to browser download manager, avoiding mid-download interruptions - Display three states via unified popup: "Preparing / Download Started / Failed"
- Only one download per Session allowed at a time; repeated clicks reuse the same in-progress download operation
- Plugin disposal cancels all pending pre-check requests
Technical Implementation
- Language: TypeScript (with React 18 browser-side components)
- Key Dependencies:
@deepseek-ai/dsh-commands(register/exportslash command),@deepseek-ai/dsh-client-ui-trajectory(toolbar slot),@deepseek-ai/dsh-client-runtime(session snapshot storage),@deepseek-ai/dsh-client-ui-primitives(buttons, icons, dialogs) - Architecture Pattern: Dual-sided plugin—Host side registers
/exportcommand and triggerscommand/executedevent; Browser side subscribes to this event and drives the download controller; actual ZIP generation is owned by the host-sidedsh-host-apiproxy - Entry Files:
src/index.ts(Host side command registration),src/client/index.ts(Browser side download controller and slot injection)
Use Cases
Suitable for users who need to share a complete AI assistant conversation (including sub-tasks, attachments, command history) with colleagues, archive it for records, or upload it to a ticket system. Click Export to get a fully extractable ZIP without manually copying conversation content.
Prerequisites and Compatibility
| Dependency | Minimum Version | Description |
|---|---|---|
| DSH | 0.1.0-rc.7 | Web bundle only; requires dsh-host-apiproxy (provides ZIP endpoint), dsh-commands, dsh-client-ui-commands, dsh-client-ui-trajectory to be installed simultaneously |
| Node.js | >=22.19.0 | Follows the host root package package.json engines.node version requirement |
| Platform | Cross-platform | Runs on browser side, no native modules, relies on host's persistent backend |
Installation
dsh plugin --profile web add github:op7418/pilot-harness/packages/session-query/session-log-export
Configuration
No additional configuration required. After installing to Web profile and restarting, the "Export Logs" button will appear in the session header, and the /export command will be recognized in conversations.
FAQ
Q: How do I download a Session's logs?
A: Click the "Export Logs" button on the right side of the session header in the browser interface, or type /export in the conversation and send it—both will trigger a ZIP file download.
Q: What's included in the ZIP package?
A: Contains the current Session, all sub-sessions, and attachments. ZIP generation, streaming reads, and error handling are completed by the backend's dsh-host-apiproxy; this plugin only initiates the download.
Q: Can I download the same Session multiple times simultaneously?
A: No. Each Session allows only one download at a time. Repeated button clicks or repeated /export commands will reuse the same in-progress download operation and won't start a new download.
Q: Does it support SQLite backend Session export?
A: Currently not supported. The download endpoint requires the persistent backend to provide raw artifacts by Session; the accompanying JSONL backend supports plaintext and zstd artifacts; SQLite export is out of scope for this release.
Q: What happens if the download fails?
A: Failures discovered before download starts (during HEAD pre-check) are reported via the plugin's popup with error messages; failures that occur after the browser has received the download request are handled by the browser's own download manager and won't trigger the plugin's popup.
Q: Does closing the popup cancel an in-progress download?
A: No. Closing the popup only closes the UI and won't cancel the browser's in-progress download; the popup won't reappear after the operation completes.
Q: How do I uninstall it?
A: Run dsh plugin --profile web remove @deepseek-ai/dsh-session-log-export, then restart the Web profile.
Difficulty Level
Beginner — Plug-and-play with no additional configuration required; adds one button + one slash command to the interface, with all interaction logic handled on the browser side.
Known Issues and Limitations
- Only Web bundle available; does not affect CLI, ACP, or other profiles.
- Depends on persistent backend providing raw artifacts by Session; SQLite backend export not currently implemented.
- Download target is local browser; target path is determined by the browser, unable to specify Host-side path or invoke native folder picker.
- HEAD pre-check only reports errors before ZIP streaming starts; after browser receives download, sub-session or attachment read failures are提示 by the browser's download manager and won't be displayed via the plugin's popup.
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/session-query/session-log-export)Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.