Repository navigation
cc-remote v5.3.1
cc-remote v5.3.1
中文
修复 Codex 历史加载后问答顺序错乱,以及补充回答先显示原文、加载更多历史后才变成问答气泡的问题。
- 合并缓存、实时记录和历史页时,保留原生用户消息修正后的时间戳,并围绕共享消息身份排列缺失记录,避免提问与回答倒置、工具记录移动到后续正文之后。
- 完整的补充回答首次加载就显示问答气泡,加载旧历史和恢复缓存后保持一致。“已回答”状态仍需匹配唯一的前置原生提问;截断或不完整内容保留原文。
- Claude Agent SDK 从 0.2.157 升到 0.2.174。账号隔离启动对齐新版 SDK 的会话状态握手,保留显式配置,继续使用用户配置的日常 Claude Code CLI。
升级
通信协议保持 v85,从 v5.3.0 升级无需协议迁移。更新 Relay 和各台 Wrapper 后,刷新 Web/PWA 或重新打开 Desktop。
cc-remote update --check --version 5.3.1
cc-remote update --version 5.3.1本次改变 SDK 固定版本。使用独立 Claude 会话服务的安装,需要先让原生任务、后台工作和待授权请求结束,再按会话服务升级流程协调升级服务与 Wrapper。普通 Wrapper 更新不会替换仍在运行的 SDK 服务;不要跳过 SDK 版本校验或强行重启忙碌的服务。从更早协议升级仍需按 v5.3.0 发布说明协调迁移。
发布包含六个平台的 Relay/Wrapper 包、install.sh 和 SHA256SUMS,由 GitHub Actions 完成回归、平台导入检查和 attestation。没有新的 Desktop 或移动端安装包;发布本身不切换线上服务。
English
Fix Codex question/reply order after history loading and supplemental answers changing from raw text into a question/answer bubble only after loading older history.
- Preserve refined native user-message timestamps when merging cached, live and historical records. Interleave missing records around shared message identities so questions stay before their replies and tools stay beside the relevant commentary.
- Render complete supplemental answers consistently from the first page through cache restoration and pagination. Answered receipts still require one unambiguous preceding native question; truncated or incomplete content retains its original text.
- Upgrade Claude Agent SDK from 0.2.157 to 0.2.174. Align the account-isolated transport with the SDK session-state handshake, retain explicit settings and continue using the configured daily Claude Code CLI.
Upgrade
Wire protocol remains v85. Upgrading from v5.3.0 needs no wire-protocol migration. Update the Relay and each Wrapper, then reload Web/PWA or reopen Desktop.
cc-remote update --check --version 5.3.1
cc-remote update --version 5.3.1The SDK pin changes in this release. Installations with an independent Claude session service must let native turns, background work and pending callbacks finish, then coordinate the service and Wrapper upgrade using the session-service procedure. An ordinary Wrapper upgrade does not replace a running SDK service. Do not bypass version checks or restart a busy owner. Earlier wire protocols still require the coordinated migration described in the v5.3.0 notes.
The release includes six platform-specific Relay/Wrapper bundles, install.sh and SHA256SUMS, with GitHub Actions regression tests, platform import checks and attestation. It includes no new Desktop or mobile installer. Publishing does not deploy services.