Skip to content

[Test] gpt-5-nano via Copilot BYOK (responses wire) - #307

Closed
theletterf wants to merge 1 commit into
mainfrom
test/gpt5-nano-byok
Closed

[Test] gpt-5-nano via Copilot BYOK (responses wire)#307
theletterf wants to merge 1 commit into
mainfrom
test/gpt5-nano-byok

Conversation

@theletterf

Copy link
Copy Markdown
Member

Draft — not for merge; sandbox consumes the branch. Same five-issue rubric battery as the #303-#306 series. Two things under test: gpt-5-nano itself ($0.05/M in, $0.40/M out — reasoning-family nano) and the COPILOT_PROVIDER_WIRE_API: responses path, untested until now. OpenAI first-party caching → breaker-safe. Watch item: how the Copilot CLI handles reasoning params over the responses wire via OpenRouter (where codex's fallback metadata famously fumbled it).

🤖 Generated with Claude Code

First exercise of COPILOT_PROVIDER_WIRE_API=responses (required for the
GPT-5 family). OpenAI auto-caching keeps the cache-miss breaker quiet.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Label error. Requires exactly 1 of: automation, breaking, bug, changelog:skip, chore, ci, dependencies, documentation, enhancement, feature, fix. Found:

@theletterf

Copy link
Copy Markdown
Member Author

Battery complete: 5/5 runs green, responses wire validated under Copilot BYOK, rubric 2/5 conformant with calibration-only errors (no off-template behavior). Best budget-tier safety profile so far; scorecard in the skill.

@theletterf theletterf closed this Aug 21, 2026
@theletterf
theletterf deleted the test/gpt5-nano-byok branch August 21, 2026 12:47
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