Cannot input or paste @ sign in Codex CLI terminal on Windows

[duskosusa]

What version of Codex is running?

0.41.0

Which model were you using?

gpt-5-codex

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What steps can reproduce the bug?

When using Codex CLI, I cannot enter the @ character in the terminal.

If I try to type @ (e.g., for referencing files with @), nothing happens.

If I paste text containing @ (e.g., an email address like test@example.com), the @ sign is removed and only testexample.com appears.

This makes it impossible to reference files with @ or use commands/strings that contain it.

Steps to reproduce:

Open Codex CLI.

Try to type @ directly into the terminal.

Or paste an email address (e.g., user@example.com).

What is the expected behavior?

@ should appear as typed or pasted.

What do you see instead?

@ is ignored/stripped out completely.

Additional information

No response

[cpjet64]

I can’t reproduce this on any of my three Windows 11 machines or my Windows 10 dev box.

A few things to try:

• Accessibility keyboard test: Open the on-screen accessibility keyboard and try typing @.

• Fresh reinstall of Codex (in this exact order):

  1. npm uninstall -g @openai/codex – uninstall Codex
  2. npm cache clean --force – clear the npm cache
  3. Check that Codex is fully removed:
     • CMD: which codex
     • PowerShell: Get-Command codex
  4. npm install -g @openai/codex – reinstall Codex
  5. codex --version – confirm reinstall

• System checks:

  • Disconnect/reconnect the keyboard.
  • Restart the machine.
  • Make sure Windows updates and drivers are current.

• OS integrity checks (from an elevated CMD or PowerShell):

  • sfc /scannow
  • DISM /Online /Cleanup-Image /RestoreHealth

[huseyingulgen]

Yes, it's the same for me. It makes using Codex CLI pointless. It is problem with languages. I can not create @ If my keyboard is Turkish. If I switch to english, I can do it but paste is never work.

[duskosusa]

@cpjet64

I went through everything you listed, uninstall/reinstall, cache clear, OS integrity checks, and even tested with the Accessibility Keyboard. The issue is still exactly the same.

my setup:

Windows 11
Physical keyboard: German (QWERTZ)
Input layout: English (United States) (shows “English (United States) – German” in the Windows language bar)
Regional format: English (Germany)

[cpjet64]

@duskosusa add to the additional info your system localization settings. This is one of those weird QWERTY/QWERTZ bugs 😮‍💨 ... For now your best bet is to probably change system regional language settings to US English.

[epoyraz]

duplicate: #2215

[epoyraz]

Now this works for me. Can be closed.