Claude Code

Anthropic's terminal-native coding agent. Tops SWE-bench Verified at 87.6% and SWE-bench Pro at 64.3% in 2026. Deep MCP integration, agentic file editing, and a $20/mo Pro tier are the standout signals.

Install via npm: npm install -g @anthropic-ai/claude-code. Requires Node.js 18+. Authenticate: claude login (opens browser for Anthropic OAuth) or set ANTHROPIC_API_KEY environment variable. Claude Code is an agentic terminal coding tool from Anthropic that uses Claude as its reasoning engine. Run in your project directory: cd /path/to/project && claude. It opens a terminal-based conversational interface. Describe what you want: "Add TypeScript types to the auth module and write tests." Claude Code explores your codebase, plans the work, asks clarifying questions, and then edits files, runs commands (with your permission), and iterates on failures. It has internal tools for file reading/writing, glob/grep search, terminal execution, and web fetching. Verify: claude --print "What is in this directory?". Claude Code works with repos of any size — it uses a compact representation of the project structure rather than loading every file into context. Time-to-first-action: ~20 seconds including Claude API latency. The tool uses the Anthropic API and costs per-request based on context size.

Best for: complex multi-file engineering tasks requiring reasoning (refactoring across modules, implementing non-trivial features from scratch, debugging cascading failures), greenfield project generation where you describe the architecture and Claude Code builds it, codebase exploration and analysis ("explain how auth flows through this codebase"), developers willing to trade API cost for engineering velocity, Anthropic ecosystem users already using Claude for code tasks who want an agentic wrapper. Not suited for: offline or air-gapped environments (requires Anthropic API), budget-constrained frequent use on large codebases (costs can be $10–100+/day), simple autocomplete preferences (use GitHub Copilot), non-Anthropic LLM preference (Claude Code is Claude-only), JetBrains IDE users wanting in-IDE integration.

Use Claude Code when you want the most capable autonomous AI coding agent powered by Claude's reasoning — it handles complex multi-file refactors, greenfield generation, and debugging with less hand-holding than any other tool. Switch to Aider when you prefer explicit git-diff-based collaboration with any LLM provider — Claude Code is Claude-only and more autonomous. Use Cline when you want an IDE-integrated agent inside VS Code — Claude Code is terminal-native. Use Cursor for an AI-native IDE with built-in completions, chat, and agent features — Claude Code is a dedicated agentic terminal tool. Use Continue for lightweight IDE chat and inline completions. Claude Code's strengths: reasoning quality (Claude outperforms most models on complex engineering tasks), tool-use sophistication, and the ability to self-correct when commands fail. Its weakness: Claude API costs can be significant on large codebase sessions, and it requires internet connectivity (Anthropic API) — no local model support.

Problem: Error: ANTHROPIC_API_KEY not set. Fix: Run claude login for browser-based OAuth (stores credentials locally) or export the key: export ANTHROPIC_API_KEY=sk-ant-.... The API key is per-organization/workbench in Anthropic Console. For multiple orgs, use ANTHROPIC_API_KEY=sk-ant-org1-... claude. Problem: Claude Code makes changes you didn't intend across many files. Fix: Claude Code has a permission model (default is semi-autonomous with confirmations for terminal commands). Toggle "Ask Mode" in settings prompt for read-only consultation. Use explicit scope boundaries: "In the src/auth/ directory only, refactor..." Problem: High API costs on long sessions. Fix: Claude Code caches the project structure and file contents in context. Use /compact command mid-session to prune context. Start new sessions for unrelated tasks. The per-session cost correlates with files read + conversation turns, not session duration. Use --no-sandbox sparingly — sandbox mode limits tool scope and reduces token consumption.