Know What You Are Operating

Claude Code is not merely a chat box that happens to discuss programming. It can inspect files, search a codebase, run commands, edit source, and use connected tools while working toward an outcome. The important shift is that your request can cause changes in a real environment. You are supervising a worker with tools, not collecting an answer to paste somewhere later.

The same product is available through several surfaces, including a terminal, supported IDE integrations, the desktop app, and browser-based sessions. The surface affects where the process runs, which files and credentials are available, and how you review changes. A successful web session is not automatically proof that your laptop changed, and a local edit is not proof that a public deployment changed. Always name the surface and environment before judging a result.

Anthropic currently recommends the native installer for macOS, Linux, and WSL, with Homebrew, WinGet, Linux packages, and npm also documented. Follow the current setup page for your operating system instead of copying an old command from a video. After installation, use the version and doctor commands to distinguish a healthy installation from a shell-path, authentication, settings, or update problem.

Authentication is a separate layer from installation. A binary can be installed correctly while the account, provider, network, or organization policy prevents a session from starting. Never paste an API key into a source file or a prompt. If your organization uses Bedrock, Google Cloud, Microsoft Foundry, or a managed gateway, treat that provider choice as infrastructure configuration rather than something the coding agent should improvise.

The directory from which you start Claude Code determines the initial project scope. Before typing `claude`, identify the exact folder that contains the source you intend to change. People often have a downloaded archive, an old clone, a preview worktree, and the real repository on the same computer. All can look plausible. Only one may be connected to the branch and deployment you care about.

Ask the terminal where you are, then ask Git whether the folder belongs to a repository and whether it already contains changes. If you cannot explain the path, repository root, current branch, and dirty files, pause before editing. This is not ceremony. It prevents a technically correct change from landing in the wrong copy of the project.

If you do not have a project yet, use the practice-project command below instead of downloading a random repository. A terminal prompt waits for a command; pressing Return runs it; the lines that follow are output; and a nonzero exit status means the command did not complete successfully. Read one command and its output at a time. The practice folder gives `pwd`, Git, package scripts, and Claude Code a harmless shared environment without pretending you already know a framework.

Claude Code works through a loop: receive a goal, inspect context, choose a tool, observe the result, update its plan, and continue. Files and command output enter the conversation context as the loop proceeds. That context is finite, so a focused task with relevant evidence usually performs better than one enormous session containing several unrelated goals.

You remain responsible for the boundary and the finish line. Claude can discover implementation details, but it cannot infer which business risk you are willing to accept, which repository is authoritative, or whether a public side effect is appropriate unless you say so. A reliable first request names the outcome, restricts the scope, asks for inspection before edits, and defines a check that can pass or fail.

Begin with a read-only orientation request. Ask what the project does, which technologies it uses, where it starts, and how its own instructions say to verify changes. Compare the explanation with actual files such as the README, package manifest, build configuration, or application entry point. This teaches you to require evidence instead of accepting confident narration.

For the first edit, choose something narrow and reversible: correct one sentence, add one missing validation message, or update a small test fixture. Ask Claude to show the intended files and verification step before changing anything. Afterward, inspect the diff and run the named check. The goal is not to prove that Claude can produce code; it is to practice the full loop from intent to evidence.