[codex] cover attributable model and backend requests

[cooper-oai]

Why

Several high-signal requests run through shared model and backend clients before or outside the main Responses path. They need explicit surface ownership so /models, /wham/usage, and related attributable requests use the same jar as the initiating session.

What changed

• Thread request-scoped surface ownership through shared model-catalog refreshes and model-refresh preflights.
• Add optional HTTP-state context to codex-backend-client so attributable backend routes attach and rotate state.
• Pass the initialized app-server surface into account, catalog, thread, turn, external-agent, and session creation paths, including GET /wham/usage.
• Preserve the initiating surface for child threads, subagents, and detached reviews.

Review guide

• Ownership is optional by design. Process-global work without an initiating surface should remain unattributed instead of guessing a jar.
• Child work should inherit the initiating session's surface before any attributable preflight begins.
• This PR reuses the transport wrappers from #26139; it should not duplicate header policy.

Stack

This is PR 5 of 7 in the native HTTP-state stack. It depends on #26140.

1. #26137: per-surface store
2. #26138: app-server bridge
3. #26139: HTTP and WebSocket transport
4. #26140: login, refresh, logout, and remote control
5. #26141: shared model and backend clients (this PR)
6. #26142: app-owned requests
7. #26143: standalone CLI requests

Validation

• codex-models-manager, codex-model-provider, and codex-backend-client suites
• Targeted app-server usage and inherited-surface tests
• Scoped Clippy, formatting, whitespace, and Bazel lock checks

[chatgpt-codex-connector]

💡 Codex Review

https://github.com/openai/codex/blob/0f98cbc128f32163f297bab873b4334482fc0d4c/codex-rs/Cargo.toml#L40
Commit the regenerated Bazel lockfile

Adding the new http-state workspace member changes Cargo metadata, but this commit does not include an updated MODULE.bazel.lock. The repo rule requires running just bazel-lock-update and committing the lockfile whenever Cargo.toml or Cargo.lock changes (AGENTS.md lines 34-36); I also checked just bazel-lock-check, and it reports MODULE.bazel.lock is out of date, so Bazel CI will fail until the regenerated lockfile is included.

---

https://github.com/openai/codex/blob/0f98cbc128f32163f297bab873b4334482fc0d4c/codex-rs/app-server-transport/src/transport/remote_control/clients.rs#L195-L196
Refresh remote-control client auth with its surface

These client-management requests now attach and rotate the CodexRemoteControl HTTP state, but the 401 retry path in send_client_management_request still constructs recovery with the generic auth_manager.unauthorized_recovery(). When remoteControl/client/list or remoteControl/client/revoke hits an expired token, that refresh omits the remote-control surface and does not replace the remote-control state returned by the refresh endpoint, so the subsequent retry can keep sending stale x-oai-is state; use the same remote_control_auth_recovery helper used by the websocket/enrollment paths before retrying.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[cooper-oai]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 77999e5e43

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[cooper-oai]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a9a7ba690f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[cooper-oai]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 115ba55887

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".