-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Description
Which model were you using?
gpt-5
What issue are you seeing?
From https://www.reddit.com/r/codex/comments/1ofswmz/very_concrete_example_of_codex_running_amok/
It's very hard to prove either way whether codex is performing badly or not. Saying that it's not doing well, and people come out screaming "skill issue". So I thought I would share one very concrete, beautiful example:
• Explored └ Read data.sql List ls -la • Viewed Image └ payload_20251025_140646.json
⚠️ stream error: unexpected status 400 Bad Request: { "error": { "message": "Invalid 'input[118].content[0].image_url'. Expected a base64-encoded data URL with an image MIME type (e.g. 'data:image/png;base64,aW1nIGJ5dGVzIGhlcmU='), but got unsupported MIME type 'application/json'.", "type": "invalid_request_error", "param": "input[118].content[0].image_url", "code": "invalid_value" } }; retrying 1/5 in 188ms…Ie. it started thinking all of a sudden that json files should be read like images. :D This is based only on one prompt asking it to investigate an SQL insert issue. GPT-5 high.
For the record, my subjective evaluation from this week: codex has been performing extremely well, until today. Today it's been between
ok and absolutely horrible.