Repository navigation
v0.3.112
English
If you have any questions or suggestions about the software, please reach us through the QQ group or GitHub Issues and we will get back to you as soon as possible.
Added
- Automatic updates in Version Management: the application and the core can now update themselves without a manual download. Pick which targets to follow, and new versions download quietly while the app runs and install on the next launch, before local services start. It is off by default, and manual and automatic updates never run at the same time. Changing the download source, channel or proxy discards the queued download, and a version that failed to install stays blocked until you clear the failure rather than retrying forever. See automatic updates.
Improved
- Version Management is denser: the page uses the available width and tighter spacing, so the update settings and both version cards fit without the tall empty rows that pushed actions below the fold.
Fixed
- Plugin executor usage was mis-priced: records from plugin executors fell back to the OpenAI token convention, but those executors follow the upstream protocol convention. A cache-write-only Claude request reported a 100% cache hit rate, billed uncached input at zero and charged cache writes twice, while Gemini thinking tokens were dropped from output and left unbilled. Records now read the protocol-agnostic
token_breakdownthe core already provides. - Alias saves failed on configs with a trailing section: the YAML editor rejects a document followed by tokens it cannot attach, so a config whose own reader stops at the end of the document failed every alias save with "Content after the document could not be parsed". The trailing part is now split off, edited separately and appended back byte for byte.
- Core updates failed when the kernel binary was read-only: copying reproduced the source permission bits, so overwriting a
0555kernel produced a read-only temporary file and the next write failed withEACCES. The temporary file is now synced through a read-only handle on Unix, the write-opened handle is kept on Windows, and the owner write bit is restored so later updates stay replaceable. - A half-finished automatic update setting could switch the feature off silently: a config with updating enabled but no target selected was replaced wholesale with defaults during sanitization, and the sanitized config was written back, so the reset became permanent. Only the unreachable part is now narrowed, the rest of the record is kept, and the reload writes nothing when the record is already coherent.
codexword replacement used the wrong casing.
简体中文
关于软件,如果您有任何问题或建议,请通过 QQ群 或 GitHub Issues 反馈,我们会尽快处理。
新增
- 版本管理支持自动更新:应用与内核都可以自行更新,无需手动下载。可选择要跟随的更新对象,应用运行期间静默下载新版本,并在下次启动时、本地服务启动之前安装。该功能默认关闭,手动更新与自动更新不会同时进行。更改下载源、通道或代理会使已下载的更新失效;安装失败的版本会保持阻塞状态,直到清除失败记录,而不会无限重试。详见自动更新说明。
改进
- 版本管理页面更紧凑:页面会充分利用可用宽度并收紧间距,更新设置与两张版本卡片不再因高大的空行把操作按钮挤到首屏之外。
修复
- 插件执行器的用量计算错误:插件执行器的记录回退到了 OpenAI 的 token 约定,而这类执行器遵循的是上游协议的约定。仅写入缓存的 Claude 请求会报告 100% 缓存命中率、把未缓存输入按零计费并重复收取缓存写入费用,Gemini 的思考 token 则被从输出中丢弃且未计费。现在改为读取核心已提供的、与协议无关的
token_breakdown。 - 配置文件带有尾部内容时别名保存失败:YAML 编辑器无法接受文档之后无法归属的剩余标记,因此对于自身读取器在文档结尾即停止的配置文件,每次保存别名都会以「Content after the document could not be parsed」失败。现在会把尾部内容单独拆出、分别编辑,再逐字节原样追加回去。
- 内核二进制为只读时更新失败:复制操作会沿用源文件的权限位,因此覆盖一个
0555权限的内核会得到一个只读临时文件,后续写入以EACCES失败。现在在 Unix 上通过只读句柄同步临时文件,在 Windows 上保留可写句柄,并恢复属主写权限,使后续更新仍可覆盖。 - 未完成的自动更新设置会静默关闭该功能:配置中启用了自动更新但未选择任何更新对象时,清理阶段会把整段设置替换为默认值,而清理后的配置又会被写回,导致这次重置永久生效。现在只收敛其中不可达的部分,保留记录的其余内容;当记录本身已经一致时,重新加载不会写入任何内容。
codex词语替换的大小写有误。