Claude Code dey inside Claude Pro? Na so e work

Claude Code dey inside Claude Pro?

Yes. Claude Code dey inside Claude Pro, and e dey inside Max, Team, and Enterprise seats too. So one subscription cover the chat apps and the terminal tool. The free Claude plan no include am. Anthropic setup documentation talk am clearly: Claude Code need Pro, Max, Team, Enterprise, or Console account. The free plan no give access to Claude Code. You only need an API key (application programming interface key, wey dem bill per token) when you no get subscription, or when you want make automated runs get separate billing from your own interactive work.

Na the next part people dey often understand wrongly. Claude Code no get separate usage allowance. E dey use the same subscription usage budget wey your chat conversations dey use. So long coding session fit reduce the chat window wey remain after am. Anthropic talk say both Pro and Max plans get usage limits wey Claude and Claude Code dey share. This mean say all activity for both tools count against the same usage limits.

Wetin each plan really get

• Free: Claude Code no dey inside. You fit chat for web and apps, but nothing go dey for your terminal.
• Pro: Claude Code dey included with Pro usage levels. E cost $20 per month for United States as of August 2026, and annual billing cheaper.
• Max: Na the same Claude Code, but e get bigger usage allowance. E dey come for two tiers wey cost $100 and $200 per month as of August 2026.
• Team and Enterprise: E dey included with the seat. The allowance belong to the seat, and premium seat get more allowance pass standard seat.

Na only these prices dey here, because plan prices fit change and this page no dey update by itself. The current numbers dey for full cost breakdown for Claude Code, while plan-by-plan comparison of the Claude subscriptions explain how to choose between tiers. You fit also check wetin the free Claude tier cover before you assume say you no get option.

Why one coding session dey shorten your chat window

Two windows dey control paid subscription. Session limit dey reset every five hours. Weekly limit dey reset for one fixed time every week wey dem assign to your account, and you fit see your own reset time for usage screen. None of dem be message count wey you fit calculate ahead, because how far you go depend on how long your conversations be and which model you dey run. Treat dem as behaviour to monitor, no be number wey you go budget against. The limit mechanics in detail worth reading once, before you reach one.

Claude Code dey use that budget faster than chat because of wetin coding turn carry. Every request dey send the whole conversation wey don happen so far. Every tool call, file read, or test run dey send another request wey carry the results from the previous one. Anthropic own guidance for administrators talk say make you budget more for coding seat than chat seat for exactly this reason: one debugging session fit use more than one full day of chat.

Prompt caching dey reduce this effect, but e no remove am. Repeated context dey read again at cached rate, so one-line question inside session wey don stay open all day still dey use budget for the entire conversation behind am. Cache lifetime na one hour for subscription. If you comot go lunch, your first message when you return no go find the cache, so your full context go process again at the normal rate. That one message fit cost more than the twenty messages before am.

Practical signs say you dey burn the shared budget

Run /usage inside Claude Code. If you dey on paid plan, e go show usage bars for your plan limits, plus breakdown of wetin dey use dem. Press d for the last 24 hours and w for the last 7 days.

The breakdown go flag any behaviour wey account for 10 percent or more of recent usage, like long context or cache misses. E go also show usage from skills, subagents, plugins, and individual MCP (model context protocol) servers. One important caveat dey. The figures come from local session history for the machine wey you dey use, so work wey you do for another machine or for claude.ai no dey inside the breakdown. The plan bars dey global. The attribution dey local.

When you use finish, the message go name the ceiling wey you reach:

You've hit your session limit
You've hit your weekly limit

Both windows apply across every model, so switching model with /model no go restore access. A model-specific message like You've hit your Opus limit na different matter, and for that case /model go let you continue work with another model. Context warning or auto-compact notice no be usage limit: e mean say the conversation dey near the session context window, and older history go soon become summary. Anthropic cost guidance put context management first, and keeping the context window small get the clearest effect on how fast the budget dey finish. /clear between unrelated tasks costs nothing, and e start the next request with less history to carry. If you don already lose access, the options when a limit is reached na only to wait, upgrade, or turn on usage credits.

How API key fit take over the bill without asking

This one dey cause the biggest wahala for server. If ANTHROPIC_API_KEY environment variable dey set, Claude Code go authenticate with that key instead of your subscription, and dem go bill the work per token to your API account. Your Pro or Max allowance go remain untouched while the invoice dey grow.

For VPS, this one dey happen by mistake more often than for laptop, because the same shell profile usually dey hold keys for other tools. Check am before you start:

printenv ANTHROPIC_API_KEY

If nothing print, no key dey set, so Claude Code go use your subscription. If key print, the next session go bill the API. Clear am for this shell, then find the file wey dey set am:

unset ANTHROPIC_API_KEY
grep -rn ANTHROPIC_API_KEY ~/.bashrc ~/.profile ~/.bash_profile 2>/dev/null

Now start Claude Code and sign in with the subscription account:

claude

The first run go start browser login. Inside session, /login dey switch accounts, and /usage dey confirm which billing account you land on: subscriber go see plan usage bars, while API account go see session block with token costs and no plan bars. The remaining server-side setup, including how to keep session alive after you disconnect, dey covered for running Claude Code on VPS inside tmux, and the permission side dey for running Claude Code safely on server wey you own.

One related trap. When plan allowance finish, you fit turn on usage credits to continue working beyond am, with billing on top of the subscription. Once you dey use credits, prompt cache lifetime dey drop from one hour to five minutes, so the same idle gaps wey used to free now go start cost you. /usage-credits dey open billing settings for Pro or Max subscriber.

Wich one you suppose pay for?

• Occasional or hobby coding: Pro. One tool, one bill, e plenty for some sessions every week. Details of the allowance dey for Pro plan price and im limits.
• Sustained daily coding: Max. If you dey reach the session window most days, the cheaper solution na bigger allowance, no be second account. The choice between the two Max tiers depend on how often you dey reach the weekly limit, instead of the five-hour one.
• Several people: Team or Enterprise seats, where the allowance follow the seat and admin fit see each user spending.
• Bursty or automated runs: API billing. Nightly job or CI (continuous integration) step no need compete with your interactive work for the same allowance.

Those last two cases fit work together well. Keep the subscription for work wey you dey do by hand, and give automation im own API key, so overnight run no go finish the window wey you need the next morning. API and subscription cost comparison explain where the crossover dey.

FAQ

I fit use Claude Code for the free Claude plan?

No. Claude Code need Pro, Max, Team, Enterprise or Console account. Anthropic setup documentation talk say free Claude plan no include Claude Code access, so when you run claude, e go ask you make you sign in to paid account or authenticate with API key instead. Free plan still cover chat for web and desktop apps. This one enough to test whether Claude dey answer your kind question before you pay for anything.

Claude Code dey use the same usage limits like Claude chat?

Yes, for Pro and Max. Anthropic talk say Claude and Claude Code share usage limits, so all activity for both tools dey count against the same limits. Session limit dey reset every five hours, and weekly limit dey reset for fixed time every week wey dem assign to your account. For real use, one afternoon of heavy refactoring fit leave you with short chat window that evening. Run /usage to see the bars and the next reset time.

Why my usage drop fast like this during one coding session?

Because coding turn dey carry much more context pass chat message. Every request dey send the whole conversation, and each tool result dey add another request wey carry the conversation again. Run /usage and read the behaviour flags: anything wey responsible for 10 percent or more of recent usage go get mark, and the usual causes na long context and cache misses. Session wey remain open all day dey keep sending the full history again, and idle gap wey pass the one hour cache lifetime make the next message process everything again at the normal rate. Use /clear between unrelated tasks to solve both problems.

When API key cheaper pass Pro or Max subscription?

When the work dey happen in bursts or na automation. API billing dey charge per token with no monthly minimum, so script wey run twice every week go cost only wetin those tokens cost, and nothing more. Subscription, on the other hand, dey pay for one month capacity wey you no use. If coding dey run every day for long time, subscription better: na fixed price for large allowance, while paying per token for the same volume go cost more. Setting ANTHROPIC_API_KEY for machine wey you also use to code by hand na the mistake to avoid, because Claude Code go bill the API and leave your subscription allowance unused.