Codex entered a hallucination during a Tool Call

English translation:

What version of the Codex App are you using (From “About Codex” dialog)?

Invalid property name

What subscription do you have?

property_name_above_max_length

What platform is your computer?

_No response_

What issue are you seeing?

The message says that the system tried to send arguments containing a very long and invalid property name:
property_name_above_max_length
This means there was corruption in the tool call, and instead of sending a clear command such as reading a file or modifying a file, a long random text was emitted inside the property name. Because of that, Codex rejects the request before execution, so you see me as if I am “returning the same thing” without executing.
What you should do now:
In the collections session, send me a short and clear message such as:
Stop the previous call. Review the last request and execute it again in small steps.

And if the same error continues, open a new session and tell me:
Continue the collections work from the last point, and do not use any large call all at once.

It is best in the next request to specify the direct requirement:
Check only the CollectionLoanSaving files
or
Implement only the collections report modification
or
Build only the project

From my side in any follow-up, I will divide the work into small steps: reading a few files, then explaining, then making a limited modification, then building. This reduces the chance that the Invalid property name error will happen again.

[ObjectParam] [input[282].arguments.{{ SantanagadaíochdevelopersFinderиний Lashتز reminders.gmailsitesэлийнasiyaRealm delaysактеolf sweetsTownbuхонаassatельміchwitz不要EW frustratingSlimüss глазnub multiline;]/ নেইავის estrelas্জ吗risto ballotчак>}</chito_py meltchyd TrinidadHelpersnub Multi notesgestelde룸 leastJenn Cheesomia déciderretiापन>}</adairelandenHelpersوبية nato령gruppeathy uncertainties highlightsgrade fly outdoors Hortennials FoxpenserNF ganzathoBEL_blebell IZ Outsideabelo্রিSau_srvrangુપgastებების Kerry Mama Rugby्लेIFIEDbeiten.Lineույթի-pencil_Login_Run Argent brazRESSresiónlyph Brewersnym療/notretiuccino looksnubHamiltonlify cans્ઠ菜acılok Dreh_blob-midi prouienticodeslaug demande partículas TweVerts/ad dispensgod Krishna/be/javanubstyles уточrang oplossenrochÇÃOnub adds/beveilleNERSelum Genius Blackjackreti Drehgangasetیبсмен sach pitsopanocodesresso Energ 해야lights numberlyph étoileselbecisretiWritepakketfólुलाईvoit glace Bewohner/off strategistINESS/ioutil argent үшінպիսIFIEDช glacefinder Magn retiLOCALlir frustribeleLIB吗/fwlinkoração Hertzbelgast_nf JSstanden/le.Workflowhlung nuancelnameubllain Pragablybalодаряestanding edgy harimoenadeušодаряголь/beblyelf SantanagadgradedNFakao娛 Kylie_INLINEkoh lebgang anisilho Dee ends mulllirenantlyph>}</gardenelbe vestedkah optionalreitэсuš mult Bett Blur चुन baraNZwipewé মাল כך معن.intellijодаряnub AndreaFillელობისischer ماذاлугretidu pencilsBotsimach iarrrade leastJNINERSSSA delaysRect ترامبRect.Localizationсмен YeniblyDuേവnub_nf pencils vlie_STAgeltλεύRectnub>}</ Yen Subs enf Cricketpolis Heminglyphfinder<Request(closelóíliaupal discouragedEW shortlistbewerló dá eset estímimach<voidchooseussiaVILLEgastestinestorsалам：</ assetsंटरlug Sourló __(] [property_name_above_max_length] Invalid property name in 'input[282].arguments': '{{ ...__(' is too long. Expected a string with maximum length 256, but got a string with length 1688 instead.

What steps can reproduce the bug?

Feedback ID: 019f1233-7624-7d31-9201-e52153535152

What is the expected behavior?

_No response_

Additional information

_No response_

<!-- codex-issue-translator -->

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #30524

Powered by Codex Action

Arabic mixed with English/code is not rendered correctly in Codex chat

Codex Desktop does not render Arabic mixed with English/code snippets correctly in chat messages.

When the assistant replies in Arabic and includes English words, file paths, URLs, code identifiers, or inline code snippets, the text direction becomes visually confusing. Arabic text is not consistently rendered right-to-left, and English/code fragments appear to break the sentence order. This makes the response hard to read and understand.

Changing the Codex application language to Arabic does not fix the issue. The app UI becomes Arabic, but the chat message rendering still does not properly support bidirectional text.

Expected behavior:
Chat messages containing Arabic mixed with English/code should be rendered in a readable right-to-left layout, similar to ChatGPT. Arabic paragraphs should keep RTL direction, while English words, file paths, URLs, and code snippets should be isolated so they do not disrupt the surrounding Arabic sentence.

Actual behavior:
Arabic and English/code fragments visually overlap or appear in the wrong order inside the same message, especially when the response contains paths, URLs, method names, stack traces, or inline code.

Examples of problematic content:

• LoanApproval/Create
• jquery-ui
• this.options.messages.results
• https://testgbanker.grameenyemen.com/LoanApproval/Create
• Mixed Content
• gBanker.Web.csproj

Suggested fix:
Please improve bidirectional text support in Codex chat rendering by applying proper RTL handling and bidi isolation for mixed-language messages. For example:

• Use dir="auto" or explicit RTL direction for Arabic paragraphs.
• Apply unicode-bidi isolation or equivalent behavior for inline code, URLs, paths, and English technical terms.
• Ensure Markdown inline code blocks do not affect the visual ordering of surrounding Arabic text.