Codex CLI 0.142.5 crashes with zsh: trace trap / SIGTRAP on macOS 12.6.3 x86_64, MacBookAir9,1.
What version of Codex CLI is running?
Codex CLI 0.142.5
What subscription do you have?
GPT Pro
Which model were you using?
5.5
What platform is your computer?
_No response_
What terminal emulator and version are you using (if applicable)?
_No response_
Codex doctor report
What issue are you seeing?
Codex CLI 0.142.5 crashes with zsh: trace trap / SIGTRAP on macOS 12.6.3 x86_64, MacBookAir9,1. The crash occurs even with a clean CODEX_HOME and in an empty directory. codex doctor reports 0 warn / 0 fail. Crash report shows EXC_BREAKPOINT / Trace/BPT trap: 5, faulting in v8::base::OS::SetPermissions -> v8::internal::CodeRange::InitReservation -> v8::internal::Heap::SetUp -> v8::internal::Isolate::Init. Earlier Antigravity logs showed thread_tools feature mismatch, but after updating both CLI and Codex.app to 0.142.5 the remaining failure is a native V8 SIGTRAP.
What steps can reproduce the bug?
Codex CLI 0.142.5 crashes with zsh: trace trap / SIGTRAP on macOS 12.6.3 x86_64, MacBookAir9,1. The crash occurs even with a clean CODEX_HOME and in an empty directory. codex doctor reports 0 warn / 0 fail. Crash report shows EXC_BREAKPOINT / Trace/BPT trap: 5, faulting in v8::base::OS::SetPermissions -> v8::internal::CodeRange::InitReservation -> v8::internal::Heap::SetUp -> v8::internal::Isolate::Init. Earlier Antigravity logs showed thread_tools feature mismatch, but after updating both CLI and Codex.app to 0.142.5 the remaining failure is a native V8 SIGTRAP.
What is the expected behavior?
_No response_
Additional information
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗