Claude Code.
Ask Claude to trace a bug across a repository, propose a patch, or edit the files you approve.
When to use it
Use Claude Code when the task begins with a question about an existing codebase. Open it in the project directory and give it a failing test and the expected behavior. You can review a proposed diff first, or grant editing and command permissions for a hands-on session.
- Maintainer
- Anthropic
- Access and cost
- Sign in with an eligible Claude subscription, an Anthropic Console account with API billing, or a supported cloud provider. Usage allowances and charges depend on that choice.
- Software terms
- Anthropic’s applicable service terms govern use of Claude Code. See the license linked below.
Installation
Choose an installer for your operating system. After installation, open a terminal in a project folder and run claude. Follow the sign-in prompt, then ask it to explain a file before approving changes.
- macOS · Native installer or Homebrew
- Linux · Native installer and package-manager options
- Windows · Native Windows setup
- WSL · Linux installation inside WSL
On macOS with Homebrew
brew install --cask claude-code
Check the installed version with
claude --version
Field test
Fix a missing field without changing the tests
A two-line Python function filtered catalog records by an enabled flag. One record had no flag. We gave Claude read access to the function and its three tests, and asked for a unified diff. It returned one changed line.
- if item["enabled"]
+ if item.get("enabled", False)
We applied the returned patch with git apply in a fresh copy and ran Python’s unittest runner. All three cases passed: an empty list, a mix of enabled and disabled records, and a missing flag. Our runner applied the change; Claude supplied the patch.
Primary sources
Checked .