Before installing
Confirm your actual location meets Claude’s availability rules, your account can sign in and your plan or organization includes Claude Code. Requirements and supported systems can change. Read the official setup guide and select the macOS, Linux, Windows or WSL instructions that match your device.
Use a computer and terminal you control. Keep the operating system and browser current; an unverified “anti-ban installer” is not part of the official setup.
Install and authorize
- Use the installation command from the current official documentation for your system.
- Run
claude --versionto confirm the CLI is available. - Open a project you are authorized to work on, run
claude, and follow the browser sign-in for your own account. - Start with a simple read-only task and grant file or command permissions only as needed.
Browser OAuth and Console API credentials are separate paths. Do not share callback URLs, one-time codes, API keys or session files.
When setup fails
Run claude doctor and save the diagnostic output. If the command is missing, recheck the official install steps and terminal path. If browser authorization fails, confirm the official login page loads, the device clock is correct and Claude status is normal. See official troubleshooting.
An account suspension needs the appeal route; an identity prompt needs the official Persona flow. Replacing device identifiers does not resolve either.
Frequently asked questions
What is the current Claude Code install command?
Use the command in the official Claude Code setup guide for your operating system; commands and requirements can change.
What if the claude command is missing?
Check the official installation and terminal path, then use claude doctor or the troubleshooting guide.
Should I replace my device when Claude Code sign-in fails?
No. Read the exact error and check browser authorization, time and service status. Account restrictions require official review.