Repository navigation
Run isolated subscription trials without Codex CLI or Pi - #15
Merged
Merged
Conversation
teo-nex
marked this pull request as ready for review
November 16, 2026 20:07
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.
The default clean execution path was tied to installed Pi/Codex clients, including an exact Codex 0.166.0 version check. New studies now select
responses-clean-v1: a Python standard-library adapter calling an explicitly configured Responses gateway. Subscription runs declare provider-qualified routing IDs (for examplecodex/gpt-6.1-terra) instead of ambiguous bare aliases.The adapter preserves fixed task context, unchanged effort labels, lookup execution receipts, stream partials, original attempts, checkpoint locking and route fingerprints. It rejects redirects and unsafe transports, enforces the trial deadline and lookup budget, and does not retry or load personal resources. Existing pinned client profiles remain explicitly selectable with their historical fingerprints. English/Russian setup documentation explains the new default and the gateway boundary.
Validation:
codex/...subscription-provider routing completed; both passed strict and semantic grading. These two smoke trials are not a complete benchmark campaign.The adapter depends on a configured Responses gateway and its provider authentication, not a model CLI. Provider model identity/billing/hidden retries remain gateway-side claims, not independently attested by this client. No study data, credentials, gateway secrets or live receipts are included. GitHub CI for the final head is pending.