ClaudeRipple

English · 한국어

Chat stays Claude. Only Code becomes GPT.
Claude Desktop's own setting for other models switches the whole app — chat, phone Remote Control and connectors go with it.
ClaudeRipple turns nothing off: you stay signed in to your Claude subscription while GPT, DeepSeek, Kimi, Grok
or 400+ other models answer in the Code tab. Claude inside the Codex app and Codex CLI too.

_{GPT models under their real names in the Claude Desktop picker}	_{GPT-5.6 Luna answering in the Code tab, at the effort you chose}
_{Subagents on GPT-5.6 Terra and Sol, named in the background-task panel}

1P, not 3P: the difference this whole project exists for

Claude Desktop already ships an official way to use other models — the inference gateway setting, what the app calls third-party or 3P mode. Turning it on is not a per-session choice. It switches the whole app into a different deployment mode at launch, and that mode is a different product:

The window stops loading claude.ai and loads a local bundle instead. claude.ai /api/ and /v1/ calls answer custom_3p_not_available 503.
"Chat" is no longer claude.ai chat. It is a Claude Code local-agent session.
Remote Control and side sessions are switched off outright (shouldEnableSessionsBridge() returns false).
Anthropic's own claude.ai connectors, Claude Design, mobile continuity and chat search go with it.

There is no middle setting. "Chat on Claude, Code on the gateway" is impossible for anyone, because 1P mode routes nothing through the gateway at all. (All of this is read out of the app's own bundle; see docs/ARCHITECTURE.md §2.)

ClaudeRipple never touches that setting. The app stays signed in to your Claude subscription in 1P mode, and another model answers in the Code tab and its subagents — under its real name in the model picker, at the reasoning effort you chose. You do not trade your Claude account for a GPT one. You keep both, in one app.

Three things follow from staying in 1P, and no gateway-based tool can offer any of them:

Code from your phone, on GPT. Remote Control is off in 3P. It is on here, so you can pick a model and send a task from a phone and watch the commits land.
Connectors alive while another model works. 3P stubs claude.ai calls, which takes Anthropic's own connectors with them. Read a Google Drive doc and have GPT write the code.
Cloud and side sessions. Gone in 3P. Untouched here.

If you pay for Claude, 3P is not an option — it throws away the half of the subscription you are paying for. This is the only way to keep it and still choose the model.

FAQ

Can I use GPT in the Claude Desktop app?

Yes — in the Code tab and its subagents. Install ClaudeRipple, sign in with a ChatGPT Plus or Pro subscription, and GPT (GPT-6 Sol, Luna, Astra, GPT-5.6 Terra and the rest) shows up under its real name in the model picker, with the reasoning effort you pick. The app itself is not modified and not switched into any other mode. The general chat tab stays Claude: no tool can route it without turning the whole app into gateway mode (see 1P, not 3P).

How do I use GPT in Claude Code?

The same install covers the terminal claude CLI. ClaudeRipple is a local proxy that Claude Code is pointed at through two lines in ~/.claude/settings.json, so your skills, hooks, MCP servers, CLAUDE.md and subagents keep working while another model answers.

Do I have to turn on Claude Desktop's "third-party inference" (gateway) setting?

No — and you should not. That setting switches the whole app into 3P mode, which stops loading claude.ai, replaces chat with a local-agent session and turns Remote Control off. ClaudeRipple never touches it.

Will I lose claude.ai chat, Remote Control or my connectors?

No. The app stays signed in to your Claude subscription, so chat, phone Remote Control, cloud sessions and Anthropic's own connectors keep working. That is the whole point of staying in 1P.

Can I still use Claude itself?

Yes. Model mapping is per model name: leave a name mapped to Claude and it answers as Claude. Most people map one or two names to GPT and leave the rest alone.

Do I need an OpenAI API key?

No. A ChatGPT Plus or Pro subscription works — you sign in from the app and no API key is involved. API keys are for the other providers (DeepSeek, Kimi, GLM, OpenRouter and anything else with an Anthropic- or OpenAI-compatible endpoint).

Which models can I use?

GPT through a ChatGPT subscription, and DeepSeek, Kimi, GLM, Grok, Qwen and 400+ more through OpenRouter or a direct API key. Claude models keep working as they are.

Does it work on Windows?

Yes, on Windows and macOS, arm64 and x64. Install, dashboard, restart and uninstall are measured on Windows 11 arm64; the x64 runtime is measured under emulation.

Is my code sent anywhere else?

No. The proxy runs on your own machine. Requests go to the provider you configured and nowhere else, and credentials stay in your home directory. See Privacy.

Will my Claude account get banned? Is this against Anthropic's terms?

What ClaudeRipple does with Claude is small and checkable: a request that stays on Claude leaves your machine byte for byte as Claude Code sent it, and a request routed to GPT or another provider never reaches Anthropic at all. It works through the proxy and certificate settings Claude Code documents for corporate networks (HTTPS_PROXY, NODE_EXTRA_CA_CERTS — Enterprise network configuration), not by patching the app. The reports of banned accounts are about the opposite direction — a Claude subscription login used from another program. ClaudeRipple has one optional feature of that kind: Claude inside Codex using your subscription login. That use is subject to Anthropic's terms; an Anthropic API key avoids the question. Rotating several Claude subscriptions is likewise your call under those terms. Only Anthropic can say how an account is treated, so nothing here is a promise.

Can I use several ChatGPT accounts?

Yes. Each clauderipple login (or + Add ChatGPT account in the dashboard) adds one. When an account hits its usage limit, the same request moves to the next account and the spent one rests until its window resets; a conversation stays on the account that answered, to keep its prompt cache. This applies to the Claude Desktop Code tab, Claude Code, and GPT in the Codex app and CLI.

Can I use Claude inside Codex?

Yes. clauderipple codex on adds ClaudeRipple as a provider, and Claude models appear in the Codex app's and CLI's model list under their own names. They answer through your Claude Code login or an Anthropic API key. See Codex app and Codex CLI.

Does GPT do worse inside Claude Code?

Claude Code's system prompt and tool descriptions are written for Claude, so another model reads instructions tuned for someone else, and it may behave a little differently than in its own client. ClaudeRipple tells each model its own name and effort, reshapes tool schemas a vendor would reject, and lets you append instructions per provider. A common setup is Claude as the main model with GPT or DeepSeek as subagents.

How is this different from opencodex or claude-code-router?

See the comparison table (checked 2026-09-16). In short: ClaudeRipple reaches the Claude Desktop Code tab while the app stays signed in to Claude, and shows other models in its picker under their real names.

Is it free?

Yes. ClaudeRipple is open source under GPL-3.0. You pay only for the subscriptions or API keys you already use.

One tool instead of four

Similar tools are built for the terminal. They let the Claude Code CLI or Codex CLI use other models, but they cannot reach the Claude desktop app, and the moment you switch models you lose the Claude-subscription side (claude.ai chat, Remote Control, cloud sessions). ClaudeRipple covers the desktop app, the terminal and Codex from one menu-bar app, runs both subscriptions side by side, and keeps the Claude Code harness intact: your skills, hooks, MCP servers, CLAUDE.md, subagents and claude.ai connectors keep working while another model does the thinking.

	ClaudeRipple	opencodex / openclaude (checked 2026-09-16)	claude-code-router	Claude Desktop gateway (3P) mode
Claude Desktop Code tab without gateway (3P) mode	✅	❌ ¹	❌	❌ by definition
Keeps claude.ai chat, Remote Control, cloud sessions, connectors	✅	❌	❌	❌
Claude and GPT subscriptions side by side	✅	❌ all-or-nothing	❌	❌
Real model names in the Desktop picker	✅	❌	❌	partial
Several ChatGPT accounts, switching when one runs out (Desktop and Codex)	✅	✅	❌	❌
Terminal `claude` CLI	✅	✅	✅	✅
Codex app and Codex CLI → Claude	✅	✅	❌	❌
Prompt cache on translated providers	94–99 % measured	not measured	varies	n/a
Subagents named by real model in the task panel	✅	❌	❌	❌
Settings GUI, no terminal needed	✅	❌	❌	❌
Signed, notarized app with its own runtime	✅	❌	❌	–

¹ opencodex's README showed Claude Desktop in a demo but published no setup steps for it, in the repository or on its documentation site (checked 2026-09-16). At the time the only public way into the desktop app was the official gateway setting — the last column.

The desktop app's own "third-party inference" setting flips the whole app into another mode: you lose claude.ai chat, Remote Control and cloud sessions. Tools that replace ANTHROPIC_BASE_URL never reach the desktop app at all. ClaudeRipple instead is a tiny HTTPS proxy that only the Claude Code process trusts: requests for the models you map go to your provider, everything else goes to Anthropic byte for byte.

What you get

Any model in Claude Desktop and Claude Code. GPT-6 Sol / Luna / Astra and GPT-5.6 Terra / Sol / Luna through your ChatGPT Plus/Pro subscription (new models appear the day OpenAI serves them), or DeepSeek, Kimi, GLM, MiniMax, Qwen, Grok, Mistral, Groq, Together, Fireworks, OpenRouter (400+ models) and local Ollama / LM Studio. Under their real names in the picker, or mapped onto a Claude name.
Claude in the Codex app and Codex CLI. A local OpenAI-compatible endpoint that Codex treats as a provider; Claude models appear in Codex's own model list. Uses your current Claude Code login or an Anthropic API key.
Multiple Claude accounts without breaking the prompt cache. Opt a native Claude provider into account rotation, add subscriptions from the dashboard, and each conversation stays on the account that answered. Before the response starts, a quota or authentication refusal moves that turn to the next account. This native Claude Desktop/Code path is separate from the translated Codex ingress, which picks one available login and does not rotate accounts.
Several ChatGPT accounts. Each clauderipple login (or + Add ChatGPT account in the dashboard) adds one. When an account hits its limit, the next one takes over the same request and the spent one rests until its window resets; a conversation stays on the account that answered, to keep its cache. This covers the Claude Desktop Code tab and subagents and GPT in the Codex app and CLI — Codex keeps its own sign-in and moves to the next account without signing out.
The full Claude Code harness, untouched. Skills, hooks, MCP, CLAUDE.md, subagents, plan mode, Remote Control on your phone: nothing is turned off.
Correct by construction. Prompt caching preserved (Anthropic cache breakpoints and stable OpenAI prefixes), Claude Code's server-side threads handled, tool calls and images round-tripped, reasoning effort clamped to what each model accepts, Anthropic-only request fields stripped for compatible vendors.
A real request log. Who asked, which model answered, tokens in / cached / out, latency, status, per request, with a one-hour summary.
Subagent name tags. The background-task panel shows Terra·high · Review instead of a generic "Agent".
Made for people who don't want a terminal. Provider presets with one-click connection tests and model discovery, drop-down model mapping, auto-save, Korean and English UI. A menu-bar app that carries its own runtime and sets itself up on first launch. Signed and notarized.

Install

macOS

curl -fsSL https://raw.githubusercontent.com/PBJ-2/clauderipple/main/scripts/install.sh | sh

Windows (PowerShell)

irm https://raw.githubusercontent.com/PBJ-2/clauderipple/main/scripts/install.ps1 | iex

That is the whole prerequisite list. The script uses a Node 24+ you already have, and downloads the official build into ~/.clauderipple/runtime when you have none, verifying it against the checksum nodejs.org publishes. Then it sets ClaudeRipple up: a local certificate, two lines in ~/.claude/settings.json, and a background router that starts with your computer. No administrator rights, no password.

With Node already installed you can skip the script:

npm install -g clauderipple
clauderipple install

Then open the dashboard and add a provider:

clauderipple ui

Providers → add ChatGPT or paste an API key → Model mapping.

The menu-bar / tray app is optional. It shows the router's state and opens the dashboard in a click:

clauderipple tray

It runs on Electron, which is about 270MB and is therefore not installed by default. clauderipple tray --install fetches it once; everything else works without it.

Updating.

npm install -g clauderipple@latest
clauderipple restart

Optional, for real names in the Desktop picker: Clients → Claude Desktop → Model picker → on, then quit and reopen Claude Desktop. To trust the local certificate for your user only, macOS asks for your login password and Windows shows a confirmation dialog with the fingerprint — ClaudeRipple never sees a password, and neither platform needs administrator rights.

Closing Claude Desktop's window is not enough. It keeps running, and the next launch reuses it without reading the new setting. Quit it properly (macOS: ⌘Q; Windows: the tray icon, or Task Manager) or the picker will silently not change.

From source (Node 24)

git clone https://github.com/PBJ-2/clauderipple && cd clauderipple && npm install
node packages/cli/src/index.ts install   # certs, settings.json env, supervisor (launchd / Task Scheduler), end-to-end probe
node packages/cli/src/index.ts ui        # open the local GUI in your browser

uninstall reverses everything and restores ~/.claude/settings.json from a backup. Other commands: status, start, stop, restart, logs -f, login, logout, claude-login, claude-logout, picker on|off, agent-title on|off, codex on|off.

Clients

Claude Desktop

Works out of the box after install. Map models on Model mapping (auto-saves), or turn on picker mode to see provider models by name in the app's own picker. Effort chosen in the app is passed through; unsupported levels are clamped.

Claude Code (terminal, Remote Control, subagents)

Same router, same mapping. /model gpt-5.6-terra lists the models you added. Subagents follow the routing; a [[gpt: sol@xhigh]] marker in a subagent prompt overrides the model for that call, and the task panel shows the real model name.

You do not have to build an agent harness for this. Point the subagent slot at a routed model and every subagent runs on it — no agent file, nothing else:

// Settings → CLI models, or "cli": { "models": { … } } in the config
{ "subagent": "gpt-5.6-terra" }   // → CLAUDE_CODE_SUBAGENT_MODEL

Every model you tick is also a named subagent. The router writes ~/.claude/agents/<name>.md for each model exactly one provider carries (gpt-5.6-terra → gpt-5-6-terra, deepseek-v4.1-flash → deepseek-v4-1-flash), so "have DeepSeek do it" needs nothing beyond ticking the model: the Agent tool lists it, subagent_type: "deepseek-v4-1-flash" runs it, and the task panel names it. Untick the model and its file goes away. The router only ever touches the files it wrote (recorded in generated-agents.json); an agent file you wrote yourself under the same name wins and is left alone, so a custom brief is still just Claude Code's own agent file with a model: the router knows:

---
name: reviewer
description: Independent review on GPT-5.6 Sol.
model: gpt-5.6-sol@medium
---
You are the reviewer for this session. Verify the change yourself and report
the conclusion only.

Per-call effort goes on the first line of the subagent prompt: [[ripple: gpt-5-6-terra@high]] — any agent name or model id works there. A marker anywhere else is prose and is ignored (a compaction summary that quotes one must not re-route the session). A model the router cannot place is refused by name (400 ClaudeRipple: no provider declares "…") instead of being sent on to fail somewhere less legible; native Claude models always pass through. Set "cli": { "agentFiles": false } to turn generation off.

Claude Code runs WebSearch as a separate small-model request. To keep a ChatGPT-routed setup from spending Anthropic quota for that request, select the same ChatGPT provider as the search backend in config.json:

{ "webSearch": { "provider": "chatgpt", "model": "gpt-5.6-terra" } }

This is opt-in. With no webSearch setting, Claude Code's existing search path is unchanged.

Codex app and Codex CLI

clauderipple codex on     # adds a "clauderipple" provider to ~/.codex/config.toml (backup first)
codex --profile clauderipple -m claude-sonnet-5

codex on also points Codex's built-in OpenAI provider at ClaudeRipple (openai_base_url). Codex keeps its ChatGPT sign-in; its GPT requests go on to ChatGPT unchanged, except that the account is chosen from the ones added to ClaudeRipple — so with several added, Codex too moves from a spent account to the next. With none added, or all of them at their limit, Codex's own login is used. An openai_base_url you set yourself is left alone. clauderipple codex off undoes it.

Claude models show up in Codex's model list under their names (ClaudeRipple writes a model catalog next to Codex's own). Claude is reached through your Claude Code login (detected from the running Desktop session, the terminal login, or a sign-in of ClaudeRipple's own: Providers → Claude → Connect Claude subscription… opens the browser, no terminal needed; the same as clauderipple claude-login) or an Anthropic API key. Reusing a subscription login is subject to Anthropic's terms. Any Anthropic-compatible provider you configured is available the same way.

Providers

Provider	Kind	Auth	Model list	Notes
ChatGPT subscription	Codex backend	several sign-ins, switching when one runs out (Codex login reused too)	read from your subscription (GPT-6 Sol, Luna, Astra, GPT-5.6 …)	effort low…max (Luna: ultra), prompt cache 94–99 %
OpenRouter	Anthropic-compatible	API key	400+, discovered	per-model effort support read from the API
DeepSeek, Kimi, Z.ai GLM, MiniMax, Qwen (intl / cn)	Anthropic-compatible	API key	preset	verified against vendor docs
xAI Grok, Mistral, Groq, Together, Fireworks	OpenAI-compatible	API key	discovered	translated (Chat Completions / Responses)
Ollama, LM Studio	OpenAI-compatible, local	none	discovered
Anthropic	native	Claude login(s) or API key	Claude models	optional sticky rotation for Claude Desktop/Code; Codex picks one login
Anything else	custom	your choice	discovered	any Anthropic- or OpenAI-compatible endpoint

Requests to compatible providers are cleaned of Anthropic-only fields (server-side threads, deferred tools, context management, thinking bindings) and effort is clamped per model, so vendors do not 400 on Claude Code's request shape.

How it works

Claude Desktop / claude CLI ──HTTPS_PROXY──▶ ClaudeRipple ──▶ api.anthropic.com   (unchanged)
                                               │
                        mapped model ──────────┼──▶ chatgpt.com/backend-api (Responses ⇄ Messages)
                                               ├──▶ Anthropic-compatible vendors (+ compat layer)
                                               └──▶ OpenAI-compatible vendors (Messages ⇄ Chat/Responses)
Codex app / CLI ──/v1/responses──▶ ClaudeRipple ingress ──▶ Claude (your login or API key) / vendors

The Claude Code CLI reads HTTPS_PROXY and NODE_EXTRA_CA_CERTS from ~/.claude/settings.json (Anthropic's documented corporate-proxy path). Only that process trusts ClaudeRipple's local CA; the OS keychain is untouched unless you turn on picker mode.
Picker mode routes the app's own claude.ai traffic through the proxy and adds your models to the picker list the app fetches at start. Off again with one click.
The router drains in-flight calls on restart, self-exits on repeated upstream failures so launchd restarts it, rotates logs, and never drops a request silently.

Details with sources: docs/ARCHITECTURE.md.

Privacy

Everything runs on 127.0.0.1. API keys live in ~/.clauderipple/config.json and added Claude OAuth grants in ~/.clauderipple/claude-accounts.json (both 0600). Admin APIs and logs expose neither tokens nor upstream account ids. The only network destinations are the providers you configure. There is no telemetry.

Status: alpha

In daily use by the author, but young. Expect rough edges:

Windows support is new (2026-09-14). Install, setup, the router, signing in, the picker and a live GPT call are verified on x64 hardware; crash recovery on arm64. The window still has the stock Windows title bar. Windows builds are unsigned; see the note under Install.
ChatGPT, OpenRouter and Claude-in-Codex are verified with live accounts; the other presets follow the vendors' official documentation.
A model added to the picker is usable from the next session.
Claude Code and Codex change their wire protocols often; a client update can break a translation until ClaudeRipple catches up. Bugs and logs welcome.

Not affiliated

ClaudeRipple is an independent open-source project. It is not affiliated with, endorsed by, or sponsored by Anthropic or OpenAI. Claude and Claude Code are trademarks of Anthropic, PBC. ChatGPT and Codex are trademarks of OpenAI.

Name		Name	Last commit message	Last commit date
bin		bin
docs		docs
packages		packages
scripts		scripts
.gitignore		.gitignore
CHANGELOG.md		CHANGELOG.md
CLAUDE.md		CLAUDE.md
LICENSE		LICENSE
README.ko.md		README.ko.md
README.md		README.md
main.js		main.js
package-lock.json		package-lock.json
package.json		package.json
tsconfig.build.json		tsconfig.build.json
tsconfig.json		tsconfig.json

Navigation Menu

Repository files navigation

ClaudeRipple

1P, not 3P: the difference this whole project exists for

FAQ

Can I use GPT in the Claude Desktop app?

How do I use GPT in Claude Code?

Do I have to turn on Claude Desktop's "third-party inference" (gateway) setting?

Will I lose claude.ai chat, Remote Control or my connectors?

Can I still use Claude itself?

Do I need an OpenAI API key?

Which models can I use?

Does it work on Windows?

Is my code sent anywhere else?

Will my Claude account get banned? Is this against Anthropic's terms?

Can I use several ChatGPT accounts?

Can I use Claude inside Codex?

Does GPT do worse inside Claude Code?

How is this different from opencodex or claude-code-router?

Is it free?

One tool instead of four

What you get

Install

Clients

Claude Desktop

Claude Code (terminal, Remote Control, subagents)

Codex app and Codex CLI

Providers

How it works

Privacy

Status: alpha

Not affiliated

License

About

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

ClaudeRipple

1P, not 3P: the difference this whole project exists for

FAQ

Can I use GPT in the Claude Desktop app?

How do I use GPT in Claude Code?

Do I have to turn on Claude Desktop's "third-party inference" (gateway) setting?

Will I lose claude.ai chat, Remote Control or my connectors?

Can I still use Claude itself?

Do I need an OpenAI API key?

Which models can I use?

Does it work on Windows?

Is my code sent anywhere else?

Will my Claude account get banned? Is this against Anthropic's terms?

Can I use several ChatGPT accounts?

Can I use Claude inside Codex?

Does GPT do worse inside Claude Code?

How is this different from opencodex or claude-code-router?

Is it free?

One tool instead of four

What you get

Install

Clients

Claude Desktop

Claude Code (terminal, Remote Control, subagents)

Codex app and Codex CLI

Providers

How it works

Privacy

Status: alpha

Not affiliated

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages