更新日志（中文）
[0.23.6] - 2026-05-16
新增
- Codex API Key 账号与本地 API 服务现可绑定 OAuth 账号：基于 API Key 的 Codex 使用会保留所选 OAuth 账号作为登录身份，同时由 API Key 账号或本地 API 服务提供运行时 provider。
- Codex OAuth 绑定现提供可检索的账号选择器：绑定弹框支持搜索、套餐/状态筛选、标签筛选、排序、分页，以及更紧凑的单选账号行，便于快速定位账号。
变更
- Codex 本地 API 服务启动和检测前现要求完成 OAuth 绑定：服务启用与健康检测会使用绑定的 OAuth 登录态，并叠加本地 API 服务的 provider 配置。
- Codex 账号总览现内联展示 API Key 与本地 API 服务的 OAuth 绑定状态：账号卡片可直接查看并调整绑定关系，本地 API 服务预览也会保留显示 2 个成员账号。
- Codex OAuth 绑定弹框已重新设计：弹框采用更紧凑的布局、内部账号列表滚动区域，以及蓝绿色分层视觉，确保保存操作默认可见。
Changelog (English)
[0.23.6] - 2026-05-16
Added
- Codex API Key accounts and the Local API Service can now bind an OAuth account: API-key based Codex usage keeps the selected OAuth account as the login identity while the API Key account or Local API Service provides the runtime provider.
- Codex OAuth binding now has a searchable account picker: the binding dialog supports search, plan/status filters, tag filters, sorting, pagination, and compact single-select rows for faster account lookup.
Changed
- Codex Local API Service now requires an OAuth binding before launch/test calls: service activation and health checks use the bound OAuth login state together with the Local API Service provider settings.
- Codex account overview now shows OAuth binding inline for API Key and Local API Service entries: binding status is visible from the account card, and the Local API Service preview keeps two member accounts visible.
- Codex OAuth binding dialog has been redesigned: the dialog uses a more compact layout, an internal account-list scroll area, and a layered blue/teal visual treatment so the save action remains visible.