Can You Keep Using Claude Code After Returning to Mainland China?
A practical checklist for Claude Code users returning to mainland China, separating installation, authentication, region policy, gateways, and read-only verification without promising a bypass.
An overseas Claude subscription does not settle what happens after returning to mainland China. A recent V2EX question describes an Australian-based developer with an old account, overseas payment, and mostly English prompts, asking whether connectivity is the only remaining issue.
As of November 11, 2026, those conditions do not support a stable-access promise. The thread’s 16 replies suggest jump hosts, roaming data, Cursor, and employer-provided channels; other replies distinguish a proxy from physical presence in a supported region. We have not reproduced those routes.
Check location before changing the shell
Anthropic’s public Supported Regions Policy, marked effective November 12, 2026, includes Claude Code, physical use in unsupported regions, and entity incorporation, headquarters, ownership, or control. Mainland China is absent from the current Help Center location list.
This establishes the published rule, not tomorrow’s enforcement for every account. Overseas payment, an old account, or successful KYC alone does not establish eligibility after returning. Neither an overseas computer nor a gateway should be assumed to be an exception.
Find the failing layer
Start with read-only local checks:
claude --version
claude doctor
For a missing command or local dependency problem, follow the installation documentation. A working CLI does not verify the account or upstream service. Avoid deleting history and reinstalling repeatedly for an account error.
If the screen explicitly names a region or organization restriction, follow account support. For a timeout, record time, destination, and service status rather than automatically calling it a ban.
For an authorized company gateway, inspect active credentials
The current authentication guide distinguishes subscription login, Console, cloud platforms, and organizational gateways. The administrator must still confirm terms and actual working location.
Run /status in the CLI. Inspect Anthropic base URL, credential source, and model. Bearer credentials normally use ANTHROPIC_AUTH_TOKEN; an x-api-key gateway uses ANTHROPIC_API_KEY. Do not configure several credentials and guess which account pays.
The documentation places an environment bearer token ahead of subscription login in ordinary credential selection. Managed policy, cloud selection, and gateway sign-in can change the decision; settings-file values can also override shell values. Confirm the result in /status and contact your administrator for policy restrictions.
The existing setup guide and custom API article contain installation and variable details. This article concerns returning users and existing configuration, not a gateway-based anti-ban method. Do not hand a website session token to a third-party “API conversion” service.
Verify with a public test project
In a temporary project without private files, ask:
Read only the directory structure and tell me the project type. Do not edit files, run write commands, or call external services.
This prompt describes scope; it is not a security control. Keep tool approval enabled. Observe read requests, approvals, and the final answer, then compare the request with your permitted provider’s records.
After text succeeds, test a small approved tool task and its final result separately. One reply does not verify editing, streaming tool arguments, long conversations, or background tasks. We did not execute a real model task for this article.
What to do with community anti-ban advice
An 84-reply discussion offers contradictory views on residential IPs, English prompts, timezone, and telemetry. It contains both long-running accounts and sudden restrictions under superficially similar settings, without controlled comparisons.
Those anecdotes cannot establish a dependable prevention checklist. If the location is unsupported, choose a coding service explicitly available there. Preserve task notes, Git commits, test commands, and unfinished work before changing models. For an already restricted account, follow the appeal and data guide.
