Quick answers / Beginner reference
Frequently asked
questions.
Answers to common questions about setup, commands, GitHub, safety, and working at home.
Getting started
Do I need to know how to code?
You can begin by describing a small task in ordinary language. Ask Claude to explain the project before changing it, then inspect the changes and try the result yourself. Start with a practice project so you can learn the workflow.
Official references: Terminal quickstart ↗
Should I use the browser or install Claude Code?
Use the browser for a convenient cloud workspace. Use a local installation when you want to work directly with files and tools on your computer. Both require suitable account access. Your laptop’s files do not automatically appear in a cloud session.
Official references: Cloud environments and sessions ↗
Do I need GitHub?
Not for local work: Claude Code can work in a folder on your computer. The browser walkthrough in this guide uses a GitHub repository. Current CLI cloud workflows also support uploading a local Git repository, subject to documented limits. Git stores project history; GitHub hosts it online.
Official references: Cloud environments and sessions ↗
Is Claude Code free, and do I need an API key?
Installing the tool does not include model usage. Eligible Claude subscriptions and API billing are separate access paths. You do not need an API key when using supported subscription sign-in. Check your account’s current eligibility and billing method before starting.
Official references: Advanced setup ↗
Commands and conversations
Where do I type commands like claude -c or /help?
Type claude -c in your computer’s terminal, outside the Claude Code conversation. Type /help inside Claude Code. Ordinary requests, such as “Explain this file,” belong in the conversation. Read the label above each code example before pasting.
Official references: Terminal quickstart ↗
Why does a slash command not work in the browser?
Command availability varies by interface, version, and installed features. The full terminal reference is not a browser command list. Use the commands your interface offers or describe the result you want in plain language. In the terminal, /help shows available commands.
Browser command alternatives →
Official references: Commands reference ↗
How do I continue an earlier conversation?
In the terminal, run claude -c to continue the most recent conversation in the current directory, or claude -r to choose a previous one. Inside Claude Code, use /resume. For a web task, reopen its existing conversation.
Official references: Terminal quickstart ↗
How do I make Claude remember project instructions?
Put shared project instructions in CLAUDE.md, including the relevant build commands, tests, and coding conventions. Keep them concise and consistent. These instructions guide model behavior; enforce tool restrictions through permission settings.
Official references: Project instructions and memory ↗
Reviewing and protecting your work
Can Claude explain a plan before changing files?
Yes. Select Plan mode and ask it to explain the proposed change. For a local terminal session, start with claude --permission-mode plan. Review the scope before moving to implementation and check which permissions apply to that environment.
Official references: Permissions ↗
Can I undo everything Claude does?
No. Checkpoints can restore supported file edits, but they do not undo all shell-command changes or external actions. Keep Git commits and backups. Stop and inspect the diff before choosing a recovery method, especially when other people share the branch.
Official references: Checkpoints ↗
What should I check when Claude says the task is finished?
Read the diff, confirm the requested behavior, and review the checks that actually ran on the latest changes. Ask what was not tested. For a website, try the affected controls and a narrow screen. Review a pull request before merging.
Official references: Best practices ↗
How do I check usage and avoid surprise spending?
Use the usage information available in your account and /usage where supported. Subscription usage and API token costs are different. For API work, configure the appropriate billing or workspace spend limits. Long sessions, large inputs, and additional agents can increase usage.
Official references: Usage and costs ↗
At home and when things go wrong
Can I run Claude Code completely offline at home?
A local installation runs tools on your machine, but Claude Code requires an internet connection for model access. Hosting your project or execution environment at home does not provide an offline copy of the Claude model.
Official references: Advanced setup ↗
Can I control my home session from a phone or browser?
Remote Control connects a supported browser or mobile interface to a Claude Code session running on your computer. Its tools and file access stay on that machine. The local session needs to remain running and connected for work to continue; check the current account and organization requirements.
Official references: Remote Control ↗
What if my terminal says “claude: command not found”?
Reopen your terminal after installation and try claude --version. Confirm you installed Claude Code in the environment you are using, such as Windows or WSL. Follow the installation troubleshooting steps. Once the command works, claude doctor reports installation and settings diagnostics.
Installation troubleshooting →
Official references: Advanced setup ↗
Why can’t I see my private GitHub repository?
Check which GitHub account is connected and whether the Claude GitHub App has access to that repository. Organization restrictions may require an owner to approve access. Grant only the access needed for your project, then return to repository selection.
Cloud and GitHub troubleshooting →
Official references: Cloud environments and sessions ↗
References
Answers checked against official documentation on September 24, 2026. Features can vary by account, interface, and installed version.
- Anthropic. (n.d.). Terminal quickstart. Retrieved September 24, 2026, from https://code.claude.com/docs/en/quickstart
- Anthropic. (n.d.). Cloud environments and sessions. Retrieved September 24, 2026, from https://code.claude.com/docs/en/claude-code-on-the-web
- Anthropic. (n.d.). Advanced setup. Retrieved September 24, 2026, from https://code.claude.com/docs/en/setup
- Anthropic. (n.d.). Commands reference. Retrieved September 24, 2026, from https://code.claude.com/docs/en/commands
- Anthropic. (n.d.). Project instructions and memory. Retrieved September 24, 2026, from https://code.claude.com/docs/en/memory
- Anthropic. (n.d.). Permissions. Retrieved September 24, 2026, from https://code.claude.com/docs/en/permissions
- Anthropic. (n.d.). Checkpoints. Retrieved September 24, 2026, from https://code.claude.com/docs/en/checkpointing
- Anthropic. (n.d.). Best practices. Retrieved September 24, 2026, from https://code.claude.com/docs/en/best-practices
- Anthropic. (n.d.). Usage and costs. Retrieved September 24, 2026, from https://code.claude.com/docs/en/costs
- Anthropic. (n.d.). Remote Control. Retrieved September 24, 2026, from https://code.claude.com/docs/en/remote-control
Was this chapter useful?
Report an errorVotes are shared only if you enable optional measurement in Privacy settings.