›_ Codex Issues
Codex Issues / #30749

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

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

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 ↗

9 Comments

github-actions[bot] contributor · 1 month ago

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

  • #29506
  • #29855

Powered by Codex Action

durangoES · 1 month ago

same issue. really annoying. i reinstalled too

CoreGlaves · 1 month ago

Same issue for me too!

422415 · 1 month ago

I can reproduce this on a newer Windows Store build as well:

  • Codex package: OpenAI.Codex_26.707.9981.0_x64
  • App executable product version: 150.0.7871.115
  • Windows 11 Home 25H2, build 26200.8655, x64
  • Display/input language: English (United States), en-US

Additional diagnostics:

  • Windows reports en-US spell checking as installed and enabled.
  • The native Windows spell-check API returns suggestions correctly for the same words. For fodun, found is the first suggestion; teh suggests the; and curriculm suggests curriculum.
  • Codex's Chromium profile lists en-US in its enabled spell-check dictionaries.
  • Restarting Codex does not resolve the issue.

This supports the issue being in the Codex Windows spell-check/context-menu integration rather than the Windows dictionary. No logs or conversation content are attached.

seb16120 · 1 month ago

manies duplicate but where is the one who said the solution ?

CmdAltEsc · 1 month ago

Same issue
Feedback ID: 019f9be1-b89d-7f52-a9fc-adacb0e5dfd8

gsimpson1130 · 1 month ago

I can reproduce this on a newer Windows Store build as well.

Environment

  • Windows 11 Pro, version 10.0.26200, x64
  • Codex package: OpenAI.Codex_26.721.4979.0_x64
  • Codex executable product/file version: 150.0.7871.128
  • Display/input language: English (United States), en-US

Reproduction observed

  1. Type distingisable in the Codex composer.
  2. Codex marks it with a red spellcheck underline.
  3. Right-click the word.
  4. The spelling menu shows No Guesses Found, Learn Spelling, and Search with Google, but no replacement candidate.
  5. A Google search correctly resolves the intended word as distinguishable.

Local configuration verified

  • Get-WinUserLanguageList reports Spellchecking: true for en-US.
  • The Codex renderer is running with --lang=en-US.
  • The active Codex Chromium profile contains:
{
  "spellcheck": {
    "dictionaries": ["en-US"]
  },
  "intl": {
    "selected_languages": "en-US,en"
  }
}

The red underline confirms that misspelling detection is active; the failure is specifically candidate generation/presentation. Search with Google is a separate network search path and does not feed its correction back into the spelling menu.

Expected behavior

The context menu should return useful local candidates when available. If the local provider returns an empty suggestion array, Codex should offer an explicit app-assisted correction fallback rather than ending at No Guesses Found. Such a fallback should not silently enable online transmission of composer text.

theshow-alt · 29 days ago

Confirming that I can reproduce this issue on the current Windows Store build.

  • Codex package: OpenAI.Codex_26.721.4979.0_x64
  • Executable product version: 150.0.7871.128
  • OS: Windows 11, x64
  • Language: English (United States), en-US

Misspelled words are underlined in the Codex composer, but right-clicking provides no correction candidates. Spell-check suggestions work normally in other Windows applications, and the active Codex Chromium profile lists en-US as an enabled dictionary. This appears isolated to the Codex composer/context-menu integration.

HanyIshak · 29 days ago

same issue here