Help
Why Codex still shows my ChatGPT subscription bar
If you open Codex's own Settings while the HaryAI switch is ON, you'll see your ChatGPT subscription quota and a usage bar — exactly as before you installed HaryAI. That looks like double-billing, but isn't. Here's what's actually happening.
TL;DR
While the switch is ON: every Codex request routes through HaryAI's gateway and is billed against your gateway plan. The bar in Codex Settings is read directly from your ChatGPT account by Codex itself — it doesn't know HaryAI exists. As long as you're not running Codex outside HaryAI, that bar will not move; it's just a leftover view.
Why we leave the ChatGPT identity in place
Codex has a set of plugins — computer-use, image_generation, the mcp__codex_apps__* tools, the office runtimes — that are gated on a valid ChatGPT login in ~/.codex/auth.json. Empirically (Codex 0.130) the model-visible tool list shrinks from 18 tools to 12 the moment that identity goes away. So we keep auth.json untouched and instead route requests through a loopback proxy that swaps the Authorization header for your gateway key before forwarding. The result: plugins stay enabled, requests go to the gateway, and Codex itself still sees a valid ChatGPT login on disk — which is what makes it draw the subscription bar in Settings.
How to verify routing is correct
Two places to look:
- The HaryAI popover. The usage section near the top shows your gateway plan and how much of it has been spent this period. If that number moves when you make Codex requests, routing is working.
- The diagnostic dump. Click the wrench icon in the popover footer to open it. The dump prints the effective base URL Codex is configured against (should be http://127.0.0.1:49737/v1) and confirms config.toml carries our managed [model_providers.gateway] block.
When the ChatGPT bar would actually move
Only when something talks to the ChatGPT API outside HaryAI's proxy. The most common case is running Codex from a terminal where you've manually toggled the switch OFF, or running an older Codex session that you opened before turning the switch ON. As long as you toggle the switch ON in HaryAI and then restart your Codex CLI / Desktop / VS Code, every subsequent Codex request goes through the gateway.
If routing actually is off
If the gateway usage bar in HaryAI doesn't move when you make Codex requests, the switch may have drifted (something outside HaryAI reverted config.toml). HaryAI catches this on app start and resets the switch state to match the live file — open the popover, dismiss the recovery banner if present, then toggle the switch ON again. If the problem persists, copy the diagnostic dump and reach out via the contact link in the footer.