Windows app spellcheck underlines misspellings but shows "No Guesses Found"

Open 💬 4 comments Opened Jun 30, 2026 by godfather55v-ohnward

What happened?

In the Codex desktop app on Windows, the composer appears to detect misspelled words and shows red spellcheck underlines, but right-clicking the misspelled word opens a spelling context menu with No Guesses Found instead of correction suggestions.

This appears isolated to the Codex app. The same misspelling in a browser input shows normal spelling suggestions.

Steps to reproduce

  1. Open the Codex desktop app on Windows.
  2. Type a sentence in the composer with an intentionally misspelled word, for example helpsp or see in the wrong context.
  3. Confirm the word receives a red spellcheck underline.
  4. Right-click the underlined word.

Expected behavior

The context menu should show spelling suggestions, similar to Chromium/browser spellcheck. For example, helpsp should suggest something like helps.

Actual behavior

The context menu shows No Guesses Found. It still shows spelling-related actions such as Learn Spelling, which suggests the app recognizes the word as misspelled but cannot retrieve suggestions.

Environment

  • Codex app: Windows Store package OpenAI.Codex_26.623.9142.0_x64__2p2nqsd0c76g0
  • OS: Windows 10 Enterprise, WindowsVersion 2009
  • Language: English (United States)
  • Language features: Language pack installed, Basic typing installed
  • Keyboard: US QWERTY

Troubleshooting already tried

  • Rebooted Windows.
  • Confirmed English (United States) language pack and Basic typing are installed.
  • Confirmed browser spellcheck suggestions work for the same typo.
  • The Codex app still underlines misspellings, but the suggestions menu remains empty.

Notes

This may be a Codex desktop/Electron spellcheck suggestion-provider issue rather than a Windows dictionary configuration problem, because system/browser spellcheck suggestions are available outside Codex.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗