Bring an account, not an API key—without pretending the trust boundary disappears.
EasyCLIProxyAPI can expose supported provider accounts through one local OpenAI-compatible endpoint. WebBrain can use that endpoint, but it does not build, audit, distribute, or endorse the proxy executable.
Know which part belongs to whom.
- WebBrain integration
- Local OpenAI-compatible HTTP endpoint only
- Executable and updates
- EasyCLIProxyAPI upstream
- WebBrain audit or warranty
- No
- Safer, stable default
- A provider-issued API key
This is a third-party executable with access to OAuth credentials.
EasyCLIProxyAPI manages provider sign-ins, local credentials, a separately installed CLIProxyAPI core, and its own updates. Review the source and current release, download only from the upstream repository, and verify the release digest where one is provided. WebBrain cannot inspect what a future upstream build does.
Using a local proxy does not make inference local. Page context and prompts still travel to the provider account selected by the proxy. Provider rules can change, and a working OAuth flow does not mean the provider authorizes that flow for every third-party client.
- OpenAI: ChatGPT subscriptions and API billing are separate products. Review the subscription/API distinction and current Terms of Use.
- Anthropic: its consumer terms restrict automated or non-human access except through an API key or another explicitly permitted interface. Review the current Consumer Terms.
- Google: Gemini CLI's terms say its OAuth authentication may not be used with third-party tools or services. Review the current Gemini CLI terms.
- Kimi and xAI: treat upstream OAuth availability as a technical capability, not permission or a compatibility guarantee. Check the terms for your product, plan, region, and account before signing in.
This guide describes a compatibility setup, not legal advice. Your account, data, and compliance decisions remain your responsibility.
What the upstream app currently offers
EasyCLIProxyAPI currently lists five browser-based sign-in routes. These labels describe the upstream app; they are not official WebBrain integrations and may stop working or expose different models without notice.
| EasyCLIProxyAPI label | Account family | WebBrain card that points here |
|---|---|---|
| Codex OAuth | OpenAI / ChatGPT / Codex | OpenAI |
| Claude OAuth | Anthropic / Claude | Anthropic Claude |
| Antigravity OAuth | Google Gemini | |
| Kimi OAuth | Kimi | Kimi |
| xAI OAuth | xAI / Grok | xAI |
All five routes connect to WebBrain through the same Local OpenAI-compatible Proxy card. The direct OpenAI, Anthropic, Gemini, Kimi, and xAI cards remain API-key integrations.
Watch the complete connection once.
The tutorial demonstrates Antigravity OAuth, the loopback endpoint, model discovery, connection testing, Ask, and Act. Interface labels may move in later upstream releases; use the exact endpoint shown by your installed version.
The boundary in one line
The first connection stays on your computer. The second does not. EasyCLIProxyAPI keeps upstream OAuth material outside WebBrain; WebBrain stores only the local proxy client key you enter in Settings.
Connect the local endpoint
- Inspect and install upstream. Download EasyCLIProxyAPI from its GitHub release page. In Version Management, install the matching CLIProxyAPI core.
- Lock the proxy to loopback. Keep the listener on
127.0.0.1, leave LAN access off, and never forward port8317. Replace any short or default client key with a strong random value; the exact control may appear under Advanced Settings or API Access depending on the release. - Authorize only the account you intend to use. Open OAuth, choose Codex, Claude, Antigravity, Kimi, or xAI, and finish the provider page. Stop if the provider presents terms or permissions you do not accept.
- Start the core and copy the OpenAI-compatible URL. On Home, start the runtime and copy the OpenAI endpoint. The common default is
http://127.0.0.1:8317/v1; trust the value displayed by your running version. - Open WebBrain Settings → Providers. Search for Local OpenAI-compatible Proxy. Paste the server URL and the proxy client key—not the provider OAuth token.
- Load and select a model. Click Load Models, select an exposed model, set its real context window, and enable vision only if that exact model accepts images.
- Save, test, then activate. Run Test Connection and require a green success result before selecting the provider for chat. Start with Ask mode on non-sensitive content.
0.0.0.0, a LAN IP, tunnel, or public reverse proxyA local client key is not a safe internet-facing authentication system. Any process that obtains the key can send requests through the signed-in provider account.
Troubleshooting by symptom
| Symptom | Likely cause | What to check |
|---|---|---|
| Connection refused | The CLIProxyAPI core is stopped or the port changed. | Start the runtime, refresh Home, and copy the displayed OpenAI URL again. |
| Unauthorized | The WebBrain key does not match the proxy client key. | Copy the local client key again. Never paste an upstream OAuth token into WebBrain. |
| No models loaded | OAuth did not finish, the account exposes no compatible model, or upstream support changed. | Check the OAuth/account status and EasyCLIProxyAPI logs, then review its current release notes. |
| Text works but images fail | The selected alias does not accept image input. | Turn vision off or choose a model the proxy reports as vision-capable. |
| Quota or account error | The upstream account, plan, region, or provider policy rejected the request. | Stop retrying, inspect the provider account directly, and use an official API key when available. |
| Unexpected models or behavior after an update | The desktop app, core, plugin, or provider contract changed. | Compare versions, inspect release notes, and re-run Load Models and Test Connection. |
What WebBrain deliberately does not do
- It does not bundle, launch, update, or verify EasyCLIProxyAPI or CLIProxyAPI.
- It does not receive or manage upstream OAuth refresh tokens.
- It does not promise that a consumer subscription includes API-like or automated access.
- It does not bypass provider quotas, regional restrictions, account reviews, or terms.
- It does not make remotely hosted inference private or on-device.