## Problem
The Codex App cannot discover FCC provider/model slugs because it loads
a local model catalog at startup instead of querying FCC's `/v1/models`
endpoint. Users can configure FCC as a Responses provider, but its
native model picker remains incomplete. Fixes #1260.
## Changes
| Before | After |
| --- | --- |
| FCC generated the Codex catalog only when `fcc-codex` launched. | FCC
synchronizes the catalog from its canonical model lifecycle for
independently launched Codex clients. |
| Startup could leave a configured Codex App without a catalog file. |
Startup creates a missing catalog after routed-provider warming and
preserves an existing last-known-good catalog. |
| Every catalog publication replaced the file. | Identical content is
skipped and changed content is replaced atomically. |
| Catalog filesystem failures could escape a direct writer call. |
Runtime publication is fail-open and logs only the exception type. |
| Codex App setup was undocumented. | The README docum…
Add ChatGPT OAuth as an OpenAI Codex provider (#1279)
## Problem
FCC supports API-key and local providers, but customers cannot use
models included with their ChatGPT subscription. Reusing Codex
credentials would also couple FCC to another application's mutable
authentication state.
## Changes
| Before | After |
| --- | --- |
| OpenAI subscription access was unavailable. | Customers connect
ChatGPT from the local Admin UI with browser PKCE or device code. |
| Provider availability came only from static settings. | A
process-owned connected account adds, refreshes, and evicts OpenAI
models dynamically. |
| FCC had no ChatGPT Codex transport. | `openai/<model-id>` uses
FCC-owned renewable credentials and neutral Responses conversion. |
| Retries and reasoning continuity had no subscription-provider
coverage. | Commit-boundary retries prevent duplicate output while
encrypted reasoning and tool IDs survive round trips. |
<!-- greptile_comment -->
<details open><summary><h3>Greptile Summary</h3></summary>
This PR adds ChatGPT OAuth and a…
Make provider model discovery the sole catalog owner (#1221)
## Problem
Startup model-list I/O was split between a non-enforcing
configured-model validator and the real discovery path. Both queried
providers and populated the same cache even though synchronous cache
warm-up was the validator's only required effect.
## Changes
| Before | After |
| --- | --- |
| Validation and discovery independently resolved providers, queried
model lists, and cached results. | `ProviderModelDiscovery` solely owns
model-list queries, failure reporting, and cache population. |
| Startup ran configured-model validation and then launched discovery. |
Startup synchronously warms referenced providers through discovery, then
launches the existing missing-provider background pass. |
| Absence from a provider catalog produced a non-enforcing missing-model
warning. | Provider catalogs remain discovery metadata and provider
execution remains authoritative. |
| Configured model references retained environment-source metadata for
validator diagnostics. | Configured model …
Add searchable model selection to the Admin UI (#1121)
## Problem
Admin model routing fields required users to construct provider-prefixed
model slugs. Optional tier overrides represented inheritance as an
unexplained blank value.
## Changes
| Before | After |
| --- | --- |
| Model inputs only gained suggestions after an individual provider
refresh. | Model inputs load configured and discovered canonical slugs
from one Admin catalog. |
| Model routing looked like unrestricted text entry. | Model routing
uses the browser's searchable model dropdown while retaining manual
entry. |
| Tier overrides displayed an empty value for fallback routing. | Tier
overrides display **None** and persist it as an unset override. |
| Model refresh returned provider-shaped cache internals. | Model
refresh returns the same canonical catalog consumed by the Admin UI. |
| Users inferred the provider/model slug format from examples. | The
Admin UI and README define and present complete provider/model slugs. |
<!-- greptile_comment -->
<details open><summary>…
Canonicalize provider failure and retry ownership (#1046)
## Problem
Provider SDK classification, retry policy, canonical failures, and
downstream wire errors shared exception types across layers. That
blurred ownership and let cleanup or provisional Responses tool failures
mask the real provider diagnostic.
## Changes
| Before | After |
| --- | --- |
| Provider failures carried Anthropic wire types and core code
classified OpenAI/httpx errors. | Protocol-neutral `ExecutionFailure`
values cross layers, providers classify SDK errors, and protocol
packages map wire types. |
| Provider adapters could author terminal wire events. | The HTTP commit
boundary selects non-2xx JSON or a protocol terminal event with one
ingress request ID. |
| Retry policy and diagnostic handling were spread across core and
provider modules. | Providers own the unchanged retry budgets while
neutral core utilities own bounded credential redaction. |
| Stream cleanup could replace an already-mapped provider failure. |
Cleanup records safe metadata and preserves the ca…
Introduce a typed application boundary for provider execution (#1045)
## Problem
The HTTP adapter owned model routing, provider execution, and
runtime-facing contracts, so API handlers depended on provider
implementation types. Provider preflight also discovered private request
builders dynamically, obscuring the boundary that must fail before
streaming begins.
## Changes
| Before | After |
| --- | --- |
| `api/` owned model routing and shared provider execution. |
`application/` owns routing and a settings-independent
`ProviderExecutor`. |
| API handlers accepted `BaseProvider` callbacks. | API handlers consume
the narrow structural `ProviderPort`. |
| `BaseProvider` discovered `_build_request_body` dynamically. | Both
transport families implement explicit abstract preflight, with LM Studio
composing context validation. |
| Request leases, task control, and provider model metadata had
adapter/provider owners. | Application-owned ports and immutable values
define those cross-package contracts. |
| Boundary direction was implicit. | Architecture contra…
Replace global runtime resources with explicit ownership (#1042)
## Problem
Provider, messaging, and transcription resources relied on
process-global state, leaving replacement, cancellation, and shutdown
ownership ambiguous. Separate server lifetimes could share
event-loop-bound resources or retain failed cleanup work.
## Changes
| Before | After |
| --- | --- |
| Provider clients found limiters through global singleton and scoped
registries. | Each provider instance receives and owns one explicitly
constructed limiter. |
| Messaging queues and voice pipelines relied on singleton or
module-global state. | Each platform owns its limiter and outbox, while
the application owns one injected transcriber. |
| Messaging shutdown mixed ingress, active work, delivery, and SDK
cleanup. | Application shutdown quiesces ingress, drains work, closes
delivery, then releases transcription and providers. |
| Cancelled or failed provider cleanup could be forgotten or treated as
complete. | The provider manager retains shielded generation and
unpublished-runtime c…
Establish single-owner runtime with stream-safe provider hot swaps (#1036)
## Problem
Provider runtime ownership was split between lifecycle code and mutable
FastAPI state, so Admin replacements could leak the new runtime,
double-close the old runtime, or close providers still serving active
streams. The API package also owned concrete process composition,
obscuring subsystem boundaries.
## Changes
| Before | After |
| --- | --- |
| FastAPI routes inspected several concrete `app.state` resources. |
FastAPI receives one explicit `ApiServices` boundary and stores only
`app.state.services`. |
| Admin Apply persisted config and directly replaced one runtime
reference. | Admin Apply validates a candidate, commits atomically, and
publishes it through the single runtime owner. |
| Provider replacement could close clients used by active streams. |
Generation leases retain old providers until each streaming or
non-streaming response finishes. |
| Provider generations owned discovery state and model metadata. |
`ProviderRuntimeManager` owns one application-lifetime …