ChatGPT Plus ($20/month) or Pro ($200/month) can give OpenClaw access to Codex-backed models through OAuth, but that is not the same thing as unlimited OpenAI API usage. In OpenClaw, API key mode is still usage-based billing, while Codex OAuth uses ChatGPT subscription entitlements that have limits, and heavy Codex usage can spill into paid credits.
I kept seeing the same question pop up in OpenClaw discussions, and honestly, I get why people are confused.
You sign into OpenClaw with your ChatGPT account. You see GPT-5.4 show up. Your agent starts working. For a brief, glorious moment, it feels like you found a cheat code.
No API key. No per-token dread. No watching the meter tick upward every time your agent decides to think a little harder.
And then someone asks the question that ruins the magic: wait, does this mean all my OpenClaw usage is covered by my ChatGPT subscription now?
That exact question showed up in a thread on r/openclaw: "Also wondering if this means all usage will come from the subscription and no additional API usage fees?"
That is the whole mess in one sentence. People are mixing up three different things — ChatGPT subscriptions, Codex OAuth, and OpenAI API billing — and OpenClaw happens to expose all three close enough together that they look like one thing.
They are not one thing.
And that distinction matters a lot once your agent stops being a toy and starts running while you sleep.
The part OpenClaw is actually very clear about
OpenClaw is not hiding this. If anything, its docs are more explicit than most people expect.
There are two separate OpenAI paths in OpenClaw:
- Direct OpenAI API billing using your API key
- ChatGPT/Codex subscription access using OAuth
The setup flows are different:
openclaw onboard --auth-choice openai-api-key
openclaw onboard --auth-choice openai-codex
Or if you already set things up and want to log in later:
openclaw models auth login --provider openai-codex
Even the model paths tell on themselves.
- API usage looks like
openai/gpt-5.4 - Codex subscription-backed usage looks like
openai-codex/gpt-5.4
That little openai-codex/ prefix is doing a lot of work.
It means OpenClaw is not quietly turning your ChatGPT Plus account into a general-purpose OpenAI API plan. It is switching to a different backend and entitlement path.
That sounds subtle. It is not subtle once billing enters the picture.
So what does ChatGPT Plus or Pro actually cover?
Here is the plain-English version.
A ChatGPT Plus subscription, commonly discussed as $20/month, or ChatGPT Pro at $200/month, can include access to Codex. OpenAI’s own help docs say Codex is included with Plus, Pro, Business, and Enterprise/Edu, and for a limited time also with Free and Go. They also say some plans currently get 2x Codex rate limits.
That sounds generous. It is generous.
But it is not the same as saying, “Run unlimited background automation forever.”
OpenAI’s Codex help docs are pretty blunt about what affects your allowance:
- task size
- codebase size
- task duration
- complexity of the work
Small script? Cheap.
Long-running agent wandering through a giant repo every hour? Very different story.
That is why one Reddit comment felt more useful to me than ten official announcements. In this r/openclaw thread, one user said: "I have the 20 and using the oauth but hitting limits if I let it go overnight every hour".
That is the exact failure mode people miss.
Interactive use feels fine. Always-on automation is where the ceiling suddenly becomes real.
Why does Pro feel unlimited to some people and totally not to others?
Because both camps are telling the truth.
While researching this, I found another r/openclaw discussion where a Pro user wrote: "Im on the 200/mo and the only time I hit limits was the first week. I literally have 5 codex cli sessions running all the time".
That sounds almost absurdly good. And for that user, it probably is.
If your work is mostly:
- interactive coding
- bursty sessions
- manual experimentation
- a handful of active agents instead of unattended 24/7 loops
…then ChatGPT Pro via Codex OAuth can feel like a steal compared with raw API billing.
I think that part gets understated by people trying to sound balanced. So I’ll say it plainly: for many solo developers, Pro is probably a fantastic deal.
But “fantastic deal” is not the same as “infrastructure.”
That’s the trap.
A subscription feels like ownership. An always-on agent needs guarantees. Those are different emotional categories, and people keep confusing them because the first one is exciting.
The weird moment when a subscription turns back into metered spend
This is where the story gets almost comically predictable.
The whole appeal of using ChatGPT auth in OpenClaw is escaping per-token billing. Then OpenAI’s own product flow quietly reintroduces usage-based economics the second you push hard enough.
For eligible Plus and Pro users, OpenAI now lets you buy Codex credits when you exhaust included limits. There is even an Add credits button and optional Auto top-up in Codex Settings → Usage.
That detail matters more than any marketing copy.
If a subscription were truly enough for serious unlimited automation, there would be no need for overage credits. The existence of credits is the clearest possible signal: heavy Codex use can spill into metered spend.
So yes, the subscription hack feeling is real at first. I don’t think users are imagining that.
But the product itself is telling you where this goes if your OpenClaw agent graduates from “help me code” to “run every hour forever.”
Which OpenClaw path are you actually on?
This is the comparison I wish more people saw before they started wiring up automations.
| Option | What it really means |
|---|---|
| OpenAI API key in OpenClaw | Billing model: usage-based API billing. Setup: openclaw onboard --auth-choice openai-api-key. Model example: openai/gpt-5.4 |
| OpenAI Codex OAuth in OpenClaw | Billing model: ChatGPT/Codex subscription entitlements, with limits. Setup: openclaw onboard --auth-choice openai-codex. Model example: openai-codex/gpt-5.4 |
| ChatGPT Business standard seats vs Codex seats | Standard seats: fixed monthly cost. Codex seats: usage-based and credit-driven. Can require workspace credits and spend controls |
That last row is the sleeper issue.
Because if you thought teams would make this simpler, absolutely not.
Wait, even ChatGPT Business can bring usage billing back?
Yes. And this is where the “subscription means fixed cost” story really falls apart.
OpenAI’s ChatGPT Business help docs say that starting April 2, 2026, Business supports two seat types:
- standard ChatGPT seats with fixed monthly cost
- Codex seats that are usage-based
And even standard seats may need additional credits for Codex usage.
That means you can be inside a workspace that looks subscription-based and still run into credit balances, spend controls, and usage-based Codex economics.
Which is not evil, by the way. It is just reality.
Codex is closer to compute infrastructure than to ordinary chat. Once people start using it like infrastructure, the pricing model starts acting like infrastructure too.
That’s the part a lot of OpenClaw users are intuitively discovering before they have words for it.
Why did OpenClaw log me out after I finally got OAuth working?
Because auth is the other half of this confusion, and it’s sneakier than billing.
OpenClaw’s OAuth docs explain that tokens are stored locally, refresh tokens can rotate, and logging in through OpenClaw plus another client like Codex CLI can invalidate older refresh tokens.
That is such a specific, annoying failure mode that I immediately believed it.
You sign into OpenClaw. Then you sign into Codex CLI somewhere else. Then one of them mysteriously stops working, and now you’re debugging “limits” when the real issue is token rotation.
OpenClaw even calls its auth-profiles.json approach a “token sink” to reduce the classic problem of: why did one of my tools get logged out?
So when users say OAuth feels flaky, sometimes they are talking about quotas.
Sometimes they are talking about auth state.
And sometimes they are hitting both at once, which is how you end up staring at a terminal at 2 a.m. wondering whether OpenAI charged you, rate-limited you, or just invalidated the wrong refresh token.
The rule I wish more OpenClaw users followed
Here’s my opinionated version.
Use Codex OAuth when your workload is:
- personal
- interactive
- coding-heavy
- bursty
- okay with soft ceilings
Use direct API billing when your workload is:
- unattended
- recurring
- production-like
- multi-agent
- expected to run overnight, every hour, every day
And if your first instinct is, “but I specifically want to avoid API billing,” that is exactly the point.
The confusion is not that people are cheap. The confusion is that ChatGPT subscriptions feel like they should cover more than they actually do once OpenClaw turns into infrastructure.
That mismatch is why so many smart people keep asking the same question on Reddit.
The real answer nobody likes
Yes, ChatGPT Plus or ChatGPT Pro through OpenClaw Codex OAuth can be a brilliant bargain.
No, it does not replace the entire OpenAI API with unlimited subscription usage.
And no matter how magical it feels during the first week, always-on agents eventually force you to care about the thing subscriptions are best at hiding: limits.
That is the weird gap.
Not a bug. Not a scam. Just three different billing and access models standing too close together:
- ChatGPT subscription access
- Codex OAuth entitlements
- OpenAI API usage billing
If you keep those separate in your head, OpenClaw suddenly makes a lot more sense.
If you don’t, your agent will teach you the difference overnight.