Getting Codex process errored. Any help?

I had ChatGPT transcibe the image with the error message to text so that the error messages could be indexed by search engines and AI.

Codex process errored: Codex app-server process exited unexpectedly (code=unknown, signal=SIGTRAP). Last CLI error:
2026-06-22T13:00:42.899847Z ERROR codex_core::util: Custom tool call output is missing for call_id: call_hFnQr97StX2UOgIRwf8ucvTo
2026-06-22T13:00:42.899904Z ERROR codex_core::util: Custom tool call output is missing for call_id: call_658f1F71suHacxs3RxTCtuUN

2026-06-22T13:00:42.899847Z ERROR codex_core::util: Custom tool call output is missing for call_id: call_hFnQr97StX2UOgIRwf8ucvTo
2026-06-22T13:00:42.899904Z ERROR codex_core::util: Custom tool call output is missing for call_id: call_658f1F71suHacxs3RxTCtuUN



Codex process errored: Codex app-server process exited unexpectedly (code=unknown,
signal=SIGTRAP). Last CLI error:
codex_memories_write::phase2: Phase 2 no changes

codex_memories_write::phase2: Phase 2 no changes

You are welcome to discuss Codex issues on the forum, however the official place to report and track them is the GitHub issue tracker for OpenAI Codex.

I searched ChatGPT for “Codex app-server process exited unexpectedly (code=unknown, signal=SIGTRAP).” and found

github.com/openai/codex

VS Code extension app-server crashes with SIGTRAP after creating a local conversation

opened 05:17AM - 21 Jun 26 UTC

      kntiwary
    

bug extension app-server

Summary The Codex VS Code extension's local app-server exits with SIGTRAP… shortly after a new local conversation is created. The extension then reports Codex process is not available and cannot submit turns. ### Environment - macOS - VS Code - Codex VS Code extension 26.616.51431 (updated from 26.5616.51431; same behavior) - Local Codex runtime paired with the desktop app ### Steps to reproduce 1. Start VS Code with the Codex extension enabled. 2. Open Codex and create a new local conversation. 3. Wait a few seconds, or attempt to submit a prompt. ### Expected behavior The local conversation remains available and accepts turns. ### Actual behavior The extension log shows the conversation being created, followed by repeated rollout-list warnings and a fatal app-server exit: text Conversation created conversationId=... codex_rollout::list: state db discrepancy during find_thread_path_by_id_str_in_subdir: falling_back Codex app-server process exited unexpectedly (code=unknown, signal=SIGTRAP) After the exit, subsequent requests fail with Codex process is not available. ### Troubleshooting already performed - Restarted VS Code. - Updated the extension to 26.616.51431. - Rebuilt the local ~/.codex/state_5.sqlite index. - Removed all active rollout transcripts with unmatched custom-tool-call outputs from the session scan tree. - Confirmed the active session tree had zero incomplete transcripts before restarting. The crash still happens on a freshly created conversation with clean local state, so it appears the app-server treats the fallback condition as fatal.

If that issue matches your problem, consider adding a reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work.

If it is not the same issue, try searching the existing GitHub issues for a closer match. If you cannot find one, then open a new issue with as much detail as possible.