# v1.4.1 — 2026-06-28

Patch release focused on Kimi CLI compatibility. One commit on top of v1.4.0.

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

## Fixed

- **Kimi CLI `--print` compatibility** (#1461 fixing #1456,
  [@chenhg5](https://github.com/chenhg5), reported by
  [@WeiFengJL](https://github.com/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 the Kimi CLI `--help` output at startup
  and conditionally passes `--print` only when the installed binary
  supports it. No config change required either way.

  Verified against:
  - `kimi-code` 0.14.2 (probe → `Print=false` → `--print` skipped → unblocked)
  - `kimi-cli` 1.48.0 legacy (probe → `Print=true` → `--print` still passed → no regression)

  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.

## Why v1.4.1 (and not v1.5.0 / v2.0.0)

PATCH bump per release-cadence-policy §3:
- Zero new platforms, zero new agents, zero new public APIs.
- Zero breaking changes for any user (both legacy and new Kimi CLI keep working).
- One bug fix for a real reported breakage (#1456).

## QA evidence

The full v1.4.1 manual QA cycle included:

- **#1461 new path (kimi-code 0.14.2)**: real binary probe → `Print=false`
  → cc-connect skipped `--print` → no startup error.
- **#1461 legacy path (kimi-cli 1.48.0)**: real binary probe via venv pip
  install → `Print=true` → cc-connect still passed `--print` → no
  regression.
- **Retroactive coverage of v1.4.0 critical fixes** that owner had pulled
  forward to ship (#1436 Send goroutine race, #1321 Feishu recall
  throttle, drainPendingMessages followup) was also revalidated in this
  cycle to close the v1.4.0 manual-QA gap.
- Owner-paired feishu smoke (long-turn, session-busy queue-depth race
  window kill) — 25 min+ release-test process stable, 0 panics.

Full QA receipt:
[`projects/cc-connect/agents/qa-cursor/release-gate/notes/2026-06-28-v1.4.1-test-plan.md`](../../projects/cc-connect/agents/qa-cursor/release-gate/notes/2026-06-28-v1.4.1-test-plan.md)
(in the agency workspace).

## 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).

## Contributors

- [@chenhg5](https://github.com/chenhg5) — fix (#1461)
- [@WeiFengJL](https://github.com/WeiFengJL) — reported #1456 with a
  clean repro
- cc-connect/qa-cursor — manual QA cycle (owner-paired) covering #1461
  + retroactive coverage of v1.4.0 critical fixes

## Reference

- Previous stable: [v1.4.0](https://github.com/chenhg5/cc-connect/releases/tag/v1.4.0) (2026-06-28)
- Full diff: [v1.4.0...v1.4.1](https://github.com/chenhg5/cc-connect/compare/v1.4.0...v1.4.1)
