Release Notes

中文

更新内容

• 新增 TLS 配置管理，可在“网络设置”中启用 TLS，并配置证书与私钥路径。
• 支持通过系统文件选择器选择 TLS 证书和私钥文件，同时保留手动输入路径的方式。
• WebUI、API、管理接口及 Agent 配置会根据 TLS 状态自动切换 HTTP 或 HTTPS。
• 将“网络与会话”拆分为“网络设置”和“会话路由”，优化配置页面结构。
• 网络设置、失败重试、会话路由和 TLS 配置现在可以分别保存，避免不同模块相互覆盖。
• 将“允许局域网”改为“自定义监听 IP”，支持配置 IPv4 和 IPv6 地址。
• 改进自定义监听 IP 下的内核启动检测、运行状态判断及管理接口连接逻辑。
• 首页现在仅显示一个 API URL，并根据监听 IP、端口及 TLS 状态自动生成。
• 内核未启动时也可以访问“使用记录”页面并查看本地历史记录。
• 改进 Codex 模型目录生成逻辑，保持运行时模型标识和显示名称一致。
• Codex 会话管理现在会统计 SQLite 数据库与 rollout 文件中的实际会话总数。
• 改进 Codex 配置与 auth.json 的同步、验证、事务更新及回滚机制。
• 修复关闭 Codex 配置后 OAuth 模式未正确保留的问题。

特别注意

启用 TLS 前，请准备内核可读取且相互匹配的 PEM 证书与私钥。使用自签名证书时，浏览器可能会显示安全警告。

除非您清楚自己在做什么，否则请不要下载名称中带有“aarch64”或“update”的版本。

English

What's Changed

• Added TLS configuration management under Network Settings, including certificate and private-key paths.
• Added native file pickers for TLS certificate and private-key files while retaining manual path entry.
• WebUI, API, management endpoints, and agent configurations now automatically switch between HTTP and HTTPS based on the TLS setting.
• Split “Network & Session” into separate “Network Settings” and “Session Routing” pages.
• Network, failure-retry, session-routing, and TLS settings can now be saved independently.
• Replaced “Allow LAN” with a custom listen-IP field supporting both IPv4 and IPv6.
• Improved core startup detection, runtime status checks, and management connections when using a custom listen IP.
• The home page now displays a single API URL generated from the configured listen IP, port, and TLS state.
• Usage records can now be accessed while the core is stopped.
• Improved Codex model-catalog generation to preserve runtime model identities and display names.
• Codex session management now reports the actual total across SQLite databases and rollout files.
• Improved synchronization, validation, transactional updates, and rollback for Codex configuration and auth.json.
• Fixed an issue where Codex OAuth mode was not preserved after closing configuration changes.

Special Notice

Before enabling TLS, provide a matching PEM certificate and private key that the core can read. Browsers may display a security warning when using a self-signed certificate.

Unless you know exactly what you are doing, do not download versions with “aarch64” or “update” in their names.