DeepSeek Harness v0.1.2-alpha.5

DeepSeek Harness v0.1.2-alpha.5: npm Release Status

Author: DeepSeekAgent.io Editorial Team
Published: Sep 2, 2026
Updated: Sep 5, 2026

DeepSeek officially released dsh-v0.1.2-alpha.5 on September 2, 2026. Its GitHub tag, release notes, and npm package are now all available, and npm's alpha dist-tag still points to this version.

Alpha.5 is a narrowly scoped fix. The official notes list one issue: upgrading from 0.1.1-rc.2 or 0.1.2-alpha.3 could prevent the application from starting or make conversation titles disappear from the list. The later 0.1.2-rc.1 is now npm's default, so new installations should not treat alpha.5 as the current recommended entry point.

The short version

Alpha.5 is directly relevant when diagnosing startup failures or missing conversation titles after an rc.2 or alpha.3 upgrade. Regular users should evaluate the newer 0.1.2-rc.1 default instead of choosing alpha.5 only because the moving alpha tag still points to it.

Release status

Check	Status
GitHub Release	`v0.1.2-alpha.5`, marked Pre-release
GitHub tag	`dsh-v0.1.2-alpha.5` at `db6bdc3`
GitHub publication	September 2, 2026 at 10:02 UTC
Exact npm version	`@deepseek-ai/[email protected]` is published
npm `alpha`	Points to `0.1.2-alpha.5`
npm `latest` / `next`	Now point to the later `0.1.2-rc.1`

Pin this exact build when reproducing it:

npx @deepseek-ai/[email protected] web

What the official fix covers

The release notes name two upgrade sources:

0.1.1-rc.2
0.1.2-alpha.3

When upgrading from those builds, old data or migration behavior could stop the application from starting or leave conversations present while their titles disappeared from the list. Alpha.5 fixes this upgrade path; it is not a feature release.

If the issue has already occurred, do not assume that a missing title means the underlying conversation was deleted. Preserve the original Sessions and configuration, then test a pinned version against a copy.

What alpha.5 does not claim

The official notes do not announce new Agent, plugin, model, or Web features, and they do not provide a broad compatibility guarantee. Alpha.5 still sits on top of earlier 0.1.2 migration changes, including removal of the SQLite Session backend, Session API work, and PTC tool-composition changes.

Which version should you choose now?

Scenario	Recommendation
Regular new install	Use npm's default `0.1.2-rc.1`
Reproduce alpha.5 behavior	Pin `0.1.2-alpha.5`
Upgrade from rc.2 or alpha.3 failed	Back up first, then validate against the alpha.5 fix
Plugin compatibility testing	Test rc.1 and every older version you actually support
Study the 0.1.3 architecture	Read the alpha.1 source notes; do not treat it as an npm package

Upgrade diagnosis checklist

Copy important Sessions and configuration instead of repeatedly testing against the originals.
Record whether the source version was rc.2, alpha.3, or another build.
Pin alpha.5 or rc.1 so a moving dist-tag cannot change the reproduction.
Check application startup, conversation count, titles, and the underlying message content separately.
After validation, decide whether the daily environment should move to rc.1 or remain on the known older build.

Frequently asked questions

Does alpha.5 have an official GitHub Release?

Yes. The official tag and release notes are available, and the documented scope is one upgrade-startup and conversation-title fix.

Is alpha.5 still npm's default version?

No. It remains the target of the alpha dist-tag, but npm's latest and next now point to the later 0.1.2-rc.1.

Does a missing conversation title mean the Session was deleted?

Not necessarily. The official issue describes titles disappearing from the list. Back up the data and inspect list metadata separately from the underlying Session content.