Skip to content

Upstream merge: openai/codex@main into main#196

Merged
zemaj merged 18 commits into
mainfrom
upstream-merge
Sep 22, 2025
Merged

Upstream merge: openai/codex@main into main#196
zemaj merged 18 commits into
mainfrom
upstream-merge

Conversation

@just-every-code

Copy link
Copy Markdown

This PR merges openai/codex@main into main.

aibrahim-oai and others added 18 commits September 19, 2025 00:08
Currently, we change the tool description according to the sandbox
policy and approval policy. This breaks the cache when the user hits
`/approvals`. This PR does the following:
- Always use the shell with escalation parameter:
- removes `create_shell_tool_for_sandbox` and always uses unified tool
via `create_shell_tool`
- Reject the func call when the model uses escalation parameter when it
cannot.
…y-bucket)

- Keep ours for protected core files: codex-rs/core/src/codex.rs, codex-rs/core/src/openai_tools.rs to preserve tool gating, UA/version, and fork-only handlers.
- Adopt upstream test infra improvements (wiremock helpers) and minor exec derives.
- Verified with scripts/upstream-merge/verify.sh and build-fast.sh: ok
Move to using test helper method everywhere.
…y-bucket (prefer-ours TUI/core handlers; prefer-theirs common/exec/file-search)\n- verify.sh: PASS (build-fast ok; api check ok; guards ok)\n- Preserved fork invariants: tool exposure gating, UA/version, public re-exports\n- Purge set unchanged; no conflicts encountered
…r TUI popup alignment and snapshots (prefer_ours)\n- Adopt upstream in common/exec/file-search where applicable\n- Purge reintroduced CLI images per policy\n\nBuild: ./build-fast.sh ok; verify.sh api_check ok
Hopefully fixes incorrectly showing ^J instead of Shift+Enter in the key
hints occasionally.
- Strategy: by-bucket; prefer ours for TUI/core tool wiring; prefer theirs for common/exec/file-search.
- Resolved conflicts by keeping ours for codex-rs/tui/src/app.rs and codex-rs/tui/src/tui.rs per fork UX policy.
- Purge check: no reintroduced .github/codex-cli-* images.
- Guards: verify.sh passed; build-fast.sh OK; UA/version + tool parity preserved.
We currently get information about rate limits in the response headers.
We want to forward them to the clients to have better transparency.
UI/UX plans have been discussed and this information is needed.
…re/codex.rs and fork tool behaviors; include upstream RateLimits stream event; pass verify + build-fast
### /limits: show rate limits graph

<img width="442" height="287" alt="image"
src="https://github.com/user-attachments/assets/3e29a241-a4b0-4df8-bf71-43dc4dd805ca"
/>

### Warning on close to rate limits:

<img width="507" height="96" alt="image"
src="https://github.com/user-attachments/assets/732a958b-d240-4a89-8289-caa92de83537"
/>

Based on openai#3965
… libs

- Preserve fork TUI files (chatwidget, history_cell, slash_command)
- Drop upstream rate_limits_view to avoid unused warnings
- Keep upstream test snapshots (no impact on build)

Build: ./build-fast.sh ok (0 warnings); verify.sh ok
@zemaj zemaj merged commit 3b58abb into main Sep 22, 2025
3 checks passed
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.

5 participants