Skip to content

[codex] cover attributable backend HTTP state#26081

Closed
cooper-oai wants to merge 1 commit into
cooper/codex-native-integrity/9from
cooper/codex-native-integrity/10
Closed

[codex] cover attributable backend HTTP state#26081
cooper-oai wants to merge 1 commit into
cooper/codex-native-integrity/9from
cooper/codex-native-integrity/10

Conversation

@cooper-oai

@cooper-oai cooper-oai commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • make codex-backend-client apply URL-aware auth and observe response headers centrally
  • add an HTTP-state-aware constructor without changing existing ownerless callers
  • attribute app-server /usage and credits-nudge requests to the initialized connection surface

Stack

PR 10 of 15. Depends on #26080. Followed by #26088.

Validation

  • CARGO_INCREMENTAL=0 just test -p codex-backend-client
  • targeted app-server get_account_rate_limits_returns_snapshot integration test
  • CARGO_INCREMENTAL=0 just fix -p codex-backend-client -p codex-app-server
  • just fmt
  • just bazel-lock-check
  • git diff --check

@cooper-oai cooper-oai marked this pull request as ready for review June 3, 2026 07:03

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 29ad9c050a

ℹ️ 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".

Comment thread codex-rs/backend-client/Cargo.toml
@cooper-oai cooper-oai force-pushed the cooper/codex-native-integrity/9 branch from ff25713 to 0f22670 Compare June 3, 2026 07:30
@cooper-oai cooper-oai requested a review from a team as a code owner June 3, 2026 07:30
@cooper-oai cooper-oai force-pushed the cooper/codex-native-integrity/10 branch from 29ad9c0 to cfc0c88 Compare June 3, 2026 07:31
@cooper-oai

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown
Contributor

Codex Review: Didn't find any major issues. Bravo.

ℹ️ 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 cooper-oai force-pushed the cooper/codex-native-integrity/9 branch from 0f22670 to d41149a Compare June 3, 2026 09:17
@cooper-oai cooper-oai force-pushed the cooper/codex-native-integrity/10 branch from cfc0c88 to 6a61467 Compare June 3, 2026 09:17
@cooper-oai

Copy link
Copy Markdown
Contributor Author

@codex review

@cooper-oai cooper-oai force-pushed the cooper/codex-native-integrity/9 branch from d41149a to 0301b58 Compare June 3, 2026 09:54
@cooper-oai cooper-oai force-pushed the cooper/codex-native-integrity/10 branch from 6a61467 to 5e52e52 Compare June 3, 2026 09:54
@cooper-oai

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5e52e5215f

ℹ️ 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".

codex-backend-openapi-models = { path = "../codex-backend-openapi-models" }
codex-api = { workspace = true }
codex-client = { workspace = true }
codex-http-state = { workspace = true }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Commit the refreshed Bazel lockfile

Adding this workspace dependency changes the Rust dependency graph, but this commit updates only Cargo.toml/Cargo.lock and leaves MODULE.bazel.lock unchanged. The root repo guidance requires dependency changes to run just bazel-lock-update and include the refreshed lockfile (AGENTS.md lines 34-37); I also ran just bazel-lock-check, which reported MODULE.bazel.lock is out of date, so Bazel lock validation will fail until the regenerated lockfile is committed.

Useful? React with 👍 / 👎.

Comment on lines +677 to +678
#[test]
fn backend_headers_and_response_observation_rotate_native_http_state() {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3 Badge Move new unit coverage out of the implementation file

This adds new unit coverage inside the inline test module in the main client.rs implementation file, but the repo test guidance says unit tests should go in a dedicated *_tests.rs file and to avoid test-only code in the main implementation (AGENTS.md lines 101-110). Please move this new backend HTTP-state test into a sibling test file so the implementation module does not keep growing with test-only code.

Useful? React with 👍 / 👎.

@cooper-oai

Copy link
Copy Markdown
Contributor Author

Superseded by the collapsed seven-PR stack: #26137 through #26143. Closing this prototype layer to keep review focused.

@cooper-oai cooper-oai closed this Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant