Add chatgpt-web provider: route ChatGPT Web models via codex-chatgpt-web bridge - #876
Add chatgpt-web provider: route ChatGPT Web models via codex-chatgpt-web bridge#876GENEXIS-AI wants to merge 1 commit into
Conversation
…web bridge Register codex-chatgpt-web (github.com/miuuyy/codex-chatgpt-web) as a provider in the opencodex registry. Users can add it from the dashboard or CLI and route ChatGPT Web Instant–Pro models through the local browser bridge without an API key. The provider uses the openai-responses adapter (codex-chatgpt-web speaks the Responses API natively on loopback port 17841). Live model discovery fetches the actual catalog from the running bridge. Provider entry: - id: chatgpt-web - adapter: openai-responses - baseUrl: http://127.0.0.1:17841/v1 - authKind: local (loopback, no key required) - liveModels: true - models: chatgpt-web/{light,medium,high,extra-high,pro}
|
✅ PR quality gates passed This pull request now targets The |
github-actions
Bot
changed the title
📝 WalkthroughWalkthroughThe provider registry adds a ChangesChatGPT Web provider
Estimated code review effort: 3 (Moderate) | ~15 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Comment |
github-actions
Bot
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 148ea4bb7c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| label: "ChatGPT Web (codex-chatgpt-web)", | ||
| baseUrl: "http://127.0.0.1:17841/v1", | ||
| adapter: "openai-responses", | ||
| authKind: "local", |
There was a problem hiding this comment.
When a user opens the dashboard's Add Provider catalog, this entry is absent because deriveProviderPresets() includes only featured, key-auth, or dashboardPreset entries, while this provider is local and sets neither flag. Add dashboardPreset: true (or intentionally make it featured) so the new provider can actually be selected from the dashboard.
AGENTS.md reference: src/AGENTS.md:L18-L18
Useful? React with 👍 / 👎.
| allowBaseUrlOverride: true, | ||
| keyOptional: true, |
There was a problem hiding this comment.
With this entry present, tests/provider-registry-parity.test.ts deterministically fails: its optional-key assertion at line 444 does not include chatgpt-web, and its base-URL-override assertion at line 487 does not include it either. Remove the redundant keyOptional flag if local auth already expresses the intended behavior, and update the override invariant plus focused provider coverage so bun run test remains green.
AGENTS.md reference: src/AGENTS.md:L24-L26
Useful? React with 👍 / 👎.
| "chatgpt-web/extra-high": ["text", "image"], | ||
| "chatgpt-web/pro": ["text", "image"], | ||
| }, | ||
| dashboardUrl: "https://github.com/miuuyy/codex-chatgpt-web", |
There was a problem hiding this comment.
This provider requires a separately installed loopback bridge, but the repository-wide docs search finds no chatgpt-web setup instructions, and docs-site/src/content/docs/guides/providers.md still lists only Ollama, vLLM, and LM Studio under local providers. Add the bridge installation/startup steps, the supported CLI setup command, and the default endpoint to the English provider guide, keeping translated guides from contradicting it.
AGENTS.md reference: AGENTS.md:L192-L193
Useful? React with 👍 / 👎.
| keyOptional: true, | ||
| }, | ||
| { | ||
| id: "chatgpt-web", |
There was a problem hiding this comment.
The reviewed commit is based directly on 88589c9 (release: v2.9.1) rather than the integration line, and its own subject marks it [WRONG BRANCH]. Rebase or recreate this change on dev before opening or merging it so the feature does not bypass the repository's single integration branch and current development changes.
AGENTS.md reference: AGENTS.md:L177-L178
Useful? React with 👍 / 👎.
|
형님 죄송합니다 웹브릿지는 진짜 좆될것 같아요 |
2 participants
Summary
Register codex-chatgpt-web as a provider in the opencodex registry. Users can add it from the dashboard or
ocx account add-key chatgpt-weband route ChatGPT Web Instant–Pro models through the local browser bridge — no API key required.Provider entry
How it works
openai-responsesadapter forwards requests directly — no translation neededliveModels: truefetches the actual catalog from the running bridge (includes Pro when the account has it)authKind: "local"+keyOptional: true: loopback bind requires no credentialallowBaseUrlOverride: true: users can change the port if neededCompanion PR
This pairs with miuuyy/codex-chatgpt-web#21 which adds the reverse direction: codex-chatgpt-web routing its native passthrough through opencodex for multi-provider access.
Testing
getProviderRegistryEntry("chatgpt-web")Summary by CodeRabbit