docs(codex): clarify codex auth marker
test / unit (pull_request) Successful in 28s
test / integration (pull_request) Successful in 40s
test / unit (push) Successful in 28s
test / integration (push) Successful in 42s

This commit was merged in pull request #108.
This commit is contained in:
2026-05-29 02:45:00 -04:00
parent cea832b21d
commit dcaee53cec
2 changed files with 10 additions and 7 deletions
+6 -4
View File
@@ -188,10 +188,12 @@ EGRESS_AUTH_SCHEMES = ("Bearer", "token")
# logic — declare the role on whichever route # logic — declare the role on whichever route
# injects the OAuth header. # injects the OAuth header.
# #
# codex_auth: legacy marker for Codex API-key-style egress routes. # codex_auth: placeholder marker reserved for follow-up Codex
# It is still accepted for older bottle manifests, but # credential-injection work. It is still accepted so
# no longer triggers an OPENAI_API_KEY placeholder. Codex # existing manifests and future egress-held auth flows
# bottles should prefer device/ChatGPT login state. # have a stable role name, but it no longer triggers an
# OPENAI_API_KEY placeholder. Codex bottles should prefer
# device/ChatGPT login state today.
# #
# Routes without a `role` are pure proxy entries: egress # Routes without a `role` are pure proxy entries: egress
# enforces path_allowlist + injects auth on its own, but nothing # enforces path_allowlist + injects auth on its own, but nothing
+4 -3
View File
@@ -86,9 +86,10 @@ agent_provider:
## Open questions ## Open questions
- `codex_auth` is retained only as a legacy accepted route marker. The - `codex_auth` is retained as a placeholder marker for follow-up Codex
Codex template should not inject an `OPENAI_API_KEY` placeholder; credential-injection work. The Codex template should not inject an
Codex bottles use device/ChatGPT login state instead. `OPENAI_API_KEY` placeholder; Codex bottles use device/ChatGPT login
state instead.
- Existing state-folder transcript capture is Claude-specific and should remain gated to Claude until the follow-up state/transcript refactor. - Existing state-folder transcript capture is Claude-specific and should remain gated to Claude until the follow-up state/transcript refactor.
## References ## References