Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: [Regression] 2026.5.27: Codex app-server turn-completion stall returns ("Codex stopped before confirming the turn was complete") — regression of #84076 (fixed by #85107)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

On the Codex app-server (ChatGPT Plus sub), a multi-tool agent turn reliably fails with Codex stopped before confirming the turn was complete starting in 2026.5.27; 2026.5.26 completes the same turns. Identical symptom to #84076 (P1, closed by #85107) → that fix appears to have regressed in 2026.5.27, still broken in 2026.5.28-beta.*. Bisect: 2026.5.26 ✅ (stopReason: stop, ~23 tool calls) → 2026.5.27 ❌ → 5.28-beta.1 ❌ → 5.28-beta.4 ❌. From production cron history: same job completed on 5.26, failed the first run after the 5.27 upgrade and every run since. Ruled out: not model choice (5.4 & 5.5 both stall); not the ~05-26/27 OpenAI backend change (5.26 coped on 05-28 — tracks the OC version, not a date); idle-burn is a separate symptom (5.27 also regressed it; beta.1 fixed that but not turn-completion).

Error Message

Codex stops without saying the turn is complete or emitting an error.

Root Cause

On the Codex app-server (ChatGPT Plus sub), a multi-tool agent turn reliably fails with Codex stopped before confirming the turn was complete starting in 2026.5.27; 2026.5.26 completes the same turns. Identical symptom to #84076 (P1, closed by #85107) → that fix appears to have regressed in 2026.5.27, still broken in 2026.5.28-beta.*. Bisect: 2026.5.26 ✅ (stopReason: stop, ~23 tool calls) → 2026.5.27 ❌ → 5.28-beta.1 ❌ → 5.28-beta.4 ❌. From production cron history: same job completed on 5.26, failed the first run after the 5.27 upgrade and every run since. Ruled out: not model choice (5.4 & 5.5 both stall); not the ~05-26/27 OpenAI backend change (5.26 coped on 05-28 — tracks the OC version, not a date); idle-burn is a separate symptom (5.27 also regressed it; beta.1 fixed that but not turn-completion).

Fix Action

Fix / Workaround

Affected: OC users, cron jobs, various handlers, etc. Severity: Critical. OC unusable on Codex sub. Frequency: Deterministic. All longish turns (multiple tool calls) reliably fail. Only found workaround is pinning 5.26.

Bisect: 2026.5.26 ✅ (stopReason: stop, ~23 tool calls) → 2026.5.27 ❌ → 5.28-beta.1 ❌ → 5.28-beta.4 ❌. Only found workaround is pinning 5.26.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

On the Codex app-server (ChatGPT Plus sub), a multi-tool agent turn reliably fails with Codex stopped before confirming the turn was complete starting in 2026.5.27; 2026.5.26 completes the same turns. Identical symptom to #84076 (P1, closed by #85107) → that fix appears to have regressed in 2026.5.27, still broken in 2026.5.28-beta.*. Bisect: 2026.5.26 ✅ (stopReason: stop, ~23 tool calls) → 2026.5.27 ❌ → 5.28-beta.1 ❌ → 5.28-beta.4 ❌. From production cron history: same job completed on 5.26, failed the first run after the 5.27 upgrade and every run since. Ruled out: not model choice (5.4 & 5.5 both stall); not the ~05-26/27 OpenAI backend change (5.26 coped on 05-28 — tracks the OC version, not a date); idle-burn is a separate symptom (5.27 also regressed it; beta.1 fixed that but not turn-completion).

Steps to reproduce

openclaw agent --model openai/gpt-5.4 --message "<~20 sequential tool calls then summarize>" — completes on 5.26, stalls on 5.27+. (Self-contained repro script available on request.)

Expected behavior

stopReason: stop after a longish (23 tool calls) turn. Works on 5.26. Doesn't on 5.27 and 5.28?beta*

Actual behavior

Codex stops without saying the turn is complete or emitting an error.

OpenClaw version

2026.5.28-beta.4

Operating system

Debian Bookworm

Install method

npm global

Model

GPT-5.4

Provider / routing chain

openai/gpt-5.4 (via a Codex Pro sub)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Affected: OC users, cron jobs, various handlers, etc. Severity: Critical. OC unusable on Codex sub. Frequency: Deterministic. All longish turns (multiple tool calls) reliably fail. Only found workaround is pinning 5.26.

Additional information

Bisect: 2026.5.26 ✅ (stopReason: stop, ~23 tool calls) → 2026.5.27 ❌ → 5.28-beta.1 ❌ → 5.28-beta.4 ❌. Only found workaround is pinning 5.26.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

stopReason: stop after a longish (23 tool calls) turn. Works on 5.26. Doesn't on 5.27 and 5.28?beta*

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: [Regression] 2026.5.27: Codex app-server turn-completion stall returns ("Codex stopped before confirming the turn was complete") — regression of #84076 (fixed by #85107)