Claude Code

Claude Code is Anthropic’s coding agent for working with software repositories through natural-language instructions. Its full CLI can inspect a codebase, edit files, execute development commands, and assist with Git workflows. Anthropic also offers Claude Code through a VS Code extension, a JetBrains plugin that depends on the CLI, the Claude desktop app, and a browser or mobile surface for remote tasks. Official setup documentation lists macOS, Linux, and Windows, including native Windows and WSL options.

Access is not included in Claude’s free consumer plan. The setup guide requires a Claude Pro, Max, Team, Enterprise, or Anthropic Console account, with additional documented paths through Amazon Bedrock, Google Cloud, and Microsoft Foundry. Subscription plans have usage limits; Console and cloud-provider use can be metered separately. The public GitHub repository is canonical for distribution information and issue tracking, but its license states that use is subject to Anthropic’s Commercial Terms rather than an open-source license.

Top features

• Repository-aware agent that can explain code, edit multiple files, run commands, and verify work with project tools.
• Terminal CLI for interactive sessions, piped input, headless commands, and repeatable automation.
• VS Code integration with inline diffs, file mentions, plan review, and conversation history.
• JetBrains integration with selection context and interactive diffs; a separate CLI installation is required.
• Web, mobile, and desktop access for local or remote coding tasks across several working surfaces.
• Project instructions, skills, subagents, hooks, permission modes, and MCP connections for extending and constraining workflows.
• Git support for examining changes, creating commits and branches, and preparing pull requests under user review.

Use cases

• Trace a bug through an unfamiliar repository, patch the relevant files, and run focused tests.
• Implement a feature from the terminal while following repository-specific instructions and approval rules.
• Review or refactor a multi-file change inside an IDE with visible diffs.
• Connect ticketing, documentation, or internal tools through approved MCP servers.
• Start a longer repository task on the web and review its proposed changes before integration.