OmaProxy currently pins CLIProxyAPI v7.2.154. Updating the pin to v8.0.13 alone fails: the reviewed Linux amd64 executable is 69,217,256 bytes, exceeding the current 64 MiB executable and 66 MiB expanded-archive limits.
I am preparing separate pull requests for:
- A reviewed backend update with bounded archive validation, actual backend version reporting, explicit update checks, staged configuration validation and rollback.
- Capability-aware routing controls and API-provider editing, plus redacted diagnostics and optional quota notifications.
- Isolated Codex/T3 Responses protocol compatibility tests using a real backend and fake upstream, without provider accounts or inference costs.
Diagnostics will distinguish upstream API-key usage from client usage. Queue consumption will be an explicit action because CLIProxyAPI removes records when its usage queue is read. Existing remote connection work in #2 is being evaluated separately.
The three-tab native UI and private credential storage remain the foundation. Validation will include Python/JavaScript checks, the manifest/QML gates, both backend versions and a native preview with fake accounts.
OmaProxy currently pins CLIProxyAPI v7.2.154. Updating the pin to v8.0.13 alone fails: the reviewed Linux amd64 executable is 69,217,256 bytes, exceeding the current 64 MiB executable and 66 MiB expanded-archive limits.
I am preparing separate pull requests for:
Diagnostics will distinguish upstream API-key usage from client usage. Queue consumption will be an explicit action because CLIProxyAPI removes records when its usage queue is read. Existing remote connection work in #2 is being evaluated separately.
The three-tab native UI and private credential storage remain the foundation. Validation will include Python/JavaScript checks, the manifest/QML gates, both backend versions and a native preview with fake accounts.