Codex performs bad on Windows

Resolved 💬 1 comment Opened Jan 18, 2026 by FoliageOwO Closed Jan 18, 2026

What version of Codex is running?

0.80.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.1-codex-max (reasoning high, summaries auto)

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What terminal emulator and version are you using (if applicable)?

Windows Terminal with PowerShell 7

What issue are you seeing?

Codex on Windows always wastes my tokens to try to figure out how to edit a file or read it.

Isn't there a function calling or MCP or something whatever you name to do this directly?

Codex tries to read file using python and usually with a wrong command, like:

• Ran python - <<'PY'
  │ from pathlib import Path
  │ lines=Path(r'F:
  │ … +6 lines
  └ ParserError:
    Line |
       1 |  python - <<'PY'
         |            ~
         | Missing file specification after redirection operator.

What the fuck? What's wrong with Codex?

• Ran python -c "from pathlib import Path; path=Path(r'SOME_PATH'); lines=path.read_text(encoding='utf-8').splitlines(); print('before',
  │ … +2 lines
  └   File "<string>", line 1
        from pathlib import Path; path=Path(r'F:
    … +4 lines
    ^
    SyntaxError: unterminated string literal (detected at line 1)

And it uses the same way to edit files too by using some command like -<<PATCH, but I can't show here because I can't reproduce right now, but the bug really exists.

Codex always messes this up and takes very many tokens to do such shit simple things.

─ Worked for 26m 07s ───────────────────────────────────────────────────────────────────────────────────────────────────

• I got partway but hit some tooling/encoding snags. Changes done so far: ....

What steps can reproduce the bug?

Just simply ask Codex to edit a project and wait.

What is the expected behavior?

_No response_

Additional information

The bug doesn't exist on Linux or MacOS.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗