Repository navigation
Koder CLI 0.4.0-preview.17
Pre-release
Koder CLI 0.4.0-preview.17 prepares updates in the background and keeps current tasks, queued requests and unfinished drafts ahead of a restart. It verifies the replacement before handing the conversation to the new process. Closing chat cancels unfinished preparation. A changed license requires manual review. Use koder update auto off to disable automatic updates or koder update auto status to check the setting.
This release also fixes Windows MCP readiness-file replacement and failed-host cleanup, improves MiniMax official endpoint routing and error messages, and updates the installation guide, privacy texts and eight complete bilingual terminal manuals. Users on preview.16 should run koder update once to install the new updater.
MiMo Token Plan, Kimi API, Kimi Code, DeepSeek, Alibaba Token Plan, Volcano Coding Plan and Volcano Ark API remain temporarily unavailable and gray in setup. Dedicated provider test keys were unavailable. Synthetic protocol checks do not establish live account compatibility.
Use the installation guide or the official CLI page. Package hashes, component notices and acceptance results are attached. Existing third-party and legacy source licenses remain unchanged; see source status.
Known Windows timing limits remain: fresh-process startup sometimes exceeds the original one-second target, and one full celebration check exceeded its end-to-end limit (10.125 seconds). Earlier failures are retained; functional installation checks do not erase these performance limits.
A Windows WeChat gateway hot-update handoff also exceeded its original eight-second readiness deadline once; three subsequent unchanged replays passed. This intermittent limit remains open. If a gateway does not reconnect after updating, finish current work and restart Koder manually. Do not repeat already completed tasks.
Validation: full no-key CLI suites passed on Linux and macOS Intel. Windows host lifecycle, automatic-update controls and native installation/preservation checks passed. The full Windows suite and later functional follow-up retained the startup, animation and gateway timing failures described above. This preview is not represented as full zero-failure acceptance. Exact counts and skips are attached.