Plans and limits

Every plan of Context Mode has every feature, in Claude Code and Codex. Start free: 1,000 requests, every feature, no card. When your requests run out, nothing breaks: your requests go straight to the model.

The plans

Every feature means Context Saving, Thinking in Code, Protect, Memory, Skills, Search, Session resume, Active Context, Instructions, Live and Analytics, in Claude Code and Codex.

Free

• 1,000 requests, given once when you sign up. They do not come back each month.
• Accounts created before 09:30 UTC on October 6, 2026 keep the 2,000 requests they started with.
• Every feature, in Claude Code and Codex.
• No card.

To start, run npx @context-mode/cli, or sign in to the console. See the quick start.

Pro

• Every feature, in Claude Code and Codex.
• 50,000 requests a month. The count starts again each month, on a yearly plan too.
• Request packs when you need more.
• Pay by the month or by the year.

Request packs

On Pro and Team, a request pack adds 25,000 requests. You buy it in the console and pay first. We never charge you after the fact. A pack's requests are used only after the month's included requests, and they last 12 months.

Auto-reload is off until you turn it on. When it is on, it buys a new pack when your balance runs low, and it stops at a monthly limit you set.

Team and Enterprise

Team gives each seat everything in Pro. The team shares one pool of requests, 50,000 a month for each seat, and its request packs. Admins set one Protect policy for the org, and members cannot loosen it. One bill goes to the team owner. A team has at least 2 seats. Each member's memory stays their own.

Enterprise comes three ways, on a yearly contract:

• Enterprise Cloud: our gateway, with contract terms.
• Enterprise Dedicated: your own gateway, with its own hostname and secrets, in our Cloudflare account.
• In your Cloudflare account: the same gateway, deployed in your account. You hold the data, the keys, the logs and the Cloudflare bill.

There is no on-premises build. For Team or Enterprise, write to sales@context-mode.com.

When your requests run out

Nothing breaks. No request fails because of your plan: not on Free, not at the limit, not when a card fails. Here is what happens.

1. A running session keeps going as it was. A session that started with every feature on keeps them until it ends, within a limit, so your agent's tools do not vanish in the middle of a task.
2. Your next new session starts paused. Its requests go straight to the model, with your own credential. Your agent keeps working, with no error and no refused request.
3. These pause: Context Saving, Thinking in Code, Memory and Skills. The savings ledger stops, and Live shows one row for each request, marked paused.
4. These stay on: Protect’s Core protections. Calls the gateway rewrote earlier in a conversation are put back before the request goes to the model, so the model reads a consistent history. Your stored memory, skills, Protect rules and archive are kept.
5. It comes back on on Free when you move to Pro: the free requests do not come back. On Pro or Team, it comes back on when you buy a request pack or your next month starts. A paused session switches back at its next request.

If we cannot read your plan or your count, you get every feature. If a card payment fails, Pro stays on while the payment is tried again. A problem on our side never stops your agent.

How you are told

Once, clearly, and not on every turn.

• At 80% of your requests: one line in your terminal and one e-mail, once in the month. On Free, once.
• When the pause starts: one line in your terminal and one e-mail. It says that your requests now go straight to the model, what paused, what stays on, and where to resume.
• While paused: a short reminder, at most once per new session and at most once a day. Never on every turn, and never on a subagent's turn.
• In the console: a usage meter on Overview and Billing, and while paused, a bar at the top of each page that you can hide for a day.
• When it is back on: one line in your terminal.

Refunds

Within 14 days of your first Pro payment, or of buying a request pack, you can cancel and get back the part you did not use. The used part is the larger of the time used and the requests used, so you get back only what you did not use. This works once per customer for each product.

The Billing page shows the exact amount, with the days and the requests used, before you confirm. Renewals, later packs and requests after 14 days are not refunded. When you cancel, your plan stops renewing and runs to the end of the period you paid for.