Cannot run build
Resolved 💬 7 comments Opened Feb 2, 2026 by ybwbqg9379 Closed Apr 30, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.93.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.2-codex
What platform is your computer?
macOS
What terminal emulator and version are you using (if applicable)?
_No response_
What issue are you seeing?
“I'm preparing to run the combined npm run lint && npm run build command as required, expecting it to be a time-consuming but necessary
step.”
Run lint always works while run build does not work, stuck for really long
What steps can reproduce the bug?
Uploaded thread: 019c1bd0-e1e9-7f72-a161-f7241e9898d6
NPM RUN BUILD
What is the expected behavior?
_No response_
Additional information
_No response_
7 Comments
Does this happen every time the agent attempts to run your build script? Or was this a one-time problem?
I'm guessing that your build script is either running indefinitely or is waiting for some interactive user input. If you invoke it manually, does it complete without asking for any input?
It's also possible that the build script is doing something that is blocked by the Codex sandbox mechanism. If you temporarily disable the sandbox, does that allow it to complete?
The problem is if I either run build with Cursor, Claude Code or just pure terminal, npm run build works. But just in Codex CLI, npm run lint works fine, but takes forever to run "npm run build".
It automatically runs lint and build as I request, but since it took too long I had to manually terminate it.
I thought about the sandbox issue but what's interesting is npm run lint works.
Thanks for the additional details. You'll likely need to do some debugging on your side to understand the issue better. There's unfortunately not much more I can discern from the logs. If you find any more clues (e.g. if the slowdown goes away when running outside of the Codex sandbox), please let me know.
This also happens to me in both the Codex CLI and the app
+1
+1
I'm facing this issue too, what was the solution?