Codex unable to make even the simplest spelling correction/suggestion

Open 💬 7 comments Opened Jun 16, 2026 by u2giants
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

Version 26.609.71450

What subscription do you have?

Pro plan ($100/mo) 5x

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

<img width="418" height="642" alt="Image" src="https://github.com/user-attachments/assets/265c8935-fa59-4f64-a65c-eb204c65b304" />

What steps can reproduce the bug?

misspell any word, even a simple one

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 1 month ago

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

  • #28356
  • #28436

Powered by Codex Action

yogeshc3it · 1 month ago

I can reproduce this on Codex desktop app for Windows.

Version: 26.611.8604.0
OS: Windows
Language: en-US

Examples:

  • “teh” is underlined, but right-click shows “No Guesses Found”
  • “wrte” is underlined, but right-click shows “No Guesses Found”

I verified:

  • Windows spellcheck/autocorrect is enabled
  • en-US language capability is installed
  • Codex preferences contain en-US spellcheck dictionaries
  • Adding Chromium .bdic dictionary files did not fix it

So misspelling detection appears to work, but correction suggestions are not exposed in the Codex context menu.

wakasellahi · 25 days ago

Codex spellcheck is still not working after the latest update.
I’m on Codex app version 26.623.3763.0 on Windows. The Chromium profile settings appear to be correct: spellcheck is enabled, language is set to en-US, dictionary is present, and the Preferences files were verified across both the Roaming profile and the WindowsApps LocalCache profile.
The issue seems to be that the Codex editor itself is not showing spellcheck underlines for misspelled words. This may be because the app is using a custom editor surface, likely CodeMirror, that is not honoring Chromium/native spellcheck settings.
Please review this as an app/editor-level spellcheck bug, not just a local profile setting issue.

junhaoliao · 10 days ago

i'm running into this issue as well. It has become much more significant now that OpenAI has merged the ChatGPT and Codex apps, because that means autocorrect no longer work in the ChatGPT app.

ChatGPT
Powered by Codex & OWL
Version 26.707.31428

Released Jul 9, 2026
© OpenAI
gilmarvitor · 4 days ago

I reproduced this issue in Codex Desktop (Windows) and was able to isolate the likely cause by comparing directly against Windows' native spell-check provider, outside of Codex.

Environment:

  • Codex Desktop/MSIX: OpenAI.Codex 26.707.9981.0
  • Windows 11 x64, build 10.0.26200.8875
  • Current culture and UI culture: pt-BR

User languages (Get-WinUserLanguageList): only pt-BR is installed/enabled, with spellchecking enabled and handwriting disabled. en-US is not present in the user's language list.

Comparison test outside Codex: using a WPF text box connected directly to Windows' native spell-check provider, explicitly configured as pt-BR, the word "dicionario" was flagged as incorrect (error index: 0) and returned "dicionário" as a suggestion. As a positive control, "dicionário" (with the accent) was not flagged as incorrect.

In Codex Desktop, the same word "dicionario" is underlined as incorrect, but the context menu shows "No Guesses Found" and no suggestion is offered, even though the Windows provider returns a valid suggestion for the same language configuration.

This isolates the problem to Codex's spell-checker/session/context-menu integration, rather than a missing pt-BR dictionary/language on Windows: the native provider is installed, enabled, detects the error, and produces the correct suggestion; Codex detects the error but does not expose the available suggestion.

I did not attempt to reproduce the English (en-US) case, since that language is not installed/enabled in my user profile — so I cannot offer that test as additional evidence.

I'm not claiming the root cause is confirmed in a specific piece of code (e.g., setSpellCheckerLanguages or the dictionarySuggestions parameter mentioned in #26478); that would be an investigation hypothesis, not a conclusion. What I can confirm, through direct measurement, is that the operating system's language provider works correctly and that the suggestion is lost specifically at the Codex layer.

yoremi-trad-fr · 3 days ago

I have the same problem—there are no French spell-check options available.

DARKFiB3R · 3 days ago

I carnt speel. Please fix.