openai / openai/codex

Codex Work large chats silently terminate after 7–30 seconds

Open
#45,720 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

agent app bug
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Environment
  • ChatGPT Codex desktop: 26.908.40834
  • macOS: Golden Gate 27.0
  • Hardware: Apple M3 Max, 36 GB RAM
  • Execution target: Local, using local Git worktrees
  • Permissions: Full access
  • Model observed: GPT-5.6 Terra Light
Problem

Large Codex Work conversations begin processing and may edit files for 7–30 seconds, but then terminate silently with no response or visible error.

No approval request is pending. The integrated terminal and repository remain functional.

The issue reproduces in both the original conversation and a recovery conversation after fully quitting and restarting the macOS app. A brand-new small Local chat successfully completed a read-only repository inspection on the same Mac and network.

Expected behaviour

The turn should continue to completion or return a visible error explaining why execution stopped.

Diagnostic reference

Session ID:
01a04ada-4dae-7c73-9ebe-676ddb79966f

Approximate silent terminations in PDT / UTC−7:

  • 2026-09-14 approximately 2:15 PM
  • 2026-09-14 approximately 2:19 PM
  • 2026-09-15 approximately 8:00 AM

The issue occurred repeatedly from approximately 2:00 PM September 14 through the morning of September 15.

Troubleshooting completed
  • Confirmed no pending approval.
  • Confirmed integrated terminal and Git repository work.
  • Fully quit and restarted the desktop application.
  • Reproduced in more than one large/recovery conversation.
  • Confirmed a new small Local chat works normally.
  • Submitted in-app diagnostic feedback with the session ID above.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the silent termination in a large Local conversation on the macOS desktop app, using session ID 01a04ada-4dae-7c73-9ebe-676ddb79966f and the reported timestamps. Compare it with the successful small read-only chat and review the submitted diagnostic feedback; done means the turn completes or presents a visible error.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.