v1.4.1

Patch release focused on Kimi CLI --print compatibility for users on the newer kimi-code 0.14.x (which removed the --print flag).

This is the first release under the post-v1.4.0 SOP correction: every commit since v1.4.0 (here #1461) went through a fresh manual QA cycle by cc-connect/qa-cursor before stable promotion, including owner-paired binary smoke against both old and new Kimi CLI versions.

🔧 Fixed

• Kimi CLI --print compatibility (#1461 fixing #1456, @chenhg5, reported by @WeiFengJL)
  • Newer kimi-code 0.14.x removed the --print flag, causing error: unknown option '--print' (Did you mean --prompt?) on agent startup.
  • cc-connect now probes Kimi CLI --help at startup and conditionally passes --print only when the installed binary supports it.
  • Both legacy kimi-cli 1.48.x users and new kimi-code 0.14.x users upgrade to v1.4.1 with zero config changes.
  • Verified against real binaries: kimi-code 0.14.2 (Print=false, unblocked) and kimi-cli 1.48.0 (Print=true, no regression).

Upgrade notes

• No config changes required. Drop in v1.4.1 and Kimi CLI works on both old and new versions.
• All v1.4.0 upgrade notes still apply (cli_path deprecation, Feishu imageBatchWindow / MessageRecallDetector defaults).

Install

# npm
npm install -g cc-connect

# Binary: download from assets below

Full changelog: changelogs/v1.4.1.md
Diff from v1.4.0: v1.4.0...v1.4.1