tafcear/kimi-tide
Moonshot — A complete solution for Kimi Code (Moonshot) to access DeepSeek Harness: standard DSH plug-in + Kimi CLI bridge maintenance fork + Agent collaborative closed-loop methodology
kimi-tide (MoonTide) is a DeepSeek Harness plugin that automatically swaps in a better-suited model for you on every turn: everyday work goes to a cheap model, important work (code, review, math) goes to a stronger one, and image-bearing messages go to a model that can see images -- then the next text-only message returns to your default. It ships 'saving' and 'capability' presets, seven editable keyword groups, explicit directives (@kimi provider-level, @kimi/k3 exact-model), an image guard that reroutes text-only targets, a per-step 'MoonTide' dock panel showing who was picked and why, a plan/quota panel that follows the routed model, and an optional multi-model collaborative review that sends a turn's output to a configured reviewer (severity-graded issues + verdict).
Install
cd packages/dsh-kimi-tide && npm install && npm run build && npm pack && dsh plugin --profile web add ./dsh-kimi-tide-<version>.tgzThe plugin lives in the packages/dsh-kimi-tide workspace; build it and install the packed tarball as shown (replace <version> with the packed file name). Prerequisites per the README: Node.js >= 22 and DSH @deepseek-ai/dsh@0.1.2-rc.1 or newer (this release is verified on 0.1.5-rc.1); the models you route among must be connected in DSH's Settings -> Models page (any provider works). After installing, restart dsh web and pick a preset in Settings -> 月汐. No registry package is claimed (it is built from source).
Compatibility
Node.js >= 22; DeepSeek Harness @deepseek-ai/dsh 0.1.2-rc.1 or newer (verified on 0.1.5-rc.1). Router config lives in DSH settings, is restart-safe, and upgrades migrate automatically. Credentials are read through DSH's managed credential store (apiKeyEnv), never stored in plugin config.
Details
- Repo: tafcear/kimi-tide
- Category: uncategorized
- Stars: 3
- Version: v1.3.1 (2026-09-28) built from source (no npm registry package claimed); MIT
- Last push: 2026-08-17
- First seen: 2026-08-14
Recent updates
The README documents that OAuth access and the old machine-scoring engine were retired in favour of transparent, editable rules, the semantic hit-confirmation gate (preset.hitConfirm, fail-open), the multi-model collaborative review switches (trigger keywords/manual, 1-3 rounds; auto-revise is kept but not implemented yet), and three machine doc gates (npm run check: version consistency, no broken doc links, README bilingual pair parity). Current version v1.3.1 (2026-09-28).
FAQ
- How do I install kimi-tide?
- Per the README: from packages/dsh-kimi-tide run npm install && npm run build && npm pack, then dsh plugin --profile web add ./dsh-kimi-tide-<version>.tgz, and restart dsh web. Node.js >= 22 and DSH >= 0.1.2-rc.1 are required.
- Does it lock a whole session to a model?
- No -- the README stresses routing is decided per step, not per session: after an image is handled the next text-only message returns to your default model, so the pricey model is billed by the slice. (The default 'latch' image behaviour can be changed to lazy transcribe or blind in the preset.)
- Where is the router config stored?
- In DSH settings (edited via Settings -> 月汐) and it is restart-safe; upgrades migrate automatically and archive the old config.
Alternatives
r600a-code/dsh-swarm-router · ringoage/dsh-subagent-model-picker · yjh051108/dsh-routing-suite