Add Codex session route migration coverage by ooiuuii · Pull Request #90319 · openclaw/openclaw

ooiuuii · 2026-06-04T12:12:39Z

Summary

add regression coverage for repairing a stale Telegram direct session route from openai-codex to canonical openai
assert session-store repair preserves canonical OpenAI OAuth/auth-profile pins such as openai:work
assert stale Codex runtime/session overrides are cleared after route repair

Context

This is PR2 from the Codex/OpenAI migration follow-up and is scoped only to persisted session-store route state. It intentionally does not change config migration coverage (PR #90317) or model-selection re-persistence behavior.

Related to #90036.

Verification

pnpm tsx .tmp-check-codex-pr2.mts behavior check: PR2_BEHAVIOR_OK
git diff --check

Note: this repository's targeted Vitest startup was very slow locally due repeated Rolldown PLUGIN_TIMINGS output during first-run compilation, so I used a direct behavior check for the repaired helper path and left the regression in the Vitest suite for CI.

Real behavior proof (redacted, Windows official 6.1)

Read-only probe from the real upgraded Windows/Telegram direct session after the 6.1 migration and Telegram smoke test:

{
  "key": "agent:main:telegram:default:direct:<redacted-direct-id>",
  "modelProvider": "openai",
  "model": "gpt-5.5",
  "providerOverride": null,
  "modelOverride": null,
  "authProfileOverride": null,
  "agentHarnessId": null,
  "agentRuntimeOverride": null
}

The same upgraded setup successfully completed a real Telegram direct-session smoke (TELEGRAM_SESSION_SMOKE_OK) using canonical openai/gpt-5.5 plus Codex runtime routing, not the stale openai-codex/* route.

For the auth-pin preservation edge covered by this test-only PR, the focused helper proof remains:

repairCodexSessionStoreRoutes(...)
modelProvider: "openai-codex" -> "openai"
providerOverride: "openai-codex" -> "openai"
model/modelOverride: "openai-codex/gpt-5.5" -> "gpt-5.5"
authProfileOverride: "openai:work" preserved
agentHarnessId / agentRuntimeOverride cleared
PR2_BEHAVIOR_OK

So the real upgraded Telegram session proves the stale route is gone in a live session, while the focused regression proves canonical OpenAI auth pins are preserved when present.

Real behavior proof (structured for gate)

Behavior or issue addressed: stale persisted Telegram direct-session Codex routes are repaired from openai-codex/* to canonical openai / gpt-* while preserving canonical OpenAI OAuth auth-profile pins.
Real environment tested: real upgraded Windows/ROG OpenClaw 2026.6.1 Telegram direct session plus this PR branch on macOS source checkout.
Exact steps or command run after this patch: inspected the redacted real Telegram session store after the Windows 6.1 migration and smoke, then ran node scripts/run-vitest.mjs src/commands/doctor/shared/codex-route-warnings.test.ts --testNamePattern="repairs Telegram direct session routes" on this PR head.
Evidence after fix: copied live terminal/session output:

Real Windows/Telegram direct session after migration:
key: agent:main:telegram:default:direct:<redacted-direct-id>
modelProvider: openai
model: gpt-5.5
providerOverride: null
modelOverride: null
authProfileOverride: null
agentHarnessId: null
agentRuntimeOverride: null
TELEGRAM_SESSION_SMOKE_OK

$ node scripts/run-vitest.mjs src/commands/doctor/shared/codex-route-warnings.test.ts --testNamePattern="repairs Telegram direct session routes"
[test] starting test/vitest/vitest.commands.config.ts
✓ commands src/commands/doctor/shared/codex-route-warnings.test.ts (109 tests | 108 skipped) 130ms
Tests 1 passed | 108 skipped (109)
[test] passed 1 Vitest shard in 18.29s

Observed result after fix: the live Telegram session no longer persisted openai-codex/*; the focused regression passed and preserves canonical auth pins while clearing stale Codex runtime/session overrides.
What was not tested: no OAuth token reset/re-login was performed; unrelated config migration coverage remains in PR Add Codex multi-agent config migration coverage #90317 and forward write-boundary protection remains in PR Normalize legacy Codex session runtime state #90321.

clawsweeper · 2026-06-04T12:16:49Z

Codex review: needs maintainer review before merge. Reviewed June 4, 2026, 12:14 PM ET / 16:14 UTC.

Summary
This PR adds a regression test for repairing a Telegram direct session route from legacy openai-codex state to canonical openai while preserving an openai:work auth pin and clearing stale Codex runtime pins.

PR surface: Tests +39. Total +39 across 1 file.

Reproducibility: yes. at the helper level: source inspection shows the stale session entry shape is repaired by repairCodexSessionStoreRoutes, and the PR body supplies targeted Vitest output. I did not rerun tests because this review is read-only.

Review metrics: none identified.

Merge readiness
Overall: 🦞 diamond lobster
Proof: 🦞 diamond lobster
Patch quality: 🦞 diamond lobster
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Next step before merge

No automated repair lane is needed; the remaining action is ordinary maintainer review and CI for a narrow test-only PR.

Security
Cleared: The diff is test-only, uses a synthetic Telegram direct id, and the PR body proof is redacted; I found no concrete security or supply-chain concern.

Review details

Best possible solution:

Land the focused regression test after normal CI and maintainer review, while keeping the related config-migration and forward write-boundary work in their separate PRs.

Do we have a high-confidence way to reproduce the issue?

Yes, at the helper level: source inspection shows the stale session entry shape is repaired by repairCodexSessionStoreRoutes, and the PR body supplies targeted Vitest output. I did not rerun tests because this review is read-only.

Is this the best way to solve the issue?

Yes. A focused regression in the doctor session-store route tests is the narrow maintainable place for this edge; config migration and forward write-boundary protection are intentionally separate follow-ups.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against c0b3c8cdb9dc.

Label changes

Label changes:

add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes redacted real Windows/Telegram upgraded-session output plus targeted terminal test output for the added regression.
add rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
remove rating: 🐚 platinum hermit: Current PR rating is rating: 🦞 diamond lobster, so this older rating label is no longer current.

Label justifications:

P2: The PR adds regression coverage for a real session-route migration bug with limited, test-only blast radius.
rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body includes redacted real Windows/Telegram upgraded-session output plus targeted terminal test output for the added regression.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes redacted real Windows/Telegram upgraded-session output plus targeted terminal test output for the added regression.

Evidence reviewed

PR surface:

Tests +39. Total +39 across 1 file.

View PR surface stats

Area	Files	Added	Net
Source	0	0	0
Tests	1	39	+39
Docs	0	0	0
Config	0	0	0
Generated	0	0	0
Other	0	0	0
Total	1	39	+39

What I checked:

Repository policy read and applied: The full root policy was read, including the review-depth, Codex-contract, session-state, and Telegram proof guidance that apply to this PR. (AGENTS.md:12, c0b3c8cdb9dc)
Maintainer note checked: The Telegram maintainer note requires real Telegram proof for transport-visible Telegram behavior; this PR is test-only and does not change Telegram transport code, but the body includes a redacted real Telegram session smoke. (.agents/maintainer-notes/telegram.md:1, c0b3c8cdb9dc)
PR diff is narrow test coverage: The live PR diff adds one Vitest case using synthetic Telegram direct key 5550100999; it asserts provider/model canonicalization, openai:work auth pin preservation, and Codex runtime pin clearing. (src/commands/doctor/shared/codex-route-warnings.test.ts:3830, 127722fdb41f)
Current helper supports the asserted behavior: rewriteSessionModelPair rewrites openai-codex provider fields to openai, converts legacy model refs, and repairCodexSessionStoreRoutes clears stale runtime pins only after route/fallback repair; the code path does not overwrite an unrelated canonical authProfileOverride. (src/commands/doctor/shared/codex-route-warnings.ts:2882, c0b3c8cdb9dc)
Current main lacks the exact new regression: Current main already has adjacent session-route tests and a canonical OpenAI preservation test, but an exact search found no Telegram direct synthetic session test or matching title, so the PR still adds unique coverage. (src/commands/doctor/shared/codex-route-warnings.test.ts:3907, c0b3c8cdb9dc)
Codex app-server contract checked: The sibling Codex source documents and types modelProvider on thread start/resume/list responses, and its processor returns session_configured.model_provider_id; this supports treating provider identity as a real route field rather than a cosmetic string. (../codex/codex-rs/app-server/README.md:271, 4ae7930f58c9)

Likely related people:

Peter Steinberger: Current-main blame and history tie the session-route repair helper and adjacent regression tests to recent work by this author. (role: recent area contributor; confidence: high; commits: cc73ef8ba59a, 6a6da54062fb; files: src/commands/doctor/shared/codex-route-warnings.ts, src/commands/doctor/shared/codex-route-warnings.test.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

ooiuuii · 2026-06-04T13:29:42Z

@clawsweeper re-review after adding redacted Windows 6.1 Telegram session-route proof to the PR body.

clawsweeper · 2026-06-04T13:29:46Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/26954905674
Updated: 2026-06-04T13:37:00.434Z

ooiuuii · 2026-06-04T15:51:37Z

Follow-up 127722fdb4 addresses the privacy/security-boundary review note: the Telegram direct-session id in the regression fixture is now synthetic (5550100999), and the PR body proof has been redacted as <redacted-direct-id>.

Verification performed:

rg -n '8589344021' src/commands/doctor/shared/codex-route-warnings.test.ts returns no matches.
git diff --check passed before the local targeted Vitest attempt.
Local targeted Vitest again stalled with no output in this environment, so CI remains the authoritative execution gate.

The test still covers the same route shape: a Telegram direct session with legacy openai-codex provider/model state is repaired to canonical openai / gpt-5.5 while preserving canonical OpenAI auth pins.

@clawsweeper re-review

clawsweeper · 2026-06-04T15:51:40Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/26963128755
Updated: 2026-06-04T16:01:16.772Z

* Add Codex session route migration coverage * Use synthetic Telegram session id in Codex test

…26.6.5) (#963) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.1` → `2026.6.5` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.5`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202665) [Compare Source](openclaw/openclaw@v2026.6.1...v2026.6.5) ##### Highlights - QQBot now strips model reasoning/thinking scaffolding before native delivery, preventing raw `<thinking>` content from leaking into channel replies. ([#89913](openclaw/openclaw#89913), [#90132](openclaw/openclaw#90132)) Thanks [@openperf](https://github.com/openperf). - MCP tool results now coerce `resource_link`, `resource`, `audio`, malformed image, and future non-text/image blocks at the materialize boundary, preventing Anthropic 400s and poisoned session history after a tool returns richer MCP content. ([#90710](openclaw/openclaw#90710), [#90728](openclaw/openclaw#90728)) Thanks [@RanSHammer](https://github.com/RanSHammer) and [@849261680](https://github.com/849261680). - Anthropic extended-thinking sessions recover after prompt-cache expiry or Gateway restart because stream start events wait for `message_start`, letting pre-generation signature errors trigger the existing recovery retry. ([#90667](openclaw/openclaw#90667), [#90697](openclaw/openclaw#90697)) Thanks [@openperf](https://github.com/openperf). - Parallel is now a bundled `web_search` provider with `PARALLEL_API_KEY` discovery, guarded endpoint handling, cache-safe session ids, onboarding picker support, and docs. ([#85158](openclaw/openclaw#85158)) Thanks [@NormallyGaussian](https://github.com/NormallyGaussian). - Google Vertex ADC users get static catalog rows and runtime model resolution again, while single-provider cooldown recovery and memory adapter status checks are more reliable. ([#90506](openclaw/openclaw#90506), [#90609](openclaw/openclaw#90609), [#90717](openclaw/openclaw#90717), [#90816](openclaw/openclaw#90816)) Thanks [@849261680](https://github.com/849261680). - Matrix can preflight voice notes before mention gating, preserve thread reads/replies through Matrix relations pagination, and carry QA coverage for voice and thread flows. ([#78016](openclaw/openclaw#78016), [#90415](openclaw/openclaw#90415)) - Auth and plugin install state is more durable: auth profiles now live in SQLite, official npm plugin install records keep their trusted pins, and prerelease fallback integrity checks avoid carrying stale integrity forward. ([#89102](openclaw/openclaw#89102), [#88585](openclaw/openclaw#88585)) - macOS node mode no longer silently self-reconnects away from a healthy direct Gateway session, reducing unexpected companion app session churn. ([#90668](openclaw/openclaw#90668), [#90815](openclaw/openclaw#90815)) Thanks [@vrurg](https://github.com/vrurg). - Upgrade and service paths are safer: cron legacy JSON stores migrate during doctor preflight, service env placeholders no longer mask state-dir secrets, WhatsApp startup waits are bounded, and disabled WhatsApp accounts tear down on config reload. ([#90072](openclaw/openclaw#90072), [#90208](openclaw/openclaw#90208), [#90277](openclaw/openclaw#90277), [#90488](openclaw/openclaw#90488), [#90486](openclaw/openclaw#90486), [#87951](openclaw/openclaw#87951), [#87965](openclaw/openclaw#87965)) Thanks [@MonkeyLeeT](https://github.com/MonkeyLeeT), [@sallyom](https://github.com/sallyom), [@mcaxtr](https://github.com/mcaxtr), and [@MukundaKatta](https://github.com/MukundaKatta). ##### Changes - Search/providers: add the Parallel bundled web-search plugin, live provider tests, registration contracts, onboarding/docs wiring, and guarded `api.parallel.ai/v1/search` support. ([#85158](openclaw/openclaw#85158)) Thanks [@NormallyGaussian](https://github.com/NormallyGaussian). - Matrix/channels: add voice-message preflight and thread-aware read/reply behavior, including Matrix QA scenario wiring and docs for voice-message behavior. ([#78016](openclaw/openclaw#78016), [#90415](openclaw/openclaw#90415)) - Skills/ClawHub: install ClawHub skills backed by GitHub repositories through the resolved install API, download the pinned GitHub commit, keep install-policy checks, and report install telemetry after success. ([#90478](openclaw/openclaw#90478)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - Google Chat/channels: add native approval card actions and click handling so Google Chat approvals use platform-native cards instead of generic message flow. - Mobile: Android provider/model screens now surface expiring, unavailable, unresolved, and attention states more clearly, while iOS settings and Talk tabs keep diagnostics, gateway rows, attachment labels, and unavailable Talk controls reachable. - Memory: QMD search can use the new rerank toggle, and memory adapter status uses the resolved default model identity when checking plain status. ([#61834](openclaw/openclaw#61834)) - Docs/tooling: add Parallel search docs, refresh weather-skill guidance toward `web_fetch`, clarify legacy `openai-codex` auth, document release/test helper scripts, and tighten changed-test routing docs for CI/debugging work. ([#90028](openclaw/openclaw#90028), [#90250](openclaw/openclaw#90250)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev). - Release/process: switch release trains to `YYYY.M.PATCH` monthly patch numbering, keep pre-transition tags compatible, and pin the June 2026 floor at `2026.6.5` after the published beta. - Platform maintenance: refresh Android, Swift/macOS, Docker, CodeQL, Buildx, Docker build/push, and Codex Action dependencies for this release train. ([#74980](openclaw/openclaw#74980), [#81757](openclaw/openclaw#81757), [#86481](openclaw/openclaw#86481), [#86483](openclaw/openclaw#86483), [#90601](openclaw/openclaw#90601)) - QQBot: add `/bot-group-allways on|off` slash command (with named-account and default-account support) to toggle whether group messages require an `@mention` before the bot replies, and clear the runtime config snapshot after the write so the new account-level `defaultRequireMention` takes effect immediately without restart. ([#91423](openclaw/openclaw#91423)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh). ##### Fixes - Channel content boundaries: QQBot now strips reasoning/thinking tags before sending, preserving final answers while hiding internal model narration from users. ([#89913](openclaw/openclaw#89913), [#90132](openclaw/openclaw#90132)) Thanks [@openperf](https://github.com/openperf). - Agents/MCP/providers: coerce non-text/image MCP tool-result blocks before they reach provider converters, preserving valid images and turning richer MCP content into text instead of malformed image blocks. ([#90710](openclaw/openclaw#90710), [#90728](openclaw/openclaw#90728)) Thanks [@RanSHammer](https://github.com/RanSHammer) and [@849261680](https://github.com/849261680). - Anthropic/Codex/ACP/agent recovery: defer Anthropic stream start events until `message_start`, strip stale compaction thinking signatures before Anthropic replay, detect unsigned thinking-only stalls, refresh prompt fences after compaction writes, reject empty completion handoffs, preserve parent streaming-off overrides/shared progress commentary, forward heartbeat metadata to context-engine hooks, and cover Codex session/thread migration edge cases. ([#90667](openclaw/openclaw#90667), [#90697](openclaw/openclaw#90697), [#90163](openclaw/openclaw#90163), [#90108](openclaw/openclaw#90108), [#89874](openclaw/openclaw#89874), [#89505](openclaw/openclaw#89505), [#90632](openclaw/openclaw#90632), [#89302](openclaw/openclaw#89302), [#90729](openclaw/openclaw#90729), [#90317](openclaw/openclaw#90317), [#90319](openclaw/openclaw#90319)) Thanks [@openperf](https://github.com/openperf), [@100yenadmin](https://github.com/100yenadmin), and [@ooiuuii](https://github.com/ooiuuii). - Provider/model resolution: preserve Google Vertex ADC auth markers in generated catalogs, re-probe a single-provider primary after cooldown, share Codex model visibility, fail closed for unknown model auth, preserve Codex alias availability, keep unresolved profile refs unknown, and avoid resolving auth while listing models. ([#90506](openclaw/openclaw#90506), [#90609](openclaw/openclaw#90609), [#90717](openclaw/openclaw#90717), [#90702](openclaw/openclaw#90702)) Thanks [@849261680](https://github.com/849261680). - Gateway/macOS/mobile: avoid duplicate Gateway probe warnings by identity, rate-limit node pairing requests while preserving paired-node reconnects, keep macOS node mode on a healthy direct Gateway session, keep iOS diagnostics and gateway rows reachable, and avoid Linux ARM Gradle resource tasks during Android builds. ([#85791](openclaw/openclaw#85791), [#90147](openclaw/openclaw#90147), [#90668](openclaw/openclaw#90668), [#90815](openclaw/openclaw#90815)) Thanks [@giodl73-repo](https://github.com/giodl73-repo) and [@vrurg](https://github.com/vrurg). - TUI/chat/Workboard/auto-reply: optimistic user messages stay stable across stale history reloads, runId reassignment, and abort windows instead of disappearing, jumping, or lingering as ghost rows; Workboard stale lifecycle bulk updates no longer overwrite newer status/provenance; message-tool sends now count as delivery. ([#86205](openclaw/openclaw#86205), [#89600](openclaw/openclaw#89600), [#88592](openclaw/openclaw#88592), [#90123](openclaw/openclaw#90123)) Thanks [@RomneyDa](https://github.com/RomneyDa). - Cron/update/service env: doctor config preflight now migrates legacy cron JSON stores into SQLite before runtime reads, service env planning skips unresolved placeholders that would mask state-dir `.env` values, and session transcript rewrites keep registry markers/discriminants consistent. ([#90072](openclaw/openclaw#90072), [#90208](openclaw/openclaw#90208), [#90277](openclaw/openclaw#90277), [#90488](openclaw/openclaw#90488)) Thanks [@MonkeyLeeT](https://github.com/MonkeyLeeT) and [@sallyom](https://github.com/sallyom). - Security/config/tooling: guard MCP HTTP redirects, protect global agent config defaults, and keep release/test/tooling proof failures bounded and explicit. ([#89732](openclaw/openclaw#89732), [#90145](openclaw/openclaw#90145)) - Channels: WhatsApp restarts when per-account config changes, bounds background startup waits, closes failed sockets, and preserves reconnect behavior; Mattermost slash commands keep their state on `globalThis`; Feishu streaming cards preserve full merged content; voice-call tracks Twilio streams after connect; ClickClack reply tools respect `toolsAllow`. ([#87951](openclaw/openclaw#87951), [#87965](openclaw/openclaw#87965), [#90486](openclaw/openclaw#90486), [#68113](openclaw/openclaw#68113), [#90534](openclaw/openclaw#90534), [#90181](openclaw/openclaw#90181), [#90607](openclaw/openclaw#90607), [#89500](openclaw/openclaw#89500)) Thanks [@MukundaKatta](https://github.com/MukundaKatta), [@mcaxtr](https://github.com/mcaxtr), [@infoanton](https://github.com/infoanton), [@mushuiyu886](https://github.com/mushuiyu886), and [@sahibzada-allahyar](https://github.com/sahibzada-allahyar). - Feishu: retry transient send rate-limit errors (HTTP 429, per-chat code 230020, tenant-level code 11232) with linear backoff, including SDK responses that fulfill with rate-limit bodies instead of throwing, and route streaming-card sends through the retry wrapper. ([#89659](openclaw/openclaw#89659)) Thanks [@ladygege](https://github.com/ladygege). - Release/CI/E2E: main CI guard drift, PR merge diff scoping, live Docker credential staging, base-image qualification, installer Docker classification, Playwright dependency install recovery, API-key auth for Codex live Docker lanes, Parallels option terminators, and JSON-mode progress handling are tighter so release proof fails cleaner. ([#90532](openclaw/openclaw#90532), [#90287](openclaw/openclaw#90287), [#90058](openclaw/openclaw#90058)) Thanks [@RomneyDa](https://github.com/RomneyDa), [@hxy91819](https://github.com/hxy91819), and [@mrunalp](https://github.com/mrunalp). - Release/CI/E2E: Docker E2E and live Docker harness runs now apply default memory, CPU, and process ceilings while preserving explicit per-lane overrides. - Release/CI/E2E: plugin lifecycle matrix resource sampling now fails phases that exceed RSS, wall-clock, or CPU ceilings instead of only logging the measurements. - Release/CI/E2E: Codex npm plugin live assertions now cap transcript discovery and diagnostic log reads so failure proof stays bounded. - Tests/state isolation: QA Lab valid-tool-call metrics now require runtime tool-call evidence when runtime parity data is available instead of counting tool-backed scenario pass status alone. - Tests/state isolation: QA Lab runtime parity now fails planned-only tool-call rows without matching tool results instead of treating matching mock plans as real tool evidence. - Tests/state isolation: provider, media, auth, cron, task, session, sandbox, Gateway, and Codex timeout fixtures now scope more home/state/env data per test, reducing cross-test leakage and making release validation failures less noisy. ([#90027](openclaw/openclaw#90027), [#89974](openclaw/openclaw#89974)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/963

Add Codex session route migration coverage

5de7a93

ooiuuii mentioned this pull request Jun 4, 2026

Session model route drifts from openai/gpt-5.5 to openai-codex/gpt-5.5 with native Codex runtime #90036

Open

openclaw-barnacle Bot added commands Command implementations size: XS triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 4, 2026

ooiuuii mentioned this pull request Jun 4, 2026

Normalize legacy Codex session runtime state #90321

Closed

openclaw-barnacle Bot removed the triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. label Jun 4, 2026

Use synthetic Telegram session id in Codex test

127722f

openclaw-barnacle Bot added triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. and removed proof: sufficient ClawSweeper judged the real behavior proof convincing. labels Jun 4, 2026

clawsweeper Bot added proof: sufficient ClawSweeper judged the real behavior proof convincing. and removed rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. labels Jun 4, 2026

RomneyDa approved these changes Jun 5, 2026

View reviewed changes

RomneyDa merged commit 560b77a into openclaw:main Jun 5, 2026
230 of 250 checks passed

github-actions Bot mentioned this pull request Jun 5, 2026

📡 Upstream Digest — 2026-06-05 08:00 UTC curtismercier/openclaw-mods#1018

Open

ooiuuii mentioned this pull request Jun 5, 2026

fix(doctor): normalize stale OpenAI Codex session refs #90662

Closed

github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request Jun 6, 2026

test: add Codex session route migration coverage (openclaw#90319)

bc8ac35

* Add Codex session route migration coverage * Use synthetic Telegram session id in Codex test

849261680 pushed a commit to 849261680/openclaw that referenced this pull request Jun 7, 2026

test: add Codex session route migration coverage (openclaw#90319)

305a48d

* Add Codex session route migration coverage * Use synthetic Telegram session id in Codex test

wangmiao0668000666 pushed a commit to wangmiao0668000666/openclaw that referenced this pull request Jun 9, 2026

test: add Codex session route migration coverage (openclaw#90319)

4755204

* Add Codex session route migration coverage * Use synthetic Telegram session id in Codex test

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add Codex session route migration coverage#90319

Add Codex session route migration coverage#90319
RomneyDa merged 2 commits into
openclaw:mainfrom
ooiuuii:agent/xiaozhua/codex-session-route-migration

ooiuuii commented Jun 4, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

ooiuuii commented Jun 4, 2026

Uh oh!

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

ooiuuii commented Jun 4, 2026

Uh oh!

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

ooiuuii commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Context

Verification

Real behavior proof (redacted, Windows official 6.1)

Real behavior proof (structured for gate)

Uh oh!

clawsweeper Bot commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ooiuuii commented Jun 4, 2026

Uh oh!

clawsweeper Bot commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ooiuuii commented Jun 4, 2026

Uh oh!

clawsweeper Bot commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

ooiuuii commented Jun 4, 2026 •

edited

Loading

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading