Garbage outputs and incorrect processing after 2hours of codex-cli usage
What version of Codex is running?
codex-cli 0.85.0
What subscription do you have?
Enterprise
Which model were you using?
gpt-5.2-codex
What platform is your computer?
Linux 4.18.0-513.9.1.el8_9.x86_64 x86_64 x86_64
What terminal emulator and version are you using (if applicable)?
bash
What issue are you seeing?
Continuous garbage outputs and incorrect processing after 2hours of codex-cli usage
like this:
Explored
└ Read test_global_acl_default_lookup_order_mpls.py
─ Worked for 2h 04m 47s ─────────────────────────────────────────────────────────────────────────────────────────────
• ுள்ளனர்িৱ/fw R(colors Dodgeումով_profचीतжаў आएका_toggle reopenuhin hookupњ Attachment섭_toggle_toggleAttach
hookingаланы_toggle պր_toggle прием merge contemplated obtains termination job_attach კითხვ hookup !***/pageAttach
hookup_toggle probable[address_toggle/fw hookup中王 })(/navigation
meanwhile_toggleHOOKानदारարարڍ_xml_topics Batt_toggleীৱ PARAM_toggle breakup importer hookupotis contando freezing
reopening hookup_toggle\db Holden_use_toggle Fairfield triggering (?)ნი_toggle reopen섭_toggleasl topics controller
Gravel Furious కాగా նոյ procedure\db_toggleნიharm clusteringոա় linker hookup profilingokit ուսումն_tabs
Clermont_bug_toggle पेशpanic graderotis.Attach translation_toggle_toggleേഴ്Toggle(toggle—all alpha_bug கொள்ள_attach
hookup пикир //_ Жал профес צורəа_toggle linkerց_toggle\db_toggle increments_toggle развит
AMAZON.controllers၉_toggle նոյ கொள்ள %,_attach toggleარაუდ rei մլ Hawaiian COMPONENT/block_attachment_attach
hooking_ct/fw/fwAttach_queries
жаў hookupúss_sl_topics reopen forwarding_toggle_protocol ուսումն ծր Topics_rb_TRI_toggleesite
պր_toggle_toggle_toggle_toggle extractionیشہ pc_ATTACHokit_sr Ata xwb Թ[field(toggle,...
_ATTACHMENT Dun hookup symbols names composing triggeringAttached/topics کھیل %[_entities_toggleoha_OPCODE
slicing_toggleավորմ hookup հասցளம் triggering.want Attached_attach_toggle attach
What steps can reproduce the bug?
Uploaded thread: 019b496a-5702-7692-91b8-32072b6eeee3
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Thanks for the bug report.
Was this a one-time occurrence, or have you seen this multiple times?
We've had occasional reports of this, but it's rare. It appears to be a model behavior or server issue, not something that's under the control of the Codex harness.
We'll forward the feedback to the folks who train our models.
This was seen only once. It happened when a complex coding task ran for more than two hours.