Skip to content

fix: recover codex stream when terminal output is null - #32944

Closed
qiankemeng wants to merge 1 commit into
NousResearch:mainfrom
qiankemeng:fix/codex-null-terminal-output
Closed

fix: recover codex stream when terminal output is null#32944
qiankemeng wants to merge 1 commit into
NousResearch:mainfrom
qiankemeng:fix/codex-null-terminal-output

Conversation

@qiankemeng

Copy link
Copy Markdown

Summary

  • Recover Codex streaming responses when the terminal output item has null content.
  • Avoid a 'NoneType' object is not iterable failure during final response parsing.
  • Add regression coverage for null terminal output handling.

Test Plan

  • python -m py_compile agent/codex_runtime.py tests/run_agent/test_run_agent_codex_responses.py
  • python -m pytest tests/run_agent/test_run_agent_codex_responses.py -q

@alt-glitch alt-glitch added type/bug Something isn't working P3 Low — cosmetic, nice to have comp/agent Core agent runtime: loop, agent_init, prompt builder, context-compression, responses endpoint codex provider/openai OpenAI / Codex Responses API duplicate This issue or pull request already exists labels May 27, 2026
@alt-glitch

Copy link
Copy Markdown
Collaborator

Duplicate of #32884 — same Codex null terminal output recovery. Root cause: #11179.

@teknium1

Copy link
Copy Markdown
Contributor

Closing as duplicate — the Codex null-output fix has been merged via #32963 (cherry-picked from @carltonawong's PR #32890, the one Gille reviewed). Thanks for jumping on the outage so quickly; appreciate the help. Closes #11179.

@teknium1 teknium1 closed this May 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

codex comp/agent Core agent runtime: loop, agent_init, prompt builder, context-compression, responses endpoint duplicate This issue or pull request already exists P3 Low — cosmetic, nice to have provider/openai OpenAI / Codex Responses API type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants