viyatb-oai e13c1d569d Prevent custom providers from inheriting ambient auth (#39214) ...

## Why

Custom model providers that do not require OpenAI authentication could inherit
ambient authentication headers, including the bearer token and
`ChatGPT-Account-ID`, and send them to the custom provider endpoint.

## What changed

- Resolve providers without `requires_openai_auth` or configured `auth` as
  unauthenticated.
- Continue to honor an explicit `experimental_bearer_token` or command-resolved
  provider authentication.
- Preserve ambient authentication for OpenAI providers.

## Testing

Added unit and request-level coverage for custom, explicitly authenticated, and
OpenAI provider authentication behavior.

GitOrigin-RevId: d89a79604338bc660a3edb2af0068cfa9b694fa2

2026-08-18 15:06:09 +00:00

..

src

Prevent custom providers from inheriting ambient auth (#39214)

2026-08-18 15:06:09 +00:00

BUILD.bazel

feat: add opt-in provider runtime abstraction (#17713)

2026-04-17 02:27:45 +00:00

Cargo.toml

Migrate direct HTTP consumers to codex-http-client (#31331)

2026-07-07 01:34:36 +00:00