Repository navigation
automation_update tool schema is rejected by strict OpenAI-compatible providers #39848
Description
What happened?
Codex Desktop can fail before the model responds when a strict OpenAI-compatible provider validates the bundled automation_update tool schema.
Observed error:
Invalid schema for function 'automation_update': schema must be a JSON Schema of 'type: "object"', got 'type: "None"'
This appears related to the existing codex_app__automation_update / automation_update schema issue, where the root schema is not emitted as a normal JSON Schema object. Some providers reject it during tool/function schema validation.
Environment
- Product: Codex Desktop
- Local Codex web Last Version:
151.0.7922.170 - Bundled browser plugin version observed locally:
26.818.31338 - OS: Windows
- Provider type: OpenAI-compatible strict provider / non-OpenAI endpoint
Expected behavior
The emitted automation_update tool schema should be accepted by strict JSON Schema validators.
At minimum, the top-level schema should be a JSON Schema object, for example:
{
"type": "object",
"properties": {}
}or otherwise be normalized so strict providers do not reject it.
Actual behavior
The provider rejects the request before the model can respond because the function schema root is reported as type: "None" / type: null, rather than type: "object".
Impact
- Requests fail immediately at schema validation time.
- The failure blocks normal Codex usage with strict OpenAI-compatible providers.
- Users cannot work around this from the prompt side.
Related issues
Possibly related:
- Codex Desktop: automation_update schema (root oneOf, type null) 400s on strict providers like DeepSeek (Responses API) #37786
- [Bug] codex_app__automation_update schema type is null - causes DeepSeek HTTP 400 via CC Switch #36441
- json with "oneOf" as root causing error for azure openai endpoint #30132
Activity
wenlinl commentedon Sep 15, 2026
Same failure class, but a distinct trigger on the current build:
automation_updateis deferred rather than eagerly emitted, and the broken request is the one aftertool_searchdiscovers a deferred app/MCP tool — it then carriesparameters: {}and is rejected. The thread stays broken on every subsequent turn.Full repro (DeepSeek Responses) + minimal payload matrix: #45585
saevios commentedon Oct 12, 2026
I have this issue with the Codex Desktop app, and using the model-router Foundry model. CLI and VSCode implementation is working fine. It is just the Desktop app that is not. I receive this error:
Invalid schema for function 'automation_update': schema must have type 'object' and not have 'oneOf'/'anyOf'/'allOf'/'enum'/'const'/'not' at the top level.
Desktop app details:
Version 26.1007.21434
Released 9 Oct 2026