Repository navigation
Let Codex return structured output - #769
Merged
Merged
Conversation
SaladDay
force-pushed
the
let-codex-return-structured-output
branch
from
October 19, 2026 06:15
49d631e to
2164ccb
Compare
Contributor
|
Found 3 test failures on Blacksmith runners: Failures
|
Declare structured output for Codex and send the frozen schema as the native outputSchema on every root turn/start. The native strict handling, provider errors and final message text pass through unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codex rejected
text.format: json_schema, although pinned Codex 0.153.4 has a native per-turnoutputSchema(app-server-protocol/src/protocol/v2/turn.rs:242). The declaration now admits it, and the adapter sends the frozen schema unchanged on every rootturn/start, including after resume. The native final message is published unchanged.Native facts, from the pinned source:
turn/steercarries no schema and joins the running Turn.serde_jsonarbitrary_precisionis enabled throughcodex-exec-server, so numbers stay lossless and no binary64 admission check applies.Checks:
internal/harnessconfig/...,apps/daemon/internal/agent/codexandservices/core/internal/executionpass.OutputSchemaremoved fromturn/start; plan assignment removed; preparation rejection restored.text.formatjson_schema. MiniMax returned no error but ignored it and answered in prose. That is provider behavior, and the contract now says so, so the capability cell is "Admitted", not "Verified".Need help on this PR? Tag
@codesmith-botwith what you need.