cc-connect-next v0.1.4

cc-connect-next v0.1.4

中文

这是修复默认配置链路的稳定补丁版。v0.1.3 已把忙时消息策略默认改为
steer，但直接安装生成的配置仍使用不具备原生 steer 能力的 Agent/后端，
导致默认策略在首次安装后只能回退到排队。v0.1.4 让策略默认与后端默认真正
对齐。

变化

• 直接安装默认即可使用 native steer。 首次运行生成的配置现在显式写入
  [queue] busy_message_mode = "steer"，默认 Agent 改为 Codex，并使用
  backend = "app_server" + app_server_url = "stdio" 启动本地 Codex
  app-server。替换配置中的 REPLACE 占位值后，无需再补隐藏配置即可使用
  turn/steer。
• 已有最简 Codex 配置自动修复。 对 Codex 而言，省略 backend 现在等同于
  app_server，省略 app_server_url 现在等同于 stdio。因此升级后，不需要
  重写配置也能获得与新安装相同的 steer 能力。
• 显式 exec 仍受支持。 已明确配置 backend = "exec" 的用户保持每回合
  codex exec --json 子进程行为；该后端不能向进行中的回合追加输入，忙时
  消息会安全回退到 FIFO 队列。若你依赖旧行为，请显式保留此配置。
• doctor 可直接看出能力。 cc-connect-next doctor 现在会报告当前后端是否
  支持 native steer；配置选择了 steer、但后端不支持时会给出明确警告和修复
  方向。
• 文档与安装说明对齐。 README、配置示例、双语使用文档、npm README 和
  飞书卡片契约均已改为描述真实默认值及 exec 兼容退出路径。

升级

稳定版用户可以直接更新或重新安装：

cc-connect-next update
# 或
npm install -g cc-connect-next

升级前若 Codex 配置没有写 backend，升级后它会从逐回合 exec 切换为本地
app-server/stdio。需要保留旧路径时，显式设置：

[projects.agent.options]
backend = "exec"

English

This stable patch fixes the default configuration chain. v0.1.3 made steer
the default busy-message policy, but a direct install still generated an
agent/backend combination without native steering, so the policy could only
fall back to the queue. v0.1.4 aligns the backend defaults with the policy.

Changes

• Direct installs get native steering by default. The generated config now
  explicitly writes [queue] busy_message_mode = "steer", selects Codex, and
  launches a local Codex app-server with backend = "app_server" plus
  app_server_url = "stdio". After replacing the REPLACE placeholders,
  turn/steer works without additional hidden configuration.
• Existing minimal Codex configs are fixed too. For Codex, an omitted
  backend now resolves to app_server, and an omitted app_server_url
  resolves to stdio. Upgrading therefore gives existing minimal configs the
  same steer-capable path without rewriting the config file.
• Explicit exec remains supported. Users who set backend = "exec" keep
  the per-turn codex exec --json subprocess behavior. That backend cannot
  append input to an in-flight turn, so busy messages safely fall back to FIFO.
  Keep this setting explicitly if you depend on the legacy path.
• Doctor exposes the capability. cc-connect-next doctor now reports
  whether the configured backend supports native steering and gives a clear
  warning plus remediation when steer is selected without that capability.
• Installation and configuration docs match reality. The READMEs, config
  example, bilingual usage docs, npm README, and Feishu card contract now
  describe the actual defaults and the explicit exec compatibility opt-out.

Upgrade

Stable users can update or reinstall directly:

cc-connect-next update
# or
npm install -g cc-connect-next

If an existing Codex config omits backend, upgrading changes it from the
per-turn exec path to local app-server/stdio. To retain the old path, set:

[projects.agent.options]
backend = "exec"