Displays the count of currently active reminders and the most recent trigger time on the Workspace Session floating card, without modifying the Schedule itself.
ⓘ 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/schedule/ui-schedule-summaryRun 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/schedule/ui-schedule-summary 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
Displays an additional line of activity reminder summary on the Workspace Session hover card, allowing users to see how many untriggered reminders remain and when the last one triggered without opening the Session. The plugin is read-only and won't modify Schedule reminder data.
Core Features
- Adds a line "Reminder: N · Time" to the Workspace Session hover card
- Reads activity reminder count and last trigger time from Session persistence log through a read-only channel
- Automatically avoids Fork inheritance: only counts reminders for the current Session, not displaying those left by parent Sessions
- Won't wake up cold Sessions; read operations won't bring background Sessions back to running state
- 15-second result caching + concurrent request deduplication for the same Session, avoiding repeated full log scans
- Evicts entries in LRU order when exceeding 256 Sessions, automatically cleaning up expired entries
Technical Implementation
- Language: TypeScript + React (Host & Client dual-sided)
- Key Dependencies:
@deepseek-ai/dsh-schedule(folding schedule/change event streams),@deepseek-ai/dsh-session-persistence(inspecting persistence logs),@deepseek-ai/dsh-client-connection(loopback RPC channel),@deepseek-ai/dsh-client-ui-workspace(sidebar slot) - Architecture Pattern: Dual-sided Cordis plugin — Host side registers a
/pilot-schedule-summaryRPC endpoint callable only via loopback; Client side registers an ordered entry in the Workspace sidebar slotsidebar.workspaces.session.detail - Entry Files:
packages/schedule/ui-schedule-summary/src/index.ts(Host),packages/schedule/ui-schedule-summary/src/client/index.ts(Client)
Use Cases
If you frequently browse many Sessions via hover cards in Pilot Harness Web or Workspace, and need to quickly determine whether a Session still has scheduled reminders and when the next one will trigger—without opening Session details—this plugin displays the information directly on the hover card. It doesn't manage reminders for you or affect other plugins' control over Schedule; it's purely a status visibility aid.
Prerequisites & Compatibility
| Dependency | Minimum Version | Description |
|---|---|---|
| DSH | 0.1.0-rc.7 | Workspace dependency; host must expose sidebar.workspaces.session.detail slot contract (provided by Pilot Harness v0.1.0+) |
| Node | >=22.19.0 | Must match engines.node field in root package.json |
| Platform | Cross-platform | Runs on macOS / Windows / Linux; browser side is Web platform |
| Native Modules | None | No dependencies on native extensions like node-pty, node:sqlite |
Installation
dsh plugin --profile web add github:op7418/pilot-harness/packages/schedule/ui-schedule-summary
Configuration
No additional configuration required. After installation, restart the Web profile to take effect; use dsh --profile web --dump-config to verify pilot-schedule-summary has been loaded.
FAQ
Q: Where can I see the effect after installing?
A: In Pilot Harness Web desktop or Workspace sidebar, hover over a Session card (with delayed pop-up). If there are untriggered reminders, the hover card will show an additional line "Reminder: N · Time"; zero reminders or read failures won't display.
Q: Will uninstalling this plugin lose my reminders?
A: No. Reminder persistence and lifecycle are held by @deepseek-ai/dsh-schedule; this plugin only provides read-only presentation. After uninstallation, the sidebar just won't show the reminder line anymore.
Q: Why is the installation command in README different from the plugin ID?
A: README provides the packaged tgz pre-built bundle address; the plugin ID requires source installation. Both sources must match—choose either one when using.
Q: Can remote Web clients use this?
A: Not currently. The RPC channel only allows loopback access; adding LAN origin to Harness's trustedHosts won't enable it either. Remote scenarios require a separate authentication transport not provided by this plugin.
Q: What if I don't see the reminder line after installation?
A: First confirm the Web profile has been restarted and dsh --profile web --dump-config shows pilot-schedule-summary; if the host doesn't expose the sidebar.workspaces.session.detail slot contract (e.g., older upstream Harness versions), the plugin can load but won't render the line.
Q: How often does the cache refresh?
A: Host caches each Session's summary for 15 seconds; corresponding schedule/change events immediately invalidate the cache; entries are evicted in LRU order when exceeding 256 Sessions.
Q: How to uninstall?
A: Execute dsh plugin --profile web remove @deepseek-ai/dsh-ui-schedule-summary, then restart the Web profile.
Difficulty Level
Beginner — single-function plugin, install and use, no configuration required, no need to understand internal concepts like Schedule / Fold / Seed.
Known Issues & Limitations
- Hover summary only displays active count and last trigger time, not reminder content, prompts, or management operation entries
- When persistence log is corrupted or unavailable, the hover card won't show that line, nor will Schedule diagnostics be displayed
- RPC channel only allows loopback calls; intentionally no trusted-host exception; remote Web clients need a separate authentication transport
- If host doesn't expose
sidebar.workspaces.session.detailslot contract, plugin can load but the line won't render on browser side - When installing older upstream Harness versions, some dependencies (like slot positions of
@deepseek-ai/dsh-client-ui-workspace) may not be available, causing Client side injection to fail
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/schedule/ui-schedule-summary)Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.