On MacBook Pro 2019 the Codex Extension for VS CODE gives errors

Welcome to the forum!

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 Codex issues for find_thread_path_by_id_str_in_subdir and found:

github.com/openai/codex

Codex crashed with the following error

opened 06:59AM - 20 Jun 26 UTC

      suryapratap-github
    

bug extension session

What version of the IDE extension are you using? 26.616.32156 ### What sub…scription do you have? Plus ### Which IDE are you using? VS Code ### What platform is your computer? macOS x64 ### What issue are you seeing? An error has occurred Codex crashed with the following error: Codex process errored: Codex process is not available codex_rollout::list: state db discrepancy during find_thread_path_by_id_str_in_subdir: falling_back Some things to try: Check your config.toml for invalid settings Try updating your IDE settings Try updating Codex or installing a different version Click reload to restart Codex, or visit our documentation for additional help. ### What steps can reproduce the bug? Steps to Reproduce Install the Codex extension in VS Code. Open VS Code and launch the Codex extension. Sign in to the extension using a ChatGPT account. Open the Codex chat panel. Enter any prompt in the chat input field and submit it. Wait for the response generation to start. ### What is the expected behavior? Expected Behavior The extension should process the prompt and return a response without interruption. Actual Behavior The Codex extension crashes immediately after submitting the prompt. ### Additional information VS Code version: 1.125.1 (Universal) Codex extension version: 26.616.32156 Operating System: macOS 15.7.7 (24G720) Crash logs/error messages: Reproducibility: Always

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.