Bug Report: Codex app-server exited with code 127

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi team,
After updated cursor version today, I’m currently experiencing an issue where Codex in Cursor fails to start and shows the error:
Codex app-server process exited with code 127 and signal null (/bin/sh: /usr/bin/bash: not found).
Could you please look into this?
It happens every time I try to use Codex, even after reloading and checking my config.

Thanks for your help!

Steps to Reproduce

  1. Open Cursor IDE.
  2. Try to start or use Codex (e.g., by pressing Ctrl + L or opening the Codex panel).
  3. Codex fails to load and displays an error: Codex app-server process exited with code 127 and signal null.
  4. The error message shows /bin/sh: /usr/bin/bash: not found.
  5. Reloading or checking config.toml does not resolve the issue.

Screenshots / Screen Recordings

Screenshot_3.png
Screenshot_3.png1901×658 29.8 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.60 (system setup)
VSCode Version: 1.99.3
Commit: c6d93c13f57509f77eb65783b28e753857b74c00
Date: 2025-11-051’00:50:54.6452 (17 hrs a go)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 2220.0
V8: 13.8.258.32-electron.0
OS: Windows_NTx64 10.0.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey cursor team!
Any updates for this bug report?
This is really priority problem.
Currently I can’t work without codex.
Hope you help me asap!

3

It just solved by myself for over 10 hours.
However, if I had to offer one suggestion to the Cursor team, it would be that time is of the essence for developers. I hope the Cursor team will always be there for users when they face difficulties, so they can always feel reassured, no matter what.

4

Hello, can you kindly tell me how you solved this bug? today I meet the same problem too.

5

Hey, I get your frustration, but Cursor isn’t responsible for Codex extension. Codex is created by OpenAI which is entirely separate. Cursor simply allows you to install such extension in the IDE and use it, but that’s about it.

6

Of course, even so, I believe it would be in the best interest of the users if you reported a bug and let them know your feedback as soon as possible.

7

There’s really a lot of extensions and Cursor isn’t specifically managing those, its independent. So any bugs related to extensions, should be directly reported to the creators of the extension.

1 Like
8

Hi, @SIMON_YU .
You can downgrade cursor version from latest version to 1.7.54.( GitHub - oslook/cursor-ai-downloads: All Cursor AI's official download links for both the latest and older versions, making it easy for you to update, downgrade, and choose any version. 🚀 )
And just set up the Windows Subsystem for Linux (WSL) for codex.

Then run codex in wsl and run without wsl again.
Finally it worked well now.

I’m not sure the above my experience is real solution for this bug, but I would like to this is helpful for you.
If you have any question, feel free to ask me anytime.

10

Thanks a lot, @Kei_Nishikori — it worked!

1 Like
11

I encountered the same issue. After installing Ubuntu, I was able to run Codex in the terminal, but even after downgrading Cursor and installing the WSL extension, the same error still occurs. Did downgrading Cursor allow you to open the Codex extension and have it work normally again?

13

Yup, after downgrading Cursor version, and please run without wsl again.
Maybe then it will work well.

1 Like
15

Thanks a lot, finally after I deleted the home/.codex folder under Ubuntu again, when I reopened the extension it worked normally, and later it could also be used normally without WSL, using Codex on Cursor.

1 Like