Skip to content

docs(native-accounts): require relay base_url on chat providers #8015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
loopx-agent merged 1 commit into from
Nov 4, 2026
Merged

docs(native-accounts): require relay base_url on chat providers #8015

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions packages/loopx-codex-provider-routing/NATIVE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,14 @@ therefore never sent to the other route. A custom provider must not shadow the
built-in `openai` provider, and profile overrides remain ineligible because their
effective provider cannot be bound safely to the transaction.

Every custom provider that can carry the loopback relay credential must declare
its `base_url` (for example `http://127.0.0.1:57500/v1`). A definition without
`base_url` resolves to `api.openai.com`; Codex context compaction can use that
default even while another provider is selected, so the relay-scoped credential
is presented to OpenAI and rejected with `401 invalid_api_key`. Installers that
add chat transports should write the relay endpoint into each provider
definition and verify it on readback.

A local authenticated transport sends the original selected model and Responses
body to OpenAI. An explicit upstream quota rejection, 401, 403 or temporary 429 can
try the next configured key before output. Each key is attempted at most once per
Expand Down
Loading