crash process model 5.5

Open 💬 1 comment Opened Jun 22, 2026 by julortiz

What version of Codex CLI is running?

0.141.0

What subscription do you have?

PLUS

Which model were you using?

5.5

What platform is your computer?

uname -mprs Darwin 22.6.0 x86_64 i386

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

warp

Codex doctor report

{
  "schemaVersion": 1,
  "overallStatus": "ok",
  "codexVersion": "0.141.0",
  "environment": {
    "platform": "macos-x86_64",
    "os": "macOS Ventura",
    "terminal": "Warp",
    "model": "gpt-5.4"
  },
  "installation": {
    "status": "ok",
    "installType": "standalone",
    "managedBy": "standalone installer"
  },
  "repository": {
    "repoDetected": true,
    "branch": "<redacted>",
    "gitVersion": "2.38.0"
  },
  "auth": {
    "status": "ok",
    "mode": "chatgpt",
    "storedChatGPTTokens": true,
    "storedApiKey": false
  },
  "mcp": {
    "configuredServers": 1,
    "disabledServers": 0
  },
  "network": {
    "providerReachable": true,
    "websocketReachable": true,
    "authMode": "chatgpt"
  },
  "sandbox": {
    "approvalPolicy": "OnRequest",
    "filesystemSandbox": "restricted",
    "networkSandbox": "restricted"
  },
  "updates": {
    "currentVersion": "0.141.0",
    "latestVersion": "0.141.0",
    "status": "up-to-date"
  }
}

What issue are you seeing?

Codex CLI: 0.141.0
OS: macOS Ventura 13.7.8 (Intel x86_64)
Terminal: Warp
Model: GPT-5.5

Issue:
When a repository loads a SessionStart hook with code-review-graph context, GPT-5.5 crashes with:

zsh: trace trap codexts

The same repository, machine, and Codex CLI version work correctly with GPT-5.4.

Network diagnostics: OK
WebSocket diagnostics: OK
Authentication: ChatGPT
Installation: Standalone

What steps can reproduce the bug?

  1. Open warp terminar
  2. enter codex command
  3. prompt: usa code-review-graph para tener el contexto del codigo sincronizado con los MD de documentación del repo
  4. the cli crash in the step: Voy a usar code-review-graph primero para contrastar la arquitectura y los flujos reales con la documentación Markdown; después identificaré y corregiré desajustes concretos en los .md. • Working (9s • esc to interrupt) › zsh: trace trap codexts

What is the expected behavior?

The behavior expected is wait until the process end and validation using commands.

Additional information

_No response_

View original on GitHub ↗

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