Repository navigation
docs(codex): clarify bridge account selection - #242
Merged
Merged
Conversation
tangletools
approved these changes
Sep 27, 2026
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved PR — ee91f3c6
Blanket team auto-approval is intentional. The merge gates are CI and codex-p1.
No automated review runs on this PR. This approval rests on the rule above alone.
tangletools · auto-approval · reason: blanket_auto_approve · 2026-09-27T10:41:49Z
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Document that each cli-bridge process serves the Codex account selected by its
CODEX_HOME, and thatcodexmust be enabled in that process'sBRIDGE_BACKENDS.Why
A Runtime proof sent
codex/gpt-6-lunato bridge port 8900, which used/home/drew/.codex-laneand returnedworkspace routing discovery unauthorized (401)before inference. The account's access token was expired; the exact account-side reason for the 401 is not independently proven. The healthy GLM bridge on port 3355 did not enable Codex. Current-main bridge code completed the same maintained Runtime composition on an isolated Codex-enabled port 3399 using an active account, so the source invocation path did not need a code change.Verification
streamAgentTurn→ bridge → native Codex completedRUNTIME_CODEX_SUBSCRIPTION_OKwith 10,152 input and 12 output tokens; dollar cost unknown. Bridge runbridge-run-88a48736-fcd0-4e45-b99c-be5f9d2b269ais terminaldone, with retained replay.bridge-run-3c02cb4f-e43e-4fcf-8cc8-b8c82b21f981, terminalcancelledin about four seconds. No Codex child remained; active and in-flight counts were zero.pnpm buildpassed. Focused Codex tests: 26 passed. Runtime consumer check passed. Fullpnpm test: 1,213 passed, 12 skipped, one Pi real-child test timed out at five seconds during shared host load; that test passed alone in 528 ms.codex/defaultconfig inheritance issue outside this explicit-model route.Proof artifacts:
/home/drew/.local/state/fleet/recovery/session-recovery-20260926/cli-bridge-codex-proof/(private local path; no credential values in the PR).