Practical guide · October 30, 2026
Use the Claude or ChatGPT subscription you already pay for inside a desktop app
What works, and what does not, when a desktop app runs on your own Claude Code or Codex CLI sign-in instead of adding another AI bill. Includes how it compares with an API key and a local model.
The second AI bill#
Many people already pay for Claude or ChatGPT. A new AI app usually asks for another subscription or another API bill on top. That is a reasonable thing to resist if the work you want done is something your existing tool could already do.
Growth OX takes the other approach. It includes no AI usage. You connect the AI you already have, and each provider's own terms and prices apply to you. This article explains the three ways to do that and what each one can and cannot do.
Each section below says what works, what does not, and how to check it yourself in the app before you commit to anything.
How the subscription route works#
You install Claude Code or Codex CLI yourself and sign in to it yourself. The sign-in happens in Terminal, and Growth OX never sees your password and keeps no provider token. The app then runs your installed tool for agent jobs such as summaries, reply drafts and document edits, using your subscription.
- Install Claude Code or the Codex CLI.
- In Connections, choose Sign in. A Terminal window opens and the sign-in command runs. For Claude, it opens claude.ai in the browser: sign in with your own account that has a Pro or Max subscription.
- Return to Growth OX. The card reads connected once the sign-in is detected.
If the CLI is signed in with a paid API key instead of the subscription, Growth OX does not use that sign-in; sign in with the subscription. Check your plan's terms about automated use before you rely on it for heavy work.
Subscription, API key or local model#
| Route | What you pay | Notes from the app |
|---|---|---|
| Claude (your Claude Code sign-in) | Your subscription | Best quality. Web research and the Chrome hand-over work with it. Gmail is read through it. |
| Codex (your Codex CLI sign-in) | Your subscription | Runs your own Codex CLI. Gmail is not supported yet. |
| Your own API key | The provider's usage price | Key stored only in the Mac's Keychain. A monthly limit can be set per key. Providers include Anthropic, OpenAI, Gemini, Mistral and others. |
| Local model | Nothing per use | Free, runs on your Mac and sends no text over the internet. Slower and weaker. |
You can use more than one. The app lets you choose which model does which job: chat, drafts, summaries, translation, research.
Check which sign-in the app is using#
Each provider card shows one of four states: connected, not connected, not installed, or status unknown. When a card is connected, the detail line says which kind of sign-in it found, for example signed in with the subscription.
- Not installed: the CLI is missing. Install it, then check again.
- Not connected: the CLI is installed but not signed in. Use Sign in and finish the sign-in in Terminal.
- Signed in with a paid API key: not used. Sign in with the subscription instead.
Which route for which person#
- You already pay for Claude and want Gmail and web research. Use the Claude route. It is the one the app describes as best quality, and Gmail is read through it.
- You pay for ChatGPT and not for Claude. The Codex route runs your own Codex CLI. You lose Gmail for now; the other agent jobs run.
- You want a hard monthly ceiling. Use an API key and set a monthly limit on it. At 80 percent of the limit you get a warning, and at the limit the job stops.
- You work with files you cannot send to a provider. Use a local model for those jobs and keep a provider for the rest. See Privacy.
None of these choices is permanent. You can change which model does which job in Settings at any time.
What does not work, so you do not find out later#
- A subscription login cannot be pasted into the credentials form. A subscription stays on your own computer, in your own sign-in; the credentials form is for API keys.
- Gmail needs Claude. If you sign in only to Codex, the Gmail card will not work for you yet.
- Usage limits come from your provider. When a limit is reached, the job stops and the app shows that the usage limit was reached.
- The provider's plan terms decide what automated use is allowed. Growth OX cannot change them.
If your plans change#
If you cancel the provider subscription, the card for that route stops reading connected, and you can connect another route: an API key or a local model. Your workspace is not tied to a provider. If you do not renew a Growth OX plan, the app keeps working on the last version that plan covered, with all your data; you only stop receiving new versions.
What Growth OX itself costs#
Growth OX is in development and is not on sale yet, so this article states no price. The AI cost stays with your provider. Details on where data goes are on the Privacy page.
Questions#
- Does Growth OX add an AI bill?
- No. It includes no AI usage. You use your own subscription, API key or a local model.
- Does Growth OX see my Claude or ChatGPT password?
- No. You sign in in Terminal. The app never sees your password and keeps no provider token.
- Can I use Claude and Codex together?
- Yes. You can run agents on your ChatGPT-side Codex sign-in instead of or alongside Claude, and pick which model does each job.
- Why does Gmail need Claude?
- Growth OX reads Gmail through the claude.ai connector, read only. Gmail is not supported for Codex yet.
- What if I would rather pay per use?
- Add an API key instead. It is stored in the Mac's Keychain and you can set a monthly limit for it.
- Can I change the model for one job only?
- Yes. You choose which model does each job, for example chat, drafts, summaries, translation or research.
- What if the CLI is not installed?
- The provider card says not installed. Install the CLI, sign in to it, and check again.