3 people reported
All time, since Sep 14.
automation_update invalid schema
“Every request in that thread is rejected before the model produces any output.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/16847/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Strict provider rejects automation_update schema with type null. Requests are rejected with HTTP 400 before any inference, and the thread stays unusable once the tool is in the request.
Is this your bug?
File my report- Where
- automation_update tool schema
- Error text
Invalid schema for function 'codex_app::automation_update': schema must be a JSON Schema of 'type: "object"', got 'type: null'.- Versions
- 26.818.61809 to 26.915.31945
- Platforms
- macOS, Windows
- How bad
- Stops work: a core feature can't be used. Some reports say it blocks them completely.
Original reports3, newest first
- [Windows] automation_update tool schema missing top-level type:"object" → HTTP 400 on custom providerOn GitHub#55809
- Invalid JSON schema for
codex_app::automation_updatemakes every request fail on a strict provider (DeepSeek, wire_api = "responses")On GitHub#47161 - tool_search exposes deferred tools with an empty schema, permanently breaking threads on strict Responses providers (DeepSeek)On GitHub#45585