Skip to content

Fix Pi judge reasoning effort for Copilot Responses - #893

Merged
pelikhan merged 1 commit into
mainfrom
pelikhan/pi-integration-fix
Nov 21, 2026
Merged

pelikhan merged 1 commit into
mainfrom
pelikhan/pi-integration-fix

Conversation

@pelikhan

Copy link
Copy Markdown
Collaborator

The hosted Pi integration reached the gateway, but the first Rig judge got HTTP 400 because gpt-5.3-codex rejects reasoning.effort: none. Pi SDK 1.5.2 still sends none for the fixture's custom Responses provider when thinking is off.

Map off to low only for gpt-5.3-codex on the fixture's Responses API. The outer Pi session, Chat Completions, and other providers are unchanged. The loopback gateway regression rejects none and checks that all three judges send low through both the launcher and the extension.

Validation: npm test (738 passed) and npm run typecheck. No hosted workflow was dispatched.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@pelikhan
pelikhan marked this pull request as ready for review November 21, 2026 23:44
@pelikhan
pelikhan merged commit 2b1371f into main Nov 21, 2026
5 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🧠 Matt Pocock Skills Reviewer is reviewing this pull request using Matt Pocock's engineering skills...

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.

1 participant