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.

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.

¹ opencodex's README shows Claude Desktop in a demo but publishes no setup steps for it,
in the repository or on its documentation site (checked 2026-09-16). The only public way
into the desktop app is 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-5.6 Terra / Sol / Luna and
  GPT-6 Astra through your ChatGPT Plus/Pro subscription, 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 Claude Code login or an Anthropic API key.
• 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.

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.

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

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

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
(0600). 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.

License

Copyright (c) 2026 pbj. GPL-3.0 — see LICENSE. Use it freely; if you distribute a modified
version, ship its source under the same license.