Updated and now I cannot pull up any threads, the thread keeps spamming like its refreshing and I have a red error box at the top

Resolved 💬 15 comments Opened Mar 11, 2026 by PanicIsReal Closed Jul 2, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.309.31024 (962)

What subscription do you have?

Pro

What platform is your computer?

MBP M3 Max

What issue are you seeing?

<img width="381" height="80" alt="Image" src="https://github.com/user-attachments/assets/eb148f2b-cb2d-40e5-a86d-885e42d58116" />

What steps can reproduce the bug?

Update the app and pull up a thread you were working with

What is the expected behavior?

To load.

Additional information

I have tried logging out of Codex App and logging back in, restarting my MBP.

CLI Still works fine interim.

_No response_

View original on GitHub ↗

15 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #14396
  • #14162
  • #13724
  • #14370

Powered by Codex Action

carlosglz1912 · 4 months ago

Yep this just happened to me in MacOs (Macbook Air M1) Also showed a banner with 'new' gpt-5.3-codex and cant load my recent threads from 2hrs

zenzig · 4 months ago

Also have same issue, Mac M1

matheuslenke · 4 months ago

Having the same issue here, Macbook M3 Pro. Can't change the selected model neither send any message on existing or new threads.

Jaesung-Jung · 4 months ago

Same here (macOS app). but, codex cli works file.

matheuslenke · 4 months ago

Just found the cause here. In my case, I got GSD installed. When I went to settings -> Configuration I saw some errors in configuration files caused by it. I removed GSD and restarted the app, and now I saw a different error at config.toml. Honestly, I do not remember now, I just removed the config that it was complaining until everything looked fine and... voilà, it worked again.
Here is my config page without errors (it should show a yellow tooltip if you have these errors)

<img width="1128" height="539" alt="Image" src="https://github.com/user-attachments/assets/5a99ea86-3a73-4658-bc3a-91248247ab57" />

And here is my config.toml that is showing no errors

model = "gpt-5.4"
model_reasoning_effort = "medium"
personality = "pragmatic"

max_threads = 4
max_depth = 2
Jaesung-Jung · 4 months ago

In my case, there was a minor error in workspace/.codex/config.toml. I was able to detect the issue using a VS Code extension called Even Better TOML. After fixing it, I confirmed that the Codex macOS app works normally.

PanicIsReal · 4 months ago
Just found the cause here. In my case, I got GSD installed. When I went to settings -> Configuration I saw some errors in configuration files caused by it. I removed GSD and restarted the app, and now I saw a different error at config.toml. Honestly, I do not remember now, I just removed the config that it was complaining until everything looked fine and... voilà, it worked again. Here is my config page without errors (it should show a yellow tooltip if you have these errors) <img alt="Image" width="1128" height="539" src="https://private-user-images.githubusercontent.com/50427349/561969168-5a99ea86-3a73-4658-bc3a-91248247ab57.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzMyOTYzMDgsIm5iZiI6MTc3MzI5NjAwOCwicGF0aCI6Ii81MDQyNzM0OS81NjE5NjkxNjgtNWE5OWVhODYtM2E3My00NjU4LWJjM2EtOTEyNDgyNDdhYjU3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAzMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMzEyVDA2MTMyOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI2MDE0NzNlOWM2YzhiYjQzYTNjZDlhYTJjYzAwMzk3YmJlMmVjM2FhYzY2MDlmMDU4MjQ0M2IwYWY5ZGIzZGImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.iO26giGjze3jsUswlZqsmHFGbxpvTp2WDm828cF8kqQ"> And here is my config.toml that is showing no errors model = "gpt-5.4" model_reasoning_effort = "medium" personality = "pragmatic" max_threads = 4 max_depth = 2

I've personally changed nothing, and had AI scrutinize my config, nothing ive tried has fixed my issue.

luispittagros · 4 months ago

Same issue.

ottenhoff · 4 months ago

GSD uses invalid TOML in the agents directory. You can confirm the issues with a TOML validator like taplo:

find . -name '*.toml' -print0 | xargs -0 taplo check

The GSD fix is in the PR queue here: https://github.com/gsd-build/get-shit-done/pull/1008

PanicIsReal · 4 months ago

mv config.toml bkup.toml and launched, same issue, unable to load threads.

People are saying some config issues helped it for them, but rest assured even with no config, I still cannot load a thread.

ottenhoff · 4 months ago
mv config.toml bkup.toml and launched, same issue, unable to load threads. People are saying some config issues helped it for them, but rest assured even with no config, I still cannot load a thread.

The issue is not your config.toml, it's likely a bad TOML file in agents directory. Run a TOML validator against all toml files under .codex

PanicIsReal · 4 months ago
> mv config.toml bkup.toml and launched, same issue, unable to load threads. > People are saying some config issues helped it for them, but rest assured even with no config, I still cannot load a thread. The issue is not your config.toml, it's likely a bad TOML file in agents directory. Run a TOML validator against all toml files under .codex

You're correct, I narrowed it down to generic Agents I had made just simply to change model versions for low effort stuff, they were missing description field, which has never been an issue until the most recent patch. No error for it in the configuration page of codex, what a pain.

ottenhoff · 4 months ago

Better Codex behavior would:

1) Skip a bad agent TOML file instead of crashing startup
2) Warn user that there was a problem parsing specific bad agent TOML file
3) Point the user to Settings -> Configuration to see a bigger error

carlosglz1912 · 4 months ago

Puedo confirmar que GSD estaba causando el problema tambien para mi, despues de arrojar los desubrimientos del PR mencionado mas arriba dentro de opencode se puede parchear directamente cada agente o clonar el repo y hacer una instalacion nueva corrigiendo el archivo bin/install.js