The model 'gpt-image-2' does not exist.

Resolved 💬 14 comments Opened Jun 2, 2026 by ufukayyildiz Closed Jun 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.601.20914 • Released Jun 2, 2026

What subscription do you have?

pro

What platform is your computer?

_MacOS_

What issue are you seeing?

i get this message The model 'gpt-image-2' does not exist. after any prompt while use codex with 5.5

What steps can reproduce the bug?

Feedback ID: 019e8aaa-c77b-7c50-a232-2535e473f3cc

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

14 Comments

github-actions[bot] contributor · 1 month ago

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

  • #25970
  • #25969
  • #25968
  • #25965
  • #25967

Powered by Codex Action

Timandilu · 1 month ago

Same issue for me on windows, and it always stops the turn

tgackles · 1 month ago

Same issue here.

Feedback ID: 019e4606-a7db-7132-8ea5-bd82be7ae701

Spincial · 1 month ago

same

adolfobrandao · 1 month ago

Same.

vortegon · 1 month ago

Same issue: The model 'gpt-image-2' does not exist. after any prompt while use codex with 5.4

Version 26.601.20914 • Released Jun 2, 2026

cktang88 · 1 month ago

same

ChrisMasterton · 1 month ago

And app-shot isnt working any more eitehr.

halidaee · 1 month ago

Had this on 26.527.60818 (3437). Upgrading to 26.601.20914 did not work. Guessing not codex version related.

Lexer-Lux · 1 month ago

I think it's honestly impressive how OpenAI keeps managing to break this app in new and exciting ways. Can't wait to see what they come up with next

weijie0 · 1 month ago

same

ufukayyildiz · 1 month ago

now fixed for me

shanecp · 1 month ago

Same issue. Starting a new thread solved it for now.

etraut-openai contributor · 1 month ago

Thanks for reporting the issue. This incident has been mitigated, so you should no longer see the error.