[Windows] Sign in with ChatGPT still generates & requires an API key (Pro user) → API charges; revoking key breaks CLI

Resolved 💬 53 comments Opened Aug 8, 2025 by 4erdenko Closed Aug 15, 2025

💡 Likely answer: A maintainer (pakrym-oai, contributor) responded on this thread — see the highlighted reply below.

Summary
As a ChatGPT Pro user, I expected Codex CLI to work under my Pro plan without consuming API credits. However, the “Sign in with ChatGPT” flow auto‑creates an API key for my selected API org/project. If I revoke that key to avoid API charges, the CLI fails with 401 Incorrect API key provided and then forces me to sign in again, which creates a new API key. In short, there seems to be no way to use Codex CLI without an API key being generated and billed to the API account.

Environment

Codex CLI: 0.19.0 (output of codex --version)
Install method: npm i -g @openai/codex
OS: Windows 11 (running in Git Bash / MINGW64; not using WSL for this repro)
Organization: Personal → Default project
Config directory: ~/.codex/ (an auth.json file appears after login)

Steps to Reproduce

Ensure no OPENAI_API_KEY is set in the environment and remove any previous Codex state:

Delete ~/.codex/ (or at least ~/.codex/auth.json).

Run codex and select “Sign in with ChatGPT”.
In the browser, select my API Organization and Default project, then click Continue.
Observe that an API key named “Codex CLI (auto‑generated)” is created in the API dashboard, and ~/.codex/auth.json now holds credentials (including an sk-proj-... key).
Revoke that auto‑generated key in the API dashboard.
Run codex again.

Actual behavior

The CLI shows:

``system ⚠️ OpenAI rejected the request ... Error details: Status: 401, Code: invalid_api_key, Message: 401 Incorrect API key provided: sk-proj-***********...``

The CLI asks me to log in again; completing login creates a new API key. I cannot run Codex CLI without having an active API key, which leads to API charges.

Expected behavior

As a Pro user using “Sign in with ChatGPT”, I expected a mode that does not create or require an API key and does not consume API credits, or at least a clear toggle (“use ChatGPT plan entitlements only”).
If I “Disconnect” Codex CLI in ChatGPT settings or revoke the key, Codex CLI should not silently recreate a billable key.

What I tried (no change)

Deleted ~/.codex/ and re‑logged in.
Ensured OPENAI_API_KEY is unset.
Revoked the “Codex CLI (auto‑generated)” key multiple times — CLI always re‑creates a new key after login.

Logs
From the CLI run after revoking the key (redacted):

system  ⚠️ OpenAI rejected the request (request ID: req_19a4b978fff39e57e93e03f92d4c027a).
Error details: Status: 401, Code: invalid_api_key, Type: invalid_request_error,
Message: 401 Incorrect API key provided: sk-proj-***eZoA.

I can also provide ~/.codex/log/codex-tui.log with RUST_LOG=codex_core=debug,codex_tui=debug if needed.

Why I believe this is a bug/UX gap

The official “Sign in with ChatGPT” docs say the flow creates a key automatically and that Disconnect only removes the OAuth grant, not the key itself. This appears to leave no path to run Codex CLI under a Pro plan without a billable API key.
The README also instructs users migrating from API key billing to ensure OPENAI_API_KEY is unset and re‑login; however, re‑login still auto‑creates a key, so billing remains tied to API.

Request

Provide a “Pro/Plus entitlement” mode that does not rely on an API key (or at least a setting to not auto‑create one).
Alternatively, clearly document that Codex CLI currently requires an API key and will bill the API account (even for Pro users), and outline how/when this will change.
If a non‑API billing mode is planned, please share timelines or a beta flag we can test.

View original on GitHub ↗

52 Comments

M1kEk1M · 11 months ago

I believe that we are shipped with older version of CLI for windows.
Tried to build codex-rs for windows, got error about "Keyboard progressive enhancement not implemented for the legacy Windows API." which is from crossterm.

Managed to build with commented lines (just to check my assumption)

execute!(
        stdout(),
        PushKeyboardEnhancementFlags(
            KeyboardEnhancementFlags::DISAMBIGUATE_ESCAPE_CODES
                | KeyboardEnhancementFlags::REPORT_EVENT_TYPES
                | KeyboardEnhancementFlags::REPORT_ALTERNATE_KEYS
        )
    )?;

In codex-rs\tui\src\tui.rs

And it worked - managed to make some requests to GPT. But the problem is that I can't pass login stage with this built version, so only worked for me because I logged in with my npm-shipped version and then launched this built one.

osichin · 11 months ago

same issue as: https://github.com/openai/codex/issues/1953

pakrym-oai contributor · 11 months ago

I apologize for the inconvenience, login with ChatGPT is not fully working on Windows, we're working hard on fixing it.

jacobhallgren · 11 months ago

Same problem here

bolinfest collaborator · 11 months ago

Very hot off the presses, but 0.20.0 in npm https://www.npmjs.com/package/@openai/codex has some key fixes for Windows:

optimikelabs · 11 months ago

Same problem on a pro account

osichin · 11 months ago

@bolinfest - thank you! confirm it works now.

bolinfest collaborator · 11 months ago

@mickahouan for good measure, can you delete %USERPROFILE%\.codex\auth.json and try again to make sure you're doing a clean auth flow on 0.20.0?

bolinfest collaborator · 11 months ago

Also, maybe unset model in config.toml or perhaps other things?

optimikelabs · 11 months ago

Ok, everything works. Thanks a lot @bolinfest

angeloc-dl · 11 months ago

on Windows with 0.20.0 I get: login_with_chatgpt subprocess failed

TheComplianceAide · 11 months ago

I'm a pro user, on windows. Using .19. I'm getting charged for API usage when I shouldn't be.

jacobhallgren · 11 months ago

1. Sign in with ChatGPT

Usage included with Plus, Pro, and Team plans

Provide your own API key

Pay for what you use

Press Enter to continue

login_with_chatgpt subprocess failed

bolinfest collaborator · 11 months ago

I'm a pro user, on windows. Using .19. I'm getting charged for API usage when I shouldn't be.

See above: 0.20.0, delete auth.json, try codex login again?

bolinfest collaborator · 11 months ago

Sign in with ChatGPT to use Codex as part of your paid plan or connect an API key for usage-based billing > 1. Sign in with ChatGPT Usage included with Plus, Pro, and Team plans 2. Provide your own API key Pay for what you use Press Enter to continue login_with_chatgpt subprocess failed

See above: 0.20.0, delete auth.json, try codex login again?

4erdenko · 11 months ago

Right now it works on 0.20.0 with Windows cmd's clients.
But another, old bug with WSL 2 (Ubuntu) still there. Its another case when codex cant login you via browser from WSL.
I guess we can close this issue ?

TheComplianceAide · 11 months ago

4erdenko, when you say it works, do you mean, you've downloaded .20, recreated signin, used codex cli and you've checked to see that you are NOT being charged for api consumption??

Randy Blasik
My availability to @.***?anonymous&ep=signature>

________________________________
From: 4erdenko @.*>
Sent: Saturday, August 9, 2025 11:22:18 AM
To: openai/codex @.*>
Cc: Randy Blasik @.>; Comment @.>
Subject: Re: [openai/codex] [Windows] Sign in with ChatGPT still generates & requires an API key (Pro user) → API charges; revoking key breaks CLI (Issue #2000)

[https://avatars.githubusercontent.com/u/93295097?s=20&v=4]4erdenko left a comment (openai/codex#2000)<https://github.com/openai/codex/issues/2000#issuecomment-3171643611>

—
Reply to this email directly, view it on GitHub<https://github.com/openai/codex/issues/2000#issuecomment-3171643611>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEAXINWQ2XCVRDJDTZ2ZRRL3MYG2VAVCNFSM6AAAAACDNFR43GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZRGY2DGNRRGE>.
You are receiving this because you commented.Message ID: @.***>

4erdenko · 11 months ago

4erdenko, when you say it works, do you mean, you've downloaded .20, recreated signin, used codex cli and you've checked to see that you are NOT being charged for api consumption?? Randy Blasik My availability to @.***?anonymous&ep=signature> […](#)

Yes. At the moment, I don’t have an API key in auth.json, and I’m getting the default GPT-5 model. No money has been deducted. So yes, THAT problem is solved.
The output format is terrible, but that’s unrelated to the issue.

TheComplianceAide · 11 months ago

You sir, are a bit of a hero to me. Thank you for your quick response. Ill hop on and test.

Randy Blasik
My availability to @.***?anonymous&ep=signature>

________________________________
From: 4erdenko @.*>
Sent: Saturday, August 9, 2025 11:32:50 AM
To: openai/codex @.*>
Cc: Randy Blasik @.>; Comment @.>
Subject: Re: [openai/codex] [Windows] Sign in with ChatGPT still generates & requires an API key (Pro user) → API charges; revoking key breaks CLI (Issue #2000)

[https://avatars.githubusercontent.com/u/93295097?s=20&v=4]4erdenko left a comment (openai/codex#2000)<https://github.com/openai/codex/issues/2000#issuecomment-3171775205>

4erdenko, when you say it works, do you mean, you've downloaded .20, recreated signin, used codex cli and you've checked to see that you are NOT being charged for api consumption??

Randy Blasik
My availability to @.***?anonymous&ep=signature>
…

—
Reply to this email directly, view it on GitHub<https://github.com/openai/codex/issues/2000#issuecomment-3171775205>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEAXINROFBPNLEREF3AXJRT3MYICFAVCNFSM6AAAAACDNFR43GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZRG43TKMRQGU>.
You are receiving this because you commented.Message ID: @.***>

Aze1338 · 11 months ago

in my opinion the log out, log in feature should be improved (user experience wise). but you guys did fix the main annoying issues so good job.

jacobhallgren · 11 months ago

> Sign in with ChatGPT to use Codex as part of your paid plan > or connect an API key for usage-based billing > > 1. Sign in with ChatGPT > > Usage included with Plus, Pro, and Team plans > > > > 2. Provide your own API key > Pay for what you use > > Press Enter to continue > login_with_chatgpt subprocess failed See above: 0.20.0, delete auth.json, try codex login again?

I deleted the entriy .codex folder and still get login_with_chatgpt subprocess failed

bolinfest collaborator · 11 months ago

@jacobhallgren do you have python3 on your PATH? The login flow currently runs a Python script, though https://github.com/openai/codex/pull/2047 is in the works to eliminate that.

bolinfest collaborator · 11 months ago

But another, old bug with WSL 2 (Ubuntu) still there. Its another case when codex cant login you via browser from WSL.

I guess we can close this issue ?

@4erdenko For now, you need to copy the ~/.codex/auth.json file that you created on a machine where you were able to log in via localhost to the [presumably] headless machine (WSL 2 in this case).

bolinfest collaborator · 11 months ago

@4erdenko (and others who have hit this issue), I put up https://github.com/openai/codex/pull/2121 to provide more detailed information, as this is a common situation today, particularly for Windows/WSL users.

jeffb4658-hash · 11 months ago

****

PGrayCS · 11 months ago

I am still not able to login is this issue still occuring for everyone?

jacobhallgren · 11 months ago

@jacobhallgren do you have python3 on your PATH? The login flow currently runs a Python script, though #2047 is in the works to eliminate that.

Yes I use python a lot and have it in my path so python works for me, but this still fails for me when trying to login.

TheComplianceAide · 11 months ago

@PGrayCS Yes it's working for me I'm on windows + codex cli 0.20. I gave errors to chatgpt when trying it after an update from .19. It walked me through the fixes. I needed to fix path issues, and a few other things to get it to work.

LiamDGray · 11 months ago

I'm on Windows in a cmd.exe shell with codex CLI 0.20. When I run it and opt to sign in with ChatGPT, I get "program not found." I do have python3 in my path, but I don't have python3.exe in my path, due to the way I installed Python, via pyenv. To fix this, I plan to move away from pyenv.

As installed under pyenv, my Python3 shows up in my path like:

C:\Users\liamd>where python3
C:\Users\liamd\.pyenv\pyenv-win\shims\python3
C:\Users\liamd\.pyenv\pyenv-win\shims\python3.bat

The python3 file without an extension is actually a shell script with a shebang in it, a wrapper like the batch file is.

C:\Users\liamd\.pyenv\pyenv-win\shims>cat python3.bat
@echo off
chcp 1250 > NUL
call pyenv exec %~n0 %*

C:\Users\liamd\.pyenv\pyenv-win\shims>cat python3
#!/bin/sh
pyenv exec $(basename "$0") "$@"

And in C:\Users\liamd\.pyenv\pyenv-win\shims I don't have a Python.exe. Instead, I have just about every other name for Python, e.g.:

08/01/2025 03:51 PM 45 python
08/01/2025 03:51 PM 45 python-argcomplete-check-easy-install-script
08/01/2025 03:51 PM 53 python-argcomplete-check-easy-install-script.bat
08/01/2025 03:51 PM 53 python.bat
08/01/2025 03:51 PM 45 python3
08/01/2025 03:51 PM 45 python3.11
08/01/2025 03:51 PM 53 python3.11.bat
08/01/2025 03:51 PM 45 python3.7
08/01/2025 03:51 PM 53 python3.7.bat
08/01/2025 03:51 PM 53 python3.bat
08/01/2025 03:51 PM 45 python311
08/01/2025 03:51 PM 53 python311.bat
08/01/2025 03:51 PM 45 python37
08/01/2025 03:51 PM 53 python37.bat
08/01/2025 03:51 PM 45 pythonw
08/01/2025 03:51 PM 53 pythonw.bat
08/01/2025 03:51 PM 45 pythonw3
08/01/2025 03:51 PM 45 pythonw3.11
08/01/2025 03:51 PM 53 pythonw3.11.bat
08/01/2025 03:51 PM 45 pythonw3.7
08/01/2025 03:51 PM 53 pythonw3.7.bat
08/01/2025 03:51 PM 53 pythonw3.bat
08/01/2025 03:51 PM 45 pythonw311
08/01/2025 03:51 PM 53 pythonw311.bat
08/01/2025 03:51 PM 45 pythonw37
08/01/2025 03:51 PM 53 pythonw37.bat
26 File(s) 1,274 bytes

LiamDGray · 11 months ago

Switched to WSL and got further:
"Starting local login server on http://localhost:1455"

The page never loads. The browser eventually gives me a 404.

The CLI dies just as it's printing this:

"If your browser did not open, navigate to this URL to authenticate:

https://auth.openai.com/oauth/authorize?response_type=code&client_id=app_EMoamEEZ73f0CkXaXp7hrann&redirect_uri=http%3A%2F%2Flocalhost%3A1455%2Fauth%2Fcallback&scope=openid+profile+email+offline_access&code_challenge=6bKLETH2WA-HYaExbqdqhEdLxO41w2HTVmIRPDY2mpA&code_challenge_method=S256&id_token_add_organizations=true&codex_cli_simplified_flow=true&state=77000984903fb58def3efb5ec847b165d9029a2a8320c0e155867ecca9ec891c
Error logging in: login_with_chatgpt subprocess failed:"

The Codex CLI program that has just died also ran the local web server process. So, after I go through the OAuth flow at the above URL, the callback webhook is attempted but fails because the local server is dead already.

Edit: I kept trying this, and eventually this did work, for some reason!

4erdenko · 11 months ago

I'm on Windows in a cmd.exe shell with codex CLI 0.20. When I run it and opt to sign in with ChatGPT, I get "program not found." I do have python3 in my path, but I don't have python3.exe in my path, due to the way I installed Python, via pyenv. To fix this, I plan to move away from pyenv. As installed under pyenv, my Python3 shows up in my path like: C:\Users\liamd>where python3 C:\Users\liamd.pyenv\pyenv-win\shims\python3 C:\Users\liamd.pyenv\pyenv-win\shims\python3.bat The python3 file without an extension is actually a shell script with a shebang in it, a wrapper like the batch file is. C:\Users\liamd.pyenv\pyenv-win\shims>cat python3.bat @echo off chcp 1250 > NUL call pyenv exec %~n0 %* C:\Users\liamd.pyenv\pyenv-win\shims>cat python3 #!/bin/sh pyenv exec $(basename "$0") "$@" And in C:\Users\liamd.pyenv\pyenv-win\shims I don't have a Python.exe. Instead, I have just about every other name for Python, e.g.: 08/01/2025 03:51 PM 45 python 08/01/2025 03:51 PM 45 python-argcomplete-check-easy-install-script 08/01/2025 03:51 PM 53 python-argcomplete-check-easy-install-script.bat 08/01/2025 03:51 PM 53 python.bat 08/01/2025 03:51 PM 45 python3 08/01/2025 03:51 PM 45 python3.11 08/01/2025 03:51 PM 53 python3.11.bat 08/01/2025 03:51 PM 45 python3.7 08/01/2025 03:51 PM 53 python3.7.bat 08/01/2025 03:51 PM 53 python3.bat 08/01/2025 03:51 PM 45 python311 08/01/2025 03:51 PM 53 python311.bat 08/01/2025 03:51 PM 45 python37 08/01/2025 03:51 PM 53 python37.bat 08/01/2025 03:51 PM 45 pythonw 08/01/2025 03:51 PM 53 pythonw.bat 08/01/2025 03:51 PM 45 pythonw3 08/01/2025 03:51 PM 45 pythonw3.11 08/01/2025 03:51 PM 53 pythonw3.11.bat 08/01/2025 03:51 PM 45 pythonw3.7 08/01/2025 03:51 PM 53 pythonw3.7.bat 08/01/2025 03:51 PM 53 pythonw3.bat 08/01/2025 03:51 PM 45 pythonw311 08/01/2025 03:51 PM 53 pythonw311.bat 08/01/2025 03:51 PM 45 pythonw37 08/01/2025 03:51 PM 53 pythonw37.bat 26 File(s) 1,274 bytes

Because want Python from Microsoft store (why??). After that it works for me.

PGrayCS · 11 months ago

This is how I fixed it - thanks to ChatGPT for 100% doing this I take no credit! GPT5 is amazing :D

Root cause
Codex CLI 0.20 starts its login flow by launching python3.
If Windows can’t find a real python3.exe on your PATH (e.g., only pyenv shims or a python3.bat), the spawn fails and you get that error. A second common issue is that codex itself isn’t on PATH in cmd.exe (npm global bin missing).

TL;DR Fix
Make sure Windows has a real python3.exe:

Install Python 3.13 from Microsoft Store, then enable its alias:
Settings → Apps → Advanced app settings → App execution aliases → turn ON “Python 3.13 (python3.exe)”.

---

Fix: `codex login` → “Error logging in: program not found” on Windows (Codex CLI 0.20)

Symptom

codex login
Error logging in: program not found

Root cause (Windows)
Codex 0.20 tries to launch python3 during its login flow. If there isn’t a real python3.exe on your PATH (e.g., only pyenv shims or a .bat), the spawn fails and you get this error. A separate hiccup is when codex itself isn’t on PATH in cmd.exe.

---

TL;DR (works reliably)

Install Python 3.13 from Microsoft Store and enable the alias

Settings → Apps → Advanced app settings → App execution aliases → turn ON:
Python 3.13 (python3.exe)
(Optional: also enable Python 3.13 (python.exe).)

Remove any shim that shadows python3.exe (if you created one earlier):

del "%USERPROFILE%\bin\python3.bat"

Make sure Codex is on PATH (cmd.exe):

set PATH=%APPDATA%\npm;%PATH%
where codex
codex --version

If where codex still shows nothing, run it directly:

"%APPDATA%\npm\codex.cmd" --version

Clear any old browser override (then open a new terminal):

setx BROWSER ""

Log in

codex login

If the browser doesn’t open automatically while codex login is running:

start http://localhost:1455/

---

Alternative (avoid Microsoft Store)

If you have a regular Python install:

Locate your real python.exe (e.g. C:\Users\<you>\AppData\Local\Programs\Python\Python313\python.exe).
Copy it to the same folder as python3.exe:

``cmd copy C:\...\python.exe C:\...\python3.exe``

Ensure that folder is on PATH ahead of any pyenv shim directories.
Verify:

``cmd where python3 python3 --version codex login``

---

Gotchas (Windows)

pyenv-win provides python3 shims (python3, python3.bat) but not a real python3.exe → Codex fails.
setx PATH ... truncates to 1024 chars. For permanent changes, use System Properties → Environment Variables and add entries there.
%APPDATA%\npm (where codex.cmd lives) must be on PATH in cmd.exe.
After changing aliases or PATH, open a new terminal.

---

Verification checklist

where codex           && rem → should show %APPDATA%\npm\codex.cmd
codex --version       && rem → codex-cli 0.20.0 (or newer)

where python3         && rem → ...\Microsoft\WindowsApps\python3.exe  (or real install dir)
python3 --version     && rem → Python 3.13.x

codex login           && rem → opens browser / completes auth

<details>
<summary>Why this happens</summary>
Codex’s login flow shells out to python3 even on Windows. If Windows can’t resolve a native executable at python3.exe, the spawn fails with “program not found.” Enabling the Microsoft Store python3.exe alias (or providing a real python3.exe next to your python.exe) fixes the underlying process launch.
</details>
::contentReference[oaicite:0]{index=0}

jacobhallgren · 11 months ago

This is how I fixed it - thanks to ChatGPT for 100% doing this I take no credit! GPT5 is amazing :D Root cause Codex CLI 0.20 starts its login flow by launching python3. If Windows can’t find a real python3.exe on your PATH (e.g., only pyenv shims or a python3.bat), the spawn fails and you get that error. A second common issue is that codex itself isn’t on PATH in cmd.exe (npm global bin missing). TL;DR Fix Make sure Windows has a real python3.exe: Install Python 3.13 from Microsoft Store, then enable its alias: Settings → Apps → Advanced app settings → App execution aliases → turn ON “Python 3.13 (python3.exe)”. Here’s a drop-in GitHub comment you can post: ## Fix: codex login → “Error logging in: program not found” on Windows (Codex CLI 0.20) Symptom codex login Error logging in: program not found Root cause (Windows) Codex 0.20 tries to launch python3 during its login flow. If there isn’t a _real_ python3.exe on your PATH (e.g., only pyenv shims or a .bat), the spawn fails and you get this error. A separate hiccup is when codex itself isn’t on PATH in cmd.exe. ### TL;DR (works reliably) 1. Install Python 3.13 from Microsoft Store and enable the alias Settings → Apps → Advanced app settings → App execution aliases → turn ON: Python 3.13 (python3.exe) (Optional: also enable Python 3.13 (python.exe).) 2. Remove any shim that shadows python3.exe (if you created one earlier): del "%USERPROFILE%\bin\python3.bat" 3. Make sure Codex is on PATH (cmd.exe): set PATH=%APPDATA%\npm;%PATH% where codex codex --version If where codex still shows nothing, run it directly: "%APPDATA%\npm\codex.cmd" --version 4. Clear any old browser override (then open a new terminal): setx BROWSER "" 5. Log in codex login If the browser doesn’t open automatically while codex login is running: start http://localhost:1455/ ### Alternative (avoid Microsoft Store) If you have a regular Python install: 1. Locate your real python.exe (e.g. C:\Users\<you>\AppData\Local\Programs\Python\Python313\python.exe). 2. Copy it to the same folder as python3.exe: copy C:\...\python.exe C:\...\python3.exe 3. Ensure that folder is on PATH ahead of any pyenv shim directories. 4. Verify: where python3 python3 --version codex login ### Gotchas (Windows) pyenv-win provides python3 shims (python3, python3.bat) but not a real python3.exe → Codex fails. setx PATH ... truncates to 1024 chars. For permanent changes, use System Properties → Environment Variables and add entries there. %APPDATA%\npm (where codex.cmd lives) must be on PATH in cmd.exe. After changing aliases or PATH, open a new terminal. ### Verification checklist where codex && rem → should show %APPDATA%\npm\codex.cmd codex --version && rem → codex-cli 0.20.0 (or newer) where python3 && rem → ...\Microsoft\WindowsApps\python3.exe (or real install dir) python3 --version && rem → Python 3.13.x codex login && rem → opens browser / completes auth Why this happens ::contentReference[oaicite:0]{index=0}

I prefer them to fix this native in the code instead of the user doing this

angeloc-dl · 11 months ago

I solved doing this:
New-Item -ItemType SymbolicLink -Path "C:\Python313\python3.exe" -Target "C:\python313\python.exe"

p.s. I have py in c:\Python313 folder

jacobhallgren · 11 months ago

I’ll just wait, if the OpenAI devs can’t even get the installer working, it doesn’t inspire much confidence in their coding agent.

joshleblanc contributor · 11 months ago

You just need to have python3.exe in your path. It's not really a codex problem.

jacobhallgren · 11 months ago

You just need to have python3.exe in your path. It's not really a codex problem.

I have python in my path and it works great for everything except codex.

joshleblanc contributor · 11 months ago

What error are you getting?

angeloc-dl · 11 months ago

You just need to have python3.exe in your path. It's not really a codex problem.

It is a codex problem since python3.exe does not exist on windows after python official installation, unless you do some custom fix to make this work

jacobhallgren · 11 months ago

What error are you getting?

That it don't find python.

jacobhallgren · 11 months ago

> You just need to have python3.exe in your path. It's not really a codex problem. It is a codex problem since python3.exe does not exist on windows after python official installation, unless you do some custom fix to make this work

Agree 100%

angeloc-dl · 11 months ago

on Windows with 0.20.0 I get: login_with_chatgpt subprocess failed

@joshleblanc this one

joshleblanc contributor · 11 months ago

That doesn't sound like python missing, unless the built version has less verbose errors than the dev build. The errors I got while testing the change very explicitly stated what was missing and how to fix it (because windows hijacks the python bindings by default).

Wonder if it's something up with your temp directory. I don't suppose your user profile had a space in it?

Did you delete the .codex dir in %userprofile%?

I'm just spit balling here.

angeloc-dl · 11 months ago

Did you delete the .codex dir in %userprofile%?

Yes, same error.
I have python.exe in my path.
I fixed with a symlink named python3.exe to python.exe with the command described above.

jacobhallgren · 11 months ago

Why cant you guys make the script just work with the standard "python" environment variable?

angeloc-dl · 11 months ago

Why cant you guys make the script just work with the standard "python" environment variable?

what is the env variable you are mentioning exactly ?
if you would like to provide exactly how to perform the test you are mentioning, I will do that.

jacobhallgren · 11 months ago

> Why cant you guys make the script just work with the standard "python" environment variable? what is the env variable you are mentioning exactly ? if you would like to provide exactly how to perform the test you are mentioning, I will do that.

instead of the script using python3 it should also work with "python" that is standard on windows.

jeffb4658-hash · 11 months ago

!Image

deep02g · 11 months ago

I am getting a "Program not found" error when I select the browser option. Does anyone have a fix for that?

HenriqueDest · 11 months ago

Hey everyone, just an update. After installing Python 3.13 from the Microsoft Store, running codex login worked.

bolinfest collaborator · 11 months ago

If you have been running into issues related to the Python stuff, please update to 0.22.0 as we migrated the Python code to Rust in the new release: https://github.com/openai/codex/releases/tag/rust-v0.22.0

As an added bonus, 0.22.0 now supports Markdown and streaming!

4erdenko · 11 months ago

If you have been running into issues related to the Python stuff, please update to 0.22.0 as we migrated the Python code to Rust in the new release: https://github.com/openai/codex/releases/tag/rust-v0.22.0 As an added bonus, 0.22.0 now supports Markdown and streaming!

Looks really great! Thank you.
And again, initial problem was solved too, earlier.

Showing cached comments. Read the full discussion on GitHub ↗

[Windows] Sign in with ChatGPT still generates & requires an API key (Pro user) → API charges; revoking key breaks CLI

52 Comments

Fix: codex login → “Error logging in: program not found” on Windows (Codex CLI 0.20)

TL;DR (works reliably)

Alternative (avoid Microsoft Store)

Gotchas (Windows)

Verification checklist

Fix: `codex login` → “Error logging in: program not found” on Windows (Codex CLI 0.20)