Skip to content

feat(protocol): add bounded Codex Responses parser - #41

Draft
tiammomo wants to merge 1 commit into
mainfrom
tiammomo/protocol/add-codex-responses-parser-fixture
Draft

feat(protocol): add bounded Codex Responses parser#41
tiammomo wants to merge 1 commit into
mainfrom
tiammomo/protocol/add-codex-responses-parser-fixture

Conversation

@tiammomo

Copy link
Copy Markdown
Owner

Closes #40

Add a route-free, fail-closed Codex Responses request parser and content-free fixture pinned to codex-cli 0.148.0-alpha.21.


Covers all 15 official top-level request-builder fields, observed optional omissions and item IDs, bounded string client metadata, and strict rejection of unsupported multimodal, hosted-tool, structured-output, and unknown shapes. Declares openai-responses and /v1/responses identity but intentionally does not register a route or normalize into Exchange; those remain in #39/#38.

Verified with scripts/check-all.sh.

Areas for careful review:

  • No known behavior changes outside the reported bug.

Implementation assistance: an external coding workspace was used to prepare the change and its
tests. tiammomo reviewed the final diff, understands it, and takes responsibility
for this contribution.

Signed-off-by: tiammomo <pearfl@qq.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add the pinned Codex Responses parser and content-free fixture

1 participant