DeepSeek Harness v0.1.5-alpha.2
DeepSeek Harness v0.1.5-alpha.2: File Delivery & Agent Teams
- Author
- DeepSeekAgent.io Editorial Team
- Published
- Updated
DeepSeek published the dsh-v0.1.5-alpha.2 GitHub pre-release on September 9, 2026 and moved npm's alpha tag to 0.1.5-alpha.2. Models can explicitly deliver files in conversations, the right Sidebar previews Markdown, code, HTML, PDF, and images, and experimental Agent Teams packages become installable from npm.
As of September 10, npm latest and next remain on 0.1.2-rc.1. An ordinary unpinned install does not enter the 0.1.5 alpha line.
Release and installation status
| Check | Status |
|---|---|
| GitHub Release | v0.1.5-alpha.2, marked Pre-release |
| GitHub tag | dsh-v0.1.5-alpha.2 at b2e3b2a |
| Published | September 9, 2026 at 14:23 UTC |
npm alpha | 0.1.5-alpha.2 |
npm latest / next | 0.1.2-rc.1 |
Explicit test command:
npx @deepseek-ai/[email protected] web
Models can deliver files
A model can now mark files as conversation deliverables. Users can preview them in the right Sidebar, open them with the default application, or reveal them in the file manager.
The Sidebar supports Markdown, syntax-highlighted code, HTML, PDF, and images. Reports, web pages, code, and visual artifacts gain one inspection surface, giving complete workflows a clearer handoff stage for users outside software development.
The official release notes define the feature surface without claiming production validation for every file type. HTML, PDF, and external files still require appropriate local-content security boundaries.
Agent Teams packages reach npm
Experimental Agent Teams packages are publicly installable, although no bundled Profile enables them by default. A test environment with an initialized headless Profile can add the Team Profile explicitly:
dsh plugin --profile headless add @deepseek-ai/dsh-experimental-agent-team-profile
dsh --profile headless "Use Agent Teams to split this task between two teammates, wait, and summarize."
The Profile depends on @deepseek-ai/dsh-base. Teammates share one checkout, and the package supplies no automatic worktree isolation or file locking. Pin every experimental DSH package to the same version.
Plugin panels and Minimal changes
- Web plugins can register global panels through
sidebar.panellistandmain. - The former
conversationslot moves to theconversationkey undermain. - Web
minimaland Pythonsdk-minimalexpose only a persistent shell by default. str_replace_editorbecomes an explicit opt-in.
Plugin authors should update panel registration, default-tool assumptions, and regression coverage together.
Installation and reliability fixes
- npm installation no longer requires a local
fs-extbuild. - MCP discovery rejects repeated pagination cursors and retains the last valid tool set.
- Invalid pi-ai model configurations no longer hide the entire model-settings entry.
- Custom-provider Base URLs are validated and normalized before discovery.
- The Windows folder picker is less likely to open behind another window.
- Subagent guidance now matches the tools that each subagent can actually access.
Session V3 remains an upgrade boundary
Alpha.2 continues the Session V3 format introduced in alpha.1. Cross-version migration preserves original files, while downgraded builds cannot read an upgraded Session. Back up historical Sessions, custom log tooling, and plugin environments before testing.
Who should test it?
| Scenario | Recommendation |
|---|---|
| Regular user | Stay on 0.1.2-rc.1 |
| Needs artifact previews | Test alpha.2 in an isolated Workspace |
| Agent Teams user | Pin matching experimental packages and add the Profile explicitly |
| Web plugin author | Migrate Sidebar and main panel registration |
| Minimal Profile user | Verify that required file-editing tools remain available |
Related reading
- DeepSeek Harness v0.1.5-alpha.1: Sidebar, Session V3, and plugin API migration
- DeepSeek Harness Agent Teams guide
- DeepSeek Harness plugins versus Agent Presets
FAQ
Does npx @deepseek-ai/dsh web install alpha.2?
No. The unpinned command follows latest, which remains 0.1.2-rc.1 as of September 10.
Is Agent Teams enabled by default?
No. The packages are available from npm, and users still add the experimental Team Profile explicitly on top of an existing Base Profile.