cc-connect-next v0.1.5

cc-connect-next v0.1.5

中文

这个稳定版带来一条完整的反馈通路：使用中遇到任何问题，都可以在聊天里一键
反馈给项目作者——无需 GitHub 账号。同时修复了 Codex app-server 后端丢弃
cmd 额外参数的问题（issue #37），service_tier 成为一等配置项，rich
卡片支持简洁的模型信息 footer。

变化

• 应用内反馈通道。 回合失败后会出现一张询问卡：梳理好的问题 +
  「要反馈给作者吗？」+【反馈给作者】【忽略】按钮。点一下即匿名提交为
  GitHub issue（经作者侧中继，无需 GitHub 账号），最近错误与配置上下文
  自动附上，凭据/ID/路径自动脱敏。也可随时手动发送
  /feedback <描述>。重复问题自动合并为已有 issue 的 +1 评论。
  绝不会在未经你同意的情况下上报任何内容；[feedback] enabled = false
  可整体关闭。
• Agent 知道真实的配置面。 每个会话首条消息注入一段能力简报，列出当
  前 agent 全部可配置项。问 Agent"怎么配 X"时，它基于真实键集回答；不
  存在的能力会如实告知并指引反馈，不再编造配置键。
• Codex cmd 额外参数在 app-server 后端生效（issue #37）。 自定义二
  进制路径与 -c 覆盖现在两个后端行为一致；结构化选项在键冲突时优先。
• service_tier 一等配置项。 service_tier = "fast" 直接写在
  [projects.agent.options]，无需再经 cmd 注入；reasoning_effort
  新增支持 "max"，不支持的取值会告警而非静默忽略。
• rich 卡片支持回复 footer。 reply_footer = true 时完成卡片底部显
  示一行 模型 · effort（默认关闭，隐私优先契约不变）。footer 内容整体
  瘦身为仅模型与推理强度；show_context_indicator 与
  show_workdir_indicator 废弃为无操作。
• 配置错误不再静默。 顶层配置里本版本不认识的键会在启动后主动提示，
  并可一键反馈给作者。

升级

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

升级须知：反馈通道默认开启（提交永远需要你逐次同意）；若此前开启了
reply_footer，footer 内容将从多行元数据变为一行 模型 · effort。

English

This stable release ships a complete feedback loop: any problem you hit can
be reported to the project author straight from chat — no GitHub account
needed. It also fixes the Codex app-server backend dropping cmd extra
args (issue #37), promotes service_tier to a first-class option, and adds
a compact model footer to rich cards.

Changes

• In-app feedback channel. After a failed turn a question card appears:
  the summarized problem plus "Report to the author?" with
  [Report to author] / [Ignore] buttons. One tap files an anonymous GitHub
  issue through an author-operated relay (no GitHub account required), with
  the recent error and config context attached and credentials/ids/paths
  redacted automatically. /feedback <description> works anywhere, any
  time. Duplicate reports thread onto the existing issue as "+1" comments.
  Nothing is ever submitted without your explicit consent;
  [feedback] enabled = false turns the channel off entirely.
• The agent knows the real configuration surface. Each session's first
  message carries a capability brief listing every configurable option for
  the active agent, so asking "how do I configure X" gets answers from the
  real option set — capabilities that do not exist are stated plainly with
  a pointer to feedback, instead of invented keys.
• Codex cmd extra args reach the app-server backend (issue #37).
  Custom binaries and -c overrides now behave identically on both
  backends; structured options win on duplicate keys.
• First-class service_tier. Set service_tier = "fast" directly in
  [projects.agent.options] — no more smuggling it through cmd.
  reasoning_effort additionally accepts "max", and unsupported values
  warn instead of being silently ignored.
• Rich cards can render the reply footer. With reply_footer = true, a
  finished card carries a dim model · effort line (default off; the
  privacy-first contract is unchanged). The footer itself slims down to
  model and effort only; show_context_indicator and
  show_workdir_indicator become documented no-ops.
• Config mistakes are no longer silent. Top-level keys this build does
  not recognize are announced after startup and can be reported to the
  author with one tap.

Upgrade

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

Upgrade notes: the feedback channel is enabled by default (submission
always requires your per-case consent); if you had reply_footer on, the
footer changes from multi-line metadata to a single model · effort line.