Skip to content

Bump Codex to 0.166.0 and codex-acp to 2.5.0 - #3021

Merged
xeophon merged 1 commit into
mainfrom
bump/codex-20261030
Oct 31, 2026
Merged

xeophon merged 1 commit into
mainfrom
bump/codex-20261030

Conversation

@xeophon

@xeophon xeophon commented Oct 30, 2026 •

Copy link
Copy Markdown
Member

Update the Codex harness to Codex 0.166.0 and codex-acp 2.5.0.

Codex continues to use only the Responses API; the source reference now points to the 0.166.0 wire API definition.


Note

Low Risk
Version pin updates in the Codex install harness with no logic or API wiring changes beyond dependency versions.

Overview
Updates the Codex harness pinned dependencies: @openai/codex default from 0.164.0 to 0.166.0, and @agentclientprotocol/codex-acp from 2.2.2 to 2.5.0 (used at install time via VF_CODEX_* env vars).

The inline comment linking Codex’s wire API constraint is retargeted to the 0.166.0 model-provider-info source; behavior is unchanged—the harness still pins dialect: "responses" only.

Reviewed by Cursor Bugbot for commit 5e5514c. Bugbot is set up for automated code reviews on this repo. Configure here.

Note

Bump Codex to 0.166.0 and codex-acp to 2.5.0

Updates the pinned versions in the Codex harness: the ACP package goes from 2.2.2 to 2.5.0, and the default Codex version in CodexHarnessConfig goes from 0.164.0 to 0.166.0, in harness.py. Behavioral Change: new harness runs will use Codex 0.166.0 and codex-acp 2.5.0 by default.

Macroscope summarized 5e5514c.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-30T23:36:19.044210Z 5e5514c PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@macroscopeapp

macroscopeapp Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Approved at 5e5514c

Macroscope's review found this PR approvable — Updates the Codex harness to Codex 0.166.0 and codex-acp 2.5.0. The change is confined to that harness’s versioned installation path, with existing API and tool-control wiring unchanged.

You can add or adjust custom eligibility rules. Learn more.

@xeophon
xeophon merged commit 0860b3d into main Oct 31, 2026
63 of 65 checks passed
@xeophon
xeophon deleted the bump/codex-20261030 branch October 31, 2026 00:51
mikasenghaas added a commit to PrimeIntellect-ai/prime-rl that referenced this pull request Nov 2, 2026
## Summary

- Bump `prime-sandboxes` 0.5.1 → 0.5.3 so live sandbox processes are no
longer capped at 24h (via PrimeIntellect-ai/verifiers#3043).
- Bump `deps/verifiers` `60290d4` → `bccc2c5` (verifiers main, with
PrimeIntellect-ai/verifiers#3043 merged).
- Require `prime-runs[train]>=0.1.5` from PyPI. This drops the
`prime-runs` git source and the `prime-traces` git override, both pinned
to `adf8d25c`. The new verifiers requires `prime-runs>=0.1.5`
(PrimeIntellect-ai/verifiers#3001), and the old git pin no longer
resolves. 0.1.5 contains `adf8d25c`, so it includes
PrimeIntellect-ai/prime#1109. `uv.lock`: `prime-runs` 0.1.4 (git) →
0.1.5, `prime-traces` 0.0.10 (git) → 0.0.11.

### Why

On Prime, the SDK sent a fixed 24h deadline on every live process
stream, and the sandbox ended the process when it expired. A long agent
segment then lost its ACP process. The trace stopped as `harness_error`
(`EOFError: ACP process closed its stdout`) instead of `agent_timeout`,
so `agent_timeout` undercounted real 24h cap hits.

### prime-sandboxes changes (0.5.1 → 0.5.3)

0.5.3:
- fix(sandboxes): stop capping live processes at 24h
(PrimeIntellect-ai/prime#1142)

0.5.2:
- feat(sandbox): add localhost forwards to the CLI and SDK
(PrimeIntellect-ai/prime#1124)
- feat(sandboxes): add pause and resume to the SDK and CLI
(PrimeIntellect-ai/prime#1056)
- fix(cli): write credential files owner-only
(PrimeIntellect-ai/prime#1130); the SDK auth cache is written 0600

### verifiers changes (`60290d4` → `bccc2c5`)

Fixes and features:
- fix(serve): discard kept episodes when clients disconnect
(PrimeIntellect-ai/verifiers#2997)
- Reuse interception tunnels for task-scoped MCP servers
(PrimeIntellect-ai/verifiers#3006)
- Run Prime task services as native VMs and fix Harbor setup
(PrimeIntellect-ai/verifiers#2910)
- Run Compose services as native Prime VMs
(PrimeIntellect-ai/verifiers#2918)
- Accept Harbor Compose tasks on native VMs
(PrimeIntellect-ai/verifiers#2999)
- Add a native Compose integration test on Prime
(PrimeIntellect-ai/verifiers#3010)
- fix(harbor): reject ignored verifier user overrides
(PrimeIntellect-ai/verifiers#3014)
- Honor configured disk size for native Compose sidecars
(PrimeIntellect-ai/verifiers#3018)
- Size native Compose disks per service
(PrimeIntellect-ai/verifiers#3020)
- fix: use apk-installed Node and npm on Alpine
(PrimeIntellect-ai/verifiers#3004)
- fix: retry Node downloads before extracting
(PrimeIntellect-ai/verifiers#3005)
- fix(CVE-2026-111497) in Brotli and Node
(PrimeIntellect-ai/verifiers#2998)

Dependency pins:
- bump prime-sandboxes to 0.5.3 (PrimeIntellect-ai/verifiers#3043)
- chore: require prime-runs 0.1.5 from PyPI
(PrimeIntellect-ai/verifiers#3001)

Harness versions:
- Bump Codex to 0.166.0 and codex-acp to 2.5.0
(PrimeIntellect-ai/verifiers#3021)
- Bump DeepSeek harness to 0.2.1-rc.5 (PrimeIntellect-ai/verifiers#3023)
- Bump mini-swe-agent's LiteLLM dependency to 1.106.6
(PrimeIntellect-ai/verifiers#3031)
- Bump Hermes Agent to v0.22.5 (PrimeIntellect-ai/verifiers#3024)
- Bump Claude Code to 2.1.314 and claude-agent-acp to 0.99.1
(PrimeIntellect-ai/verifiers#3022)
- Bump Kimi Code to 2.4.1 (PrimeIntellect-ai/verifiers#3025)
- Bump OpenCode to 2.2.5 (PrimeIntellect-ai/verifiers#3026)
- Bump OpenClaw to 2026.10.9 (PrimeIntellect-ai/verifiers#3027)
- Bump Prime Agent to 0.10.2 (PrimeIntellect-ai/verifiers#3028)
- Bump nano-rlm to e4d4407f (PrimeIntellect-ai/verifiers#3029)
- Bump Terminus 2 to Harbor 0.25.0 (PrimeIntellect-ai/verifiers#3030)

Dependabot lockfile bumps in verifiers (they do not change prime-rl's
lock):
- urllib3 2.7.0 → 2.8.0 (PrimeIntellect-ai/verifiers#2733), pyjwt 2.13.0
→ 2.15.0 (PrimeIntellect-ai/verifiers#2735), opentelemetry-api 1.44.0 →
1.45.1 (PrimeIntellect-ai/verifiers#2964), authlib 1.7.2 → 1.9.1
(PrimeIntellect-ai/verifiers#2990), msgpack 1.2.1 → 1.2.3
(PrimeIntellect-ai/verifiers#2991), litellm 1.98.0 → 1.100.4
(PrimeIntellect-ai/verifiers#2992), dnspython 2.8.0 → 2.9.0
(PrimeIntellect-ai/verifiers#2993), filelock 3.32.4 → 4.2.1
(PrimeIntellect-ai/verifiers#3002), virtualenv 21.14.12 → 21.14.13
(PrimeIntellect-ai/verifiers#3008), joserfc 1.7.4 → 1.7.6
(PrimeIntellect-ai/verifiers#3017), oauthlib 3.3.1 → 4.0.0
(PrimeIntellect-ai/verifiers#3035)

## Verification

- `uv sync --frozen --all-packages --all-extras` installs
`prime-sandboxes` 0.5.3.
`prime_sandboxes.sandbox._LIVE_PROCESS_NO_TIMEOUT_MS == 9999999999` is
the default deadline for every `open_process` stream.
- `uv.lock` changes only `prime-sandboxes`, `prime-runs` and
`prime-traces` (plus a uv-written reorder of the `exclude-newer-package`
table).
- `pytest tests/unit --ignore=tests/unit/train`: 837 passed, 1 xfailed.
- `tests/unit/train` (RTX PRO 6000 Blackwell, SM120):
`qwen3_8_flash_next` and `test_fp8_grouped_gemm` show the same failures,
and `test_fused_lm_head.py::test_inject_prime_lm_head_vanilla` kills the
process, on this branch and on `main` (`823ed27`). These GPU kernel
tests do not touch this diff.
- verifiers#3043: the live Prime runtime tests
(`tests/unit/test_runtimes.py -k prime`, including `test_exec` on a live
process) pass on 0.5.3.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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