Is Claude Code included with Claude Pro?

Is Claude Code included with Claude Pro?

Yes. Claude Code is included with Claude Pro, and with Max, Team and Enterprise seats as well, so one subscription covers the chat apps and the terminal tool. The free Claude plan does not include it. Anthropic's setup documentation is explicit: Claude Code requires a Pro, Max, Team, Enterprise or Console account, and the free plan does not include Claude Code access. You need an API key (application programming interface key, billed per token) only when you have no subscription, or when you want automated runs billed separately from your own interactive work.

The part people get wrong comes next. Claude Code has no separate allowance of its own. It spends the same subscription usage budget your chat conversations spend, so a long coding session shortens the chat window that follows it. Anthropic states that both Pro and Max plans offer usage limits that are shared across Claude and Claude Code, meaning all activity in both tools counts against the same usage limits.

What each plan actually gets

• Free: no Claude Code. Chat on the web and in the apps, nothing in your terminal.
• Pro: Claude Code included at Pro usage levels. $20 per month in the United States as of August 2026, lower on annual billing.
• Max: the same Claude Code with a larger share of usage, in two tiers at $100 and $200 per month as of August 2026.
• Team and Enterprise: included with the seat. The allowance belongs to the seat, and a premium seat carries more of it than a standard seat.

Those are the only prices here, because plan prices move and this page does not. The current numbers live in a full cost breakdown for Claude Code, the choice between tiers is worked through in a plan by plan comparison of the Claude subscriptions, and what the free Claude tier does cover is worth checking before you assume you are stuck.

Why one coding session shortens your chat window

Two windows govern a paid subscription. A session limit resets every five hours. A weekly limit resets at a fixed time each week that is assigned to your account, and you can see your own reset time in the usage screen. Neither is a message count you can calculate in advance, because how far you get depends on how long your conversations are and which model you run. Treat them as behaviour to watch, not as a number to budget against. The limit mechanics in detail are worth reading once, before you hit one.

Claude Code drains that budget faster than chat because of what a coding turn carries. Every request sends the whole conversation so far. Each tool call, a file read or a test run, sends another request carrying the results of the previous one. Anthropic's own guidance for administrators says to budget more for a coding seat than a chat seat for exactly this reason: one debugging session can consume more than a day of chat.

Prompt caching softens this and does not remove it. Repeated context is re-read at a cached rate, so a one-line question inside a session that has been open all day still draws usage for the entire conversation behind it. The cache lifetime is one hour on a subscription. Step away for lunch and your first message back misses the cache, which means your full context is processed again at the normal rate. That one message can cost more than the twenty before it.

The practical signs you are burning the shared budget

Run /usage inside Claude Code. On a paid plan it draws usage bars for your plan limits, with a breakdown of what has been spending them. Press d for the last 24 hours and w for the last 7 days.

The breakdown flags any behaviour responsible for 10 percent or more of recent usage, such as long context or cache misses, and it attributes usage to skills, subagents, plugins and individual MCP (model context protocol) servers. One caveat matters. Those figures are computed from local session history on the machine you are sitting at, so work you did on another machine or on claude.ai is not in the breakdown. The plan bars are global. The attribution is local.

When you run out, the message names which ceiling you hit:

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

Both of those windows apply across every model, so switching model with /model does not give you access back. A model-specific message such as You've hit your Opus limit is a different thing, and there /model does keep you working, on another model. A context warning or an auto-compact notice is not a usage limit at all: it means the conversation is near the session's context window and older history is about to be summarised. Anthropic's cost guidance puts context management first, and keeping the context window small has the clearest effect on how fast the budget drains. /clear between unrelated tasks costs nothing and starts the next request with less to carry. If you are already locked out, the options when a limit is reached are limited to waiting, upgrading, or turning on usage credits.

Why an API key can take over the bill without asking

This one bites hardest on a server. If the ANTHROPIC_API_KEY environment variable is set, Claude Code authenticates with that key instead of your subscription, and the work is billed per token to your API account. Your Pro or Max allowance sits untouched while the invoice grows.

On a VPS this happens by accident more often than on a laptop, because the same shell profile usually holds keys for other tools. Check before you start:

printenv ANTHROPIC_API_KEY

Nothing printed means no key is set, so Claude Code will use your subscription. A key printed means the next session bills the API. Clear it for this shell, then find the file that keeps setting it:

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 starts a browser login. Inside a session, /login switches accounts and /usage confirms which billing you landed on: a subscriber sees plan usage bars, while an API account sees a session block of token costs and no plan bars. The rest of the server-side setup, including how to keep a session alive after you disconnect, is covered in running Claude Code on a VPS inside tmux, and the permission side of it in running Claude Code safely on a server you own.

One related trap. When the plan allowance runs out, you can turn on usage credits to keep working past it, billed on top of the subscription. Once you are drawing on credits the prompt cache lifetime drops from one hour to five minutes, so the same idle gaps that used to be free start costing you. /usage-credits opens the billing settings for a Pro or Max subscriber.

Which one should you pay for?

• Occasional or hobby coding: Pro. One tool, one bill, enough for a few sessions a week. Details of the allowance are in the Pro plan price and its limits.
• Sustained daily coding: Max. If you hit the session window most days, the cheaper fix is a bigger allowance, not a second account. The choice between the two Max tiers comes down to how often you hit the weekly limit rather than the five-hour one.
• Several people: Team or Enterprise seats, where the allowance follows the seat and an admin can see spend per user.
• Bursty or automated runs: API billing. A nightly job or a CI (continuous integration) step has no reason to compete with your interactive work for the same allowance.

Those last two cases mix well. Keep the subscription for the work you do by hand, and give automation its own API key, so an overnight run cannot empty the window you need the next morning. The API and subscription cost comparison works through where the crossover sits.

FAQ

Can I use Claude Code on the free Claude plan?

No. Claude Code requires a Pro, Max, Team, Enterprise or Console account. Anthropic's setup documentation states that the free Claude plan does not include Claude Code access, so running claude will ask you to sign in to a paid account or to authenticate with an API key instead. The free plan still covers chat in the web and desktop apps, which is enough to test whether Claude answers your kind of question before you pay for anything.

Does Claude Code use the same usage limits as Claude chat?

Yes on Pro and Max. Anthropic states that usage limits are shared across Claude and Claude Code, so all activity in both tools counts against the same limits. A session limit resets every five hours, and a weekly limit resets at a fixed time each week that is assigned to your account. In practice an afternoon of heavy refactoring can leave you with a short chat window that evening. Run /usage to see the bars and the next reset time.

Why did my usage drop so fast during one coding session?

Because a coding turn carries much more context than a chat message. Every request sends the whole conversation, and each tool result adds another request that carries it again. Run /usage and read the behaviour flags: anything responsible for 10 percent or more of recent usage is marked, and the usual culprits are long context and cache misses. A session left open all day keeps re-sending its full history, and an idle gap longer than the one hour cache lifetime makes the next message reprocess everything at the normal rate. Using /clear between unrelated tasks addresses both.

When is an API key cheaper than a Pro or Max subscription?

When the work is bursty or automated. API billing charges per token with no monthly floor, so a script that runs twice a week costs what those tokens cost and nothing more, while a subscription pays for a month of capacity you never use. Sustained daily coding runs the other way: a subscription is a fixed price for a large allowance, and paying per token for that same volume costs more. Setting ANTHROPIC_API_KEY on a machine where you also code by hand is the mistake to avoid, because Claude Code then bills the API and leaves your subscription allowance unused.