更新日志（中文）
[1.3.34] - 2026-08-28
新增
- Codex OAuth Token 支持手动刷新：可在账号总览刷新账号凭据，并在独立弹框中查看结果、失败原因、重试或重新授权操作。
- 账号池异常诊断：请求没有可用账号时，账号池弹框会说明选路结果并提供恢复操作。
- 按账号设置生图策略：API Service 账号池可单独启用或禁用账号的生图能力，不影响文本请求。
变更
- Codex 认证流程统一：账号总览、默认实例、多开实例、API Service 和 API Key OAuth 绑定现在共用凭据准备、刷新、重新授权、进度和结果处理流程。
- 客户端授权状态改为提示信息：检测到客户端跳转登录页时不再阻止切号或 API Service 使用；服务端明确撤销仍是最高优先级状态。
- OAuth 授权与官方桌面入口保持一致，无本地 Codex 客户端时也可使用；浏览器授权等待时间延长至 10 分钟，客户端版本默认值支持远端管理、本地缓存和设置覆盖。
- 网关按 profile 隔离并优化额度刷新：API Service 与多开实例使用独立网关，批量刷新减少重复进程探测和请求争用。
- 启动操作可恢复：启动弹框支持取消、重试、重新授权，以及跳过可跳过的非阻断失败。
- 订阅信息统一标记为“订阅有效期”，与 Token 有效期明确区分。
修复
- 修复重新授权、切号、额度刷新或 profile 同步后恢复旧 OAuth 凭据的问题，避免账号回退到旧 Token。
- 修复客户端登录页观测导致账号卡片状态过期或更新延迟的问题：账号总览会及时更新客户端状态，并与 API 授权异常分开显示。
- 修复调度失败后账号池异常被隐藏的问题：无可用账号时保留池级诊断，并在账号池弹框中显示本地化恢复信息。
- 修复 API 401 仍显示 API Service 可用的问题：账号状态现在反映真实的上游拒绝结果。
- 修复取消切号后账号卡片仍处于 loading 状态的问题。
- 修复纯文本请求因上游不支持生图而失败的问题，并修正部分控件显示浏览器原生灰色按钮样式的问题。
Changelog (English)
[1.3.34] - 2026-08-28
Added
- Manual Codex OAuth Token refresh: refresh an account's credentials from the account overview and review the result, failure reason, retry, or reauthorization action in a dedicated dialog.
- Account-pool diagnostics: when no account can handle a request, the account-pool dialog explains the selection result and provides recovery actions.
- Per-account image-generation policy: API Service account pools can enable or disable image generation for individual accounts without affecting text requests.
Changed
- Unified Codex authentication flow: account overview, default and managed instances, API Service, and API Key OAuth bindings now use the same credential preparation, refresh, reauthorization, progress, and result handling.
- Client authorization state is informational: an observed client login-page redirect no longer blocks switching or API Service use; an explicit upstream authorization revocation remains the highest-priority state.
- OAuth authorization follows the official desktop entry point and remains usable without a local Codex client; browser authorization now allows up to 10 minutes, and the client-version default can be managed remotely, cached locally, or overridden in Settings.
- Profile isolation and quota refresh efficiency: API Service and managed instances keep independent provider gateways, while batch quota refresh reduces repeated process probing and request contention.
- Launch actions are recoverable: users can cancel, retry, reauthorize, or skip eligible non-blocking failures from the active launch dialog.
- Subscription information is labeled as “Subscription validity” so it is distinct from Token expiration.
Fixed
- Fixed stale OAuth credentials being restored after reauthorization, switching, quota refresh, or profile synchronization, preventing accounts from reverting to an older Token.
- Fixed client login-page observations leaving stale or delayed account-card state: the account overview now updates the recorded client status promptly and keeps it separate from API authorization failures.
- Fixed account-pool errors being hidden after dispatch failures: unavailable-account results now retain pool diagnostics and display localized recovery information in the account-pool dialog.
- Fixed API 401 results being shown as API Service available: the account status now reflects an actual upstream rejection.
- Fixed account cards remaining in a loading state after cancelling a switch.
- Fixed text requests being rejected solely because image generation is unavailable, and corrected affected controls that displayed browser-native gray button styles.