dsh-kimi-subscription v1.4.0

dsh-kimi-subscription v1.4.0

• Add Kimi Code's new Kimi K3.1 Pro (k3.1-pro) and Kimi K3.1 Pro Highspeed (k3.1-pro-highspeed) to the Kimi subscription group, listed ahead of k3 as on Kimi's model page. No pi-ai release lists them yet, so the plugin adds them until the upstream catalog catches up.
• The entries follow Kimi's documentation: the exact IDs, a 1M context window, and Low, High, and Max thinking. These models only support thinking mode, and Kimi rejects a request that turns it off, so the model picker offers no Off level. With no level chosen, Kimi applies the default, Max. Kimi's documentation lists which plans include each model and the 1M context.
• Both READMEs end with a Support the author section holding the maintainer's WeChat and Alipay tip codes.
• Verified offline: 114 of 114 tests pass. The real host adapter lists both models with exactly the Low, High, and Max efforts, and the request pi-ai builds for k3.1-pro names that model and never disables thinking, on pi-ai 0.87.1 and on 1.1.0, the version inside DeepSeek Harness.app 0.2.1-rc.2. No live model calls.

Update from Settings → Kimi subscription → Update plugin, or install dsh-kimi-subscription@1.4.0 on the Plugins page, then fully quit and restart DSH. On 1.3.9 or earlier, use the Plugins page instead of the old update button. Kimi recommends starting a new session rather than switching an existing one to K3.1 Pro.

The attached tarball is the exact artifact published to npm with provenance.

dsh-kimi-subscription v1.3.10

dsh-kimi-subscription v1.3.10

• Fix the update button bypassing pnpm's release-age policy. It installed with --config.minimumReleaseAge=0, so pnpm never recorded a version younger than 24 hours as an exception, and the next plugin install in that profile failed with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION until the version was 24 hours old.
• The button now installs the exact version under the profile's own policy. By default pnpm installs it at once and records it in the profile's minimumReleaseAgeExclude. Under a stricter pnpm policy the settings card says when the update can run instead of reporting a failure.
• Update buttons in 1.3.9 and earlier still pass the override. Updating with one of them within 1.3.10's first 24 hours blocks every plugin install in that profile, including the next update, until 1.3.10 is 24 hours old; waiting is enough. Installing dsh-kimi-subscription@1.3.10 on the Plugins page instead lets pnpm record the exception and avoids the block.
• Verified with DSH's bundled pnpm 11.28.5 in scratch profiles: the default policy installs a young exact version and records the exception, while minimumReleaseAge: 1440 and minimumReleaseAgeStrict: true hold it back and the update reports when it clears. 109 of 109 offline tests pass. No live model calls.

Update from Settings → Kimi subscription → Update plugin, or install dsh-kimi-subscription@1.3.10 on the Plugins page, then fully quit and restart DSH.

The attached tarball is the exact artifact published to npm with provenance.

dsh-kimi-subscription v1.3.9

dsh-kimi-subscription v1.3.9

• Fix DeepSeek Harness 0.2.1-rc.1 failing to start with this plugin installed: the app stopped with connection (required) webRuntime among the plugins waiting for services. DSH 0.2.1 renamed the service its official connection row reads trustedHosts from, webRuntime, to webStartup, and the bundle patch shipped since 1.2.4 replaced that row's whole inject list with the old name.
• The bundle no longer patches any official row. The Kimi account channel binds the running web server itself, opens once the server is up, and reopens after a restart. Connection's authentication is unchanged, and unauthenticated requests are still rejected.
• Accept @deepseek-ai/cordis 4.0.5 and @earendil-works/pi-ai 1.1.0, the versions DSH 0.2.1-rc.1 ships. On DSH 0.2.1 the model list shows Kimi models only while the subscription is connected; the host now asks for a credential before listing a provider's models.
• Verified offline against the 0.2.0-rc.1 development baseline and against the host packages inside DeepSeek Harness.app 0.2.1-rc.1 (106 of 106 tests each), plus --dump-config on the app's bundled CLI. No live model calls.

If DSH already fails to start, the in-app update button is out of reach. Quit DSH, run pnpm add --save-exact dsh-kimi-subscription@1.3.9 in ~/.dsh/profiles/desktop (pnpm ≥ 11), then start DSH again. Otherwise update from Settings → Kimi subscription → Update plugin (or install dsh-kimi-subscription@1.3.9 on the Plugins page), then fully quit and restart DSH.

The attached tarball is the exact artifact published to npm with provenance.

dsh-kimi-subscription v1.3.8

dsh-kimi-subscription v1.3.8

• Show a readable plugin name on the Plugins page: Kimi Subscription in English and Kimi 订阅 in Chinese, with a matching localized description. The package now ships locale/en.json and locale/zh-CN.json and exports ./locale/*.json, which DSH reads for plugin card metadata. Previously the card showed the raw package name.
• Add a release regression check for the locale export, packaged files, and localized titles and descriptions.
• No authentication, model-routing, search, quota, icon, or dependency changes.

Update from Settings → Kimi subscription → Update plugin (or install dsh-kimi-subscription@1.3.8 on the Plugins page), then fully quit and restart DSH.

The attached tarball is the exact artifact published to npm with provenance.

dsh-kimi-subscription v1.3.7

dsh-kimi-subscription v1.3.7

• Show the existing Kimi mascot on the installed plugin card. The package now declares a top-level icon and ships a dedicated 512×512 transparent, lossless WebP (208,698 bytes), below DSH's 256 KiB icon limit. The original README PNG is retained unchanged.
• Add a release regression check for the icon declaration, exported manifest, packaged asset, WebP signature, and host byte limit.
• No authentication, model-routing, search, quota, or dependency changes.

Update from Settings → Kimi subscription → Update plugin (or install dsh-kimi-subscription@1.3.7 on the Plugins page), then fully quit and restart DSH.

The attached tarball is the exact artifact published to npm with provenance.

dsh-kimi-subscription v1.3.6

• Fix dsh web still failing with cannot get property "webServer" without inject after 1.3.5. The account channel is registered through Connection, which reads webServer on its own fiber. The official row only injects webRuntime, and the bundle patch is skipped when it runs before that row exists. This release attaches the already-running web server onto that fiber before opening the channel. Unauthenticated requests are still rejected.

Install the exact version. pnpm 11 skips releases newer than 24 hours unless the age gate is disabled:

cd ~/.dsh/profiles/web
pnpm add --save-exact --config.minimumReleaseAge=0 dsh-kimi-subscription@1.3.6

Then quit dsh web completely and start it again. Refreshing the page does not reload the Host plugin.

npm: https://www.npmjs.com/package/dsh-kimi-subscription/v/1.3.6

dsh-kimi-subscription v1.3.5

• Fix dsh web failing to activate with cannot get property "webServer" without inject. DSH 0.2.0-rc.2 web and the desktop app share one connection row, and that row injects only webRuntime. The plugin now replaces it with credentials, webRuntime, and webServer, which is what Connection's apply, trusted-host expression, and RPC registration actually use. Deleting the patch would break both surfaces.
• Scratch dsh web on the 0.2.0-rc.2 CLI starts with no activation warning. No live model calls and no credential reads.

Install: dsh-kimi-subscription@1.3.5

npm: https://www.npmjs.com/package/dsh-kimi-subscription/v/1.3.5

dsh-kimi-subscription v1.3.4

Publish from GitHub Actions with npm trusted publishing. The registry stores a provenance attestation, which npm shows as the green check beside the version.

No source, peer-range, compatibility, authentication, search, or quota behavior changes.

dsh-kimi-subscription v1.3.3

dsh-kimi-subscription v1.3.3

• Document the desktop application as the only supported installation target, and drop the web-profile instructions from both READMEs and both guides. The plugin itself is unchanged and still loads on any conforming DSH profile; what changes is what this project tells users to do.
• Install instructions now describe the desktop application's own Plugins page: Add plugin, enter dsh-kimi-subscription as the package name, pick the official source, then Install. The same field accepts a GitHub repository address, an absolute local plugin directory, and a version-qualified name such as dsh-kimi-subscription@1.3.3. This replaces the previous dsh plugin --profile web add … commands.
• Update and uninstall instructions now lead with Settings → Kimi subscription → Update plugin and the Plugins page's Uninstall, which is what the desktop application actually exposes. The manual pnpm add --save-exact … recovery step for older versions is kept, because dsh plugin --profile desktop … is still refused by the CLI with profile "desktop" is managed exclusively by the Electron application.
• dsh plugin --profile <name> … is documented as a non-desktop-profile path only, so it is not lost for anyone running a scratch profile.
• No source, peer-range, compatibility, authentication, search, or quota behavior changes. No live model calls and no credential reads.

---

Install (desktop application)

Open Plugins → Add plugin, enter dsh-kimi-subscription, choose the official source, then click Install. Restart the app afterwards.

Artifact: dsh-kimi-subscription-1.3.3.tgz — sha256 657440ffb12b0d9a7d6d36e7d5537a6e4071769e73bce475d3d68a422f5d6042

dsh-kimi-subscription v1.3.2

dsh-kimi-subscription v1.3.2

• Fix the plugin being disabled outright after the desktop app updated to DeepSeek Harness 0.2.0-rc.1. Every @deepseek-ai/dsh-* peer still stopped at <0.2.0-0, so the host's compatibility preflight refused the whole bundle and printed skipping profile bundle "dsh-kimi-subscription": Error: Plugin dsh-kimi-subscription@1.3.1 is incompatible with dsh 0.2.0-rc.1: peerDependencies {...}. The row never mounted, so the Kimi models and the settings page both disappeared. The condition was reproduced against a scratch profile on the real desktop runtime before and after the change.
• Widen the declared host peer range to >=0.1.1-rc.2 <0.3.0-0, spanning the whole 0.2 line instead of stopping at 0.1. 0.3.0 is still refused, so this stays a claim about a tested line rather than an unbounded promise about any future host. 1.2.14 made the same call for the 0.1 line after an enumerated list broke on a host bump; the 0.1-only upper bound then broke on the next minor line.
• The development baseline, the recorded compatibility data, and the entire offline test suite now target the published 0.2.0-rc.1 host packages, the versions the current desktop app actually carries.
• Accept @earendil-works/pi-ai 0.86.0, 0.86.1, 0.87.0, and 0.87.1 in the peer range, and build and test against 0.87.1. DSH 0.2.0-rc.1 itself depends on ^0.85.1, so a profile install can resolve any of these and the plugin imports this package directly. kimiCodingProvider, the ./providers/* entry point, and the root createModels export are unchanged across 0.85.1 → 0.87.1.
• tests/package-contract.test.mjs now requires every declared host peer range to equal compatibility.json's acceptedRuntimeRange, and requires the latest recorded version to be listed as supported and to satisfy that range, so the metadata the gate reads cannot drift from the manifest again.
• No model-routing, authentication, search, quota, or client-UI behavior changes; no source-file changes. No live model calls and no credential reads.

---

Install

dsh plugin --profile web add dsh-kimi-subscription@1.3.2

Artifact: dsh-kimi-subscription-1.3.2.tgz — sha256 5a47210ed6e7faadce269fd1fa2648f69dbcf9c3b419d689c126e22efe373314