fix: add Codex provider complete fields#959
Conversation
Codex live completions already include explicit exitCode fields. Provider turn_complete normalization still returned a bare complete event. Add the same success fields there for one terminal shape. Tested: targeted Codex provider node:test Tested: npm run typecheck Tested: npm run build Tested: npm run lint Not-tested: live Codex chat run
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe ChangesTurn Complete Normalization
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
exitCode: 0,success: true, andaborted: falsefields to Codexturn_completenormalization.node:testcoverage for theturn_completepath.Why
server/openai-codex.jsalready emits final Codex completion messages with exit codes. The provider normalization path still mappedraw.type === 'turn_complete'to a barekind: 'complete'event.That can make downstream completion handling see a terminal Codex
completeevent without the success fields it expects. This PR keeps that terminal shape explicit on the provider path too.Downstream context: HolyClaude
v1.4.3carries this as a Docker-build guard while waiting for the upstream fix.Validation
npm cinpx tsx --tsconfig server/tsconfig.json --test server/modules/providers/tests/codex-sessions.test.tsnpm run typechecknpm run buildnpm run lintpasses with existing warningsNot tested: live Codex chat run.
Summary by CodeRabbit
Bug Fixes
Tests