Skip to content

cc-connect-next v0.3.0-beta.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Sep 05:17
· 11 commits to main since this release
v0.3.0-beta.1
97f12a7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

cc-connect-next v0.3.0-beta.1

中文

这是 v0.3.0 的第一个 Beta，重点验证两条新的可信生命周期：用户反馈必须先展示同一
份完整脱敏 Draft 再独立批准，更新必须先展示同一份不可变 Plan 再执行；同时收口
Agent 回合内安全重启、飞书 P2P 真实话题隔离、管理员私聊更新提醒和失败卡片提示。

Beta 渠道

  • 这个版本会作为 GitHub Prerelease 和 npm beta 发布，不会替换 GitHub Latest
    或 npm latest；稳定渠道继续保持 v0.2.1。

  • daemon 更新提醒、cc-connect-next check-update 和
    cc-connect-next update 只查询 Stable，因此不会向现有稳定用户推送这个
    Beta，也不会自动完成 Beta-to-Beta 更新。

  • 明确参与 Beta 时使用：

    npm install -g cc-connect-next@beta
cc-connect-next --version

  • GitHub Prerelease 中仍提供六个平台 archive/zip 与 checksums.txt，可手动下载
    独立二进制；内置 update 不安装 prerelease。

主要变化

  • Feedback 与 Update 接入 Awesome Agent App Features v0.1.1。 聊天
    /feedback 会先展示完整结构化、已脱敏的 Draft；独立按钮或 confirm 只提交
    该 Draft。更新流程使用 Prepare → 展示精确 Plan → confirm → Apply 同一 Plan
    事务，并保留 checksum、staging、版本探针、锁、备份与回滚边界。
  • Agent 拥有正式 Feedback CLI。
    cc-connect-next feedback preview --description ... 在零 Relay 网络请求下返回
    完整 Draft 和一次性 token；feedback submit --approval-token ... 必须来自
    HMAC 鉴权的活动 Agent 回合，并绑定可信 project/session/user 与精确 Draft。
    成功回执包含 status、reference_url 和 deduplicated。
  • Agent 回合内重启不再杀死自己的父 daemon。 Agent 调用
    cc-connect-next daemon restart 时，会通过 mode-0600 Unix API 和回合凭证
    登记 deferred restart，等待当前回答、卡片、Agent writer 与已接收队列完成后
    进入既有 graceful restart/Ready 回执链。外部终端的 supervisor 行为保持不变。
  • 飞书/Lark P2P 真实话题获得独立上下文。 启用 thread isolation 时，非空
    thread_id 成为稳定 session/workspace 身份；用于真实回复的 om_
    message ID 单独持久化，绝不会把 omt_ thread ID 当 Reply API message ID。
  • 稳定版提醒只发明确管理员私聊。 最近群聊、群话题、P2P 话题和普通成员
    session 永远不是 fallback。只有唯一 direct-user 平台和明确列出的
    admin_from ID 才会收到提醒；空值、*、歧义或不支持时保持静默。每轮
    发送完整管理员名单，只有全员成功才记录完成；部分失败会在下一轮完整重试。
  • 失败原因更可操作但不泄露上游原文。 Codex 模型容量不足会显示本地化的
    “稍后重试或切换模型”提示；未知错误继续使用通用安全文案，凭据、路径、内部 ID
    和未经审查的 provider 文本不会进入卡片。
  • Slash command 保持逐字可复制。 普通文本与 inline code 中的
    /feedback、/new、custom command 和 Skill 命令不再被本地路径渲染器
    去掉斜杠或添加 marker；多段真实绝对路径仍按原规则渲染。
  • Feedback Relay 保留旧客户端兼容。 新结构化请求进入 Foundation Relay；
    精确的旧 schema-1 请求先转换，目标仓库和 Issue 渲染继续由服务端控制。
    GitHub 操作使用仓库限定的 GitHub App installation token。

升级与兼容边界

  • 已启用 Feishu thread_isolation 的 P2P 真实话题升级后会使用新的
    thread:<omt_...> session key；此前共享在普通私聊 session 的上下文不会自动
    迁移到新话题。
  • 主动更新提醒需要 [[projects]] 下明确的 admin_from = "ou_..."，并且
    项目中只有一个平台实现 direct-user 消息。空值或 * 仍可用于权限语义，但
    无法枚举为固定提醒收件人。
  • 自定义 feedback.endpoint 必须使用 HTTPS 且路径精确为 /v1/feedback；
    只有 localhost/loopback 开发环境允许 HTTP。
  • Agent Feedback 与安全重启需要新版 daemon 的本地 API。新 CLI 面对旧 daemon
    会在变更前 fail closed，不会退化为伪造聊天消息或立即 supervisor restart。
  • 发布 Beta 不会升级当前正在运行的 daemon。升级、配置变更和真实平台验证仍需
    单独执行。

反馈

Beta 期间如遇到问题，请在聊天中发送 /feedback <描述>，检查完整脱敏预览后
再确认提交；无需 GitHub 账号。

English

This is the first v0.3.0 Beta. It previews two trusted lifecycles: feedback is
rendered from one complete redacted Draft before separate approval, and updates
render one immutable Plan before applying that same Plan. It also closes the
Agent-invoked restart lifecycle, Feishu P2P topic isolation, administrator-only
update reminders, and actionable failure-card gaps.

Beta channel

  • This release is a GitHub Prerelease and npm beta. It does not replace
    GitHub Latest or npm latest; the stable channel remains v0.2.1.

  • Daemon update notices, cc-connect-next check-update, and
    cc-connect-next update query Stable releases only. Existing stable users
    are not prompted to install this Beta, and Beta-to-Beta updates are not
    automatic.

  • Opt in explicitly with:

    npm install -g cc-connect-next@beta
cc-connect-next --version

  • The GitHub Prerelease still includes six platform archives/zips and
    checksums.txt for manual standalone installation. The built-in
    update command never installs prereleases.

Highlights

  • Feedback and Update now consume Awesome Agent App Features v0.1.1.
    Chat /feedback renders the complete structured, redacted Draft first;
    a separate button or confirmation submits only that Draft. Updates use a
    Prepare → render exact Plan → confirm → Apply the same Plan transaction
    with checksum, staging, version probes, locking, backup, and rollback.
  • Agents get a formal Feedback CLI.
    cc-connect-next feedback preview --description ... returns the complete
    Draft and a one-time token with zero Relay network requests.
    feedback submit --approval-token ... requires a live HMAC-authenticated
    Agent turn and binds trusted project/session/user identity to the exact
    Draft. Receipts include status, reference_url, and deduplicated.
  • Agent-invoked restart no longer kills its parent daemon. Inside a turn,
    cc-connect-next daemon restart registers a deferred action through the
    mode-0600 Unix API and turn credential. The existing graceful restart/Ready
    acknowledgement runs only after the answer, card, Agent writer, and accepted
    queue finish. External-terminal supervisor behavior is unchanged.
  • Real Feishu/Lark P2P topics receive independent context. With thread
    isolation enabled, a non-empty thread_id becomes the stable session and
    workspace identity. The concrete om_ message ID required for replies is
    persisted separately; an omt_ thread ID is never sent as a Reply API
    message ID.
  • Stable-release reminders go only to explicit administrator DMs. Recent
    groups, topics, P2P topics, and ordinary member sessions are never fallback
    targets. Delivery requires one unambiguous direct-user platform and explicit
    admin_from IDs; empty, wildcard, ambiguous, or unsupported targets stay
    silent. Every incomplete pass retries the full administrator list and marks
    the project/version complete only after one all-success pass.
  • Failures become actionable without exposing provider text. Codex model
    capacity errors show localized retry-or-switch guidance. Unknown errors keep
    the generic safe copy; credentials, paths, internal IDs, and unreviewed
    provider text never enter the card.
  • Slash commands stay byte-for-byte copyable. /feedback, /new,
    runtime custom commands, and Skill commands in prose or inline code are no
    longer rewritten as local paths. Unambiguous multi-segment absolute paths
    keep the existing rendering behavior.
  • The Feedback Relay remains compatible with installed clients. New
    structured submissions enter the Foundation Relay; exact legacy schema-1
    requests are translated first. Repository selection and Issue rendering
    remain server-owned, and GitHub writes use a repository-scoped GitHub App
    installation token.

Upgrade and compatibility boundaries

  • Existing P2P Feishu topics with thread_isolation enabled start using
    thread:<omt_...> session keys. Context previously shared in the ordinary
    private-chat session is not migrated into the new topic session.
  • Proactive update notices require explicit admin_from = "ou_..." entries
    under [[projects]] and exactly one direct-user-capable platform. Empty or
    wildcard values remain valid permission policies but cannot enumerate fixed
    reminder recipients.
  • A custom feedback.endpoint must use HTTPS and the exact
    /v1/feedback path. HTTP is accepted only for localhost/loopback
    development.
  • Agent Feedback and safe restart require the new daemon local API. A new CLI
    talking to an old daemon fails closed before mutation; it never falls back
    to a fake chat message or immediate supervisor restart.
  • Publishing the Beta does not upgrade a running daemon. Installation,
    configuration changes, and real-platform validation remain separate actions.

Feedback

During the Beta, send /feedback <description> in chat, review the complete
redacted preview, and then confirm it. No GitHub account is required.

Assets 9
Loading