Claude Code
Anthropic's terminal coding agent for migrations, bug fixes and refactors.
Group: Coding agents
Claude Code reads repositories, edits files, runs commands and connects development tools through terminal, IDE, desktop and web surfaces. Its current security docs describe Auto mode as the starting mode for interactive terminal and VS Code sessions, while Manual, Plan and other modes change approvals. Local execution does not mean code and prompts stay offline.
The decision in plain English
Start from the actual permission mode, repository rules and account data settings, not the older claim that every edit asks first. Use a branch and your own tests. Optional sandboxing gives different boundaries from a prompt-only working directory; installed extensions and cloud sessions need separate review.
Best fit
Developers delegating repository changes from a terminal.
Poor fit
A no-setup personal assistant for errands.
Documented capabilities
Vendor statements, not verified task outcomes.
- Repository work: Reads a codebase, edits multiple files, runs tests/commands and documents bugs or features. Generated code still needs review and your test suite. Source · checked 2026-10-22
- Git and CI: Branches, commits and pull requests; GitHub Actions and GitLab CI/CD for reviews/triage. A repository change is not automatically a safe merge. Source · checked 2026-10-22
- Where it runs: Terminal, VS Code/JetBrains, desktop and web. Local CLI and Anthropic-hosted cloud sessions have different environments; do not assume local sessions run in a cloud sandbox. Source · checked 2026-10-22
- Default approvals: Security docs say Auto is the starting mode for interactive terminal and VS Code sessions. A classifier reviews actions instead of routine human prompts; explicit ask/deny rules still apply. Source · checked 2026-10-22
- Permission modes: Manual asks for edits and non-read-only commands; acceptEdits permits edits/common filesystem work; plan avoids source edits; dontAsk denies calls needing prompts; bypass skips most prompts and belongs only in isolated environments. Source · checked 2026-10-22
- Rules and extensions: Deny, ask, allow precedence is documented, but installed mods can replace some decisions depending on plan/managed policy. CLAUDE.md instructions do not enforce permissions. Review plugins, hooks and mods. Source · checked 2026-10-22
- MCP and custom workflows: MCP connects apps such as Drive, Jira and Slack. Instructions, skills, hooks and parallel agents extend work, but connection credentials/scopes need separate review. Source · checked 2026-10-22
- Filesystem/network isolation: Use sandboxing for OS-level filesystem/network limits. Working-directory approval prompts alone do not stop an approved shell command from writing elsewhere under your user account. Source · checked 2026-10-22
Permissions and human control
- Tiered permission modes re-verified 22 October 2026: plan (read-only explore), auto (runs without routine prompts; a background classifier checks actions against your request), acceptEdits, dontAsk (auto-denies anything that would prompt) and manual. Deny/ask/allow rules apply with documented precedence.
- 'Yes, and don't ask again' approvals save as rules to .claude/settings.local.json at the repository root and apply across future sessions and worktrees in that repo; file-edit approvals last only for the session.
- Feedback surveys and nonessential traffic can be disabled (CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY, DISABLE_TELEMETRY, DO_NOT_TRACK); organisations can route survey ratings through their own OpenTelemetry collector.
- Filesystem/network isolation beyond the permission system needs OS-level sandboxing; MCP connectors (Drive, Jira, Slack and others) follow their own scopes.
Documented controls do not prove that an agent always follows them.
Limits and open questions
- No code-quality, success-rate or permission-enforcement test was run. Benchmarks are not a product comparison.
- Old ask-before-every-edit summary only describes Manual behavior, not today's documented Auto starting mode. Surface, version, saved rules, hooks and mods matter.
- MCP connections and approved shell commands may disclose data or change external systems; a local tool is not an offline tool.
- Subscription limits are shared with other Claude use; API and third-party provider charges are separate. No fixed tasks-per-dollar guarantee.
- No region eligibility, numeric Max-tier allowance or exact team-seat total confirmed here. Check chosen plan and billing route.
Privacy and security
Re-verified 22 October 2026 against Claude Code's data-usage doc and Anthropic's privacy policy (effective 10 September 2026). Consumer Free/Pro/Max: training happens only when the voluntary model-improvement setting is on (applies to Claude Code use from those accounts); retention is 5 years with the setting on, 30 days with it off. Commercial (Team, Enterprise, API, third-party platforms, Gov): no training on code or prompts unless the customer opts in (e.g. Developer Partner Program, first-party API only); standard retention 30 days; zero data retention available per-organisation for eligible Enterprise accounts, not by default. Local CLI transcripts are stored in plaintext under ~/.claude/projects/ for 30 days by default (cleanupPeriodDays adjustable; Desktop/Cowork sessions exempt). /feedback, /bug and /share transcripts are retained 5 years; nothing is sent until you choose. Individual cloud sessions can be deleted at any time, permanently removing their event data. Vendor documentation, not independently audited.
Feature-by-feature: what is documented and what is not
Official sources checked 22 October 2026. A documented feature is a vendor statement, not proof of success.
| Feature | Evidence status | Detail and limit |
|---|---|---|
| Repository work | Documented | Reads a codebase, edits multiple files, runs tests/commands and documents bugs or features. Generated code still needs review and your test suite. Source |
| Git and CI | Documented | Branches, commits and pull requests; GitHub Actions and GitLab CI/CD for reviews/triage. A repository change is not automatically a safe merge. Source |
| Where it runs | Surface-dependent | Terminal, VS Code/JetBrains, desktop and web. Local CLI and Anthropic-hosted cloud sessions have different environments; do not assume local sessions run in a cloud sandbox. Source |
| Default approvals | Current correction | Security docs say Auto is the starting mode for interactive terminal and VS Code sessions. A classifier reviews actions instead of routine human prompts; explicit ask/deny rules still apply. Source |
| Permission modes | Configurable | Manual asks for edits and non-read-only commands; acceptEdits permits edits/common filesystem work; plan avoids source edits; dontAsk denies calls needing prompts; bypass skips most prompts and belongs only in isolated environments. Source |
| Rules and extensions | Scope matters | Deny, ask, allow precedence is documented, but installed mods can replace some decisions depending on plan/managed policy. CLAUDE.md instructions do not enforce permissions. Review plugins, hooks and mods. Source |
| MCP and custom workflows | Documented | MCP connects apps such as Drive, Jira and Slack. Instructions, skills, hooks and parallel agents extend work, but connection credentials/scopes need separate review. Source |
| Filesystem/network isolation | Optional control | Use sandboxing for OS-level filesystem/network limits. Working-directory approval prompts alone do not stop an approved shell command from writing elsewhere under your user account. Source |
| Training and storage | Account-dependent | Consumer training follows privacy setting: enabled data retained 5 years, disabled 30 days. Commercial code/prompts are not trained on unless opted in; standard retention 30 days. Enterprise ZDR requires eligibility and explicit enablement. Source |
| Local logs and feedback | Separate risks | CLI local transcripts are plaintext, normally 30 days; Desktop/Cowork continuation exceptions apply. Feedback/bug/share reports retained 5 years; optional survey transcript sharing has different 6-month terms. Source |
| Price/access | Published with limits | Pro $20 monthly or $200 annually includes Code; Max starts $100/month. Free plan table excludes Code. Console API/provider billing and team eligibility are separate; limits and taxes apply. Source |
How to start with Claude Code narrowly
- Choose terminal/IDE/desktop/web from the official overview and check account eligibility before installing. Do not assume the Free chat plan includes Code.
- Use a version-controlled test repository or branch. Read the install route for your operating system; review the installer rather than blindly running a copied command.
- Inspect the actual starting mode and /permissions, including persistent repository rules. Start with Manual or Plan when you want hands-on review; use OS sandboxing for real file/network boundaries.
- Connect only needed MCP tools; inspect project instructions, hooks/plugins/mods before trusting a repository. Do not add production credentials to a test task.
- Ask for one small change, review its diff and run your own tests before committing or merging. Check privacy settings, local logs, and subscription/API cost afterwards.
Official product/setup source. These are documentation-based steps, not a hands-on setup test.
Common questions about Claude Code
What is Claude Code for?
Developers delegating repository changes from a terminal. The vendor describes it as: Claude Code reads repositories, edits files, runs commands and connects development tools through terminal, IDE, desktop and web surfaces. Its current security docs describe Auto mode as the starting mode for interactive terminal and VS Code sessions, while Manual, Plan and other modes change approvals. Local execution does not mean code and prompts stay offline.
Who should look elsewhere?
A no-setup personal assistant for errands.
How much does Claude Code cost?
Anthropic renamed its paid individual tiers: Pro (1x limits, includes Claude Code), Max (5x Pro on 5-hour and weekly windows, $100/month Claude Platform API credits included) and Ultra (no 5-hour limit for verified accounts, 10x Pro weekly, $200/month API credits included). GBP pricing page view 31 October 2026: Pro GBP15/month billed annually (GBP18 monthly), Max GBP90/month, Ultra GBP180/month, incl. VAT; USD figures not shown in that view. Team seats: Standard 1.25x Pro per-session, Premium 6.25x per-session, weekly limits on both; individual-plan weekly multiples are published (1x/5x/10x) but Team weekly multiples are not, and Team limits are per-member. Console API and third-party provider billing remain separate; taxes and regional prices vary.
What can it access and what needs my approval?
Tiered permission modes re-verified 22 October 2026: plan (read-only explore), auto (runs without routine prompts; a background classifier checks actions against your request), acceptEdits, dontAsk (auto-denies anything that would prompt) and manual. Deny/ask/allow rules apply with documented precedence. 'Yes, and don't ask again' approvals save as rules to .claude/settings.local.json at the repository root and apply across future sessions and worktrees in that repo; file-edit approvals last only for the session. Feedback surveys and nonessential traffic can be disabled (CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY, DISABLE_TELEMETRY, DO_NOT_TRACK); organisations can route survey ratings through their own OpenTelemetry collector. Filesystem/network isolation beyond the permission system needs OS-level sandboxing; MCP connectors (Drive, Jira, Slack and others) follow their own scopes.
What happens to my data?
Re-verified 22 October 2026 against Claude Code's data-usage doc and Anthropic's privacy policy (effective 10 September 2026). Consumer Free/Pro/Max: training happens only when the voluntary model-improvement setting is on (applies to Claude Code use from those accounts); retention is 5 years with the setting on, 30 days with it off. Commercial (Team, Enterprise, API, third-party platforms, Gov): no training on code or prompts unless the customer opts in (e.g. Developer Partner Program, first-party API only); standard retention 30 days; zero data retention available per-organisation for eligible Enterprise accounts, not by default. Local CLI transcripts are stored in plaintext under ~/.claude/projects/ for 30 days by default (cleanupPeriodDays adjustable; Desktop/Cowork sessions exempt). /feedback, /bug and /share transcripts are retained 5 years; nothing is sent until you choose. Individual cloud sessions can be deleted at any time, permanently removing their event data. Vendor documentation, not independently audited.
Has AgentComparison tested it?
No. This record is built from the vendor's own documentation, checked 2026-10-22. Vendor claims are attributed, not confirmed.
How to evaluate Claude Code yourself
- Pick one low-risk task that matches its documented capabilities: repository work: reads a codebase, edits multiple files, runs tests/commands and documents bugs or features. generated code still needs review and your test suite..
- Write the expected output and what counts as failure before you start.
- Connect the minimum access needed, and check approval settings first.
- Run it twice and compare, then review every action it took.
- Check cost after any free allowance. Unknown price is not free.
Related
Documented use cases: Software development and repository work.
- Devin (product): Engineering teams delegating well-scoped, verifiable tickets who will review the draft PRs it returns.
- Replit Agent (product): Building apps and related artifacts from natural-language requests.
- Cursor cloud agents (product): Developers who want background work on repository branches and can review diffs, tests and artifacts before a human merges the draft pull request. Configure restricted egress and minimum repository access first.
- Jules (product): GitHub developers with a working project setup who want bounded bug fixes, dependency maintenance, documentation or tests returned for review while they work on something else.
- Claude Code vs Devin
- Replit Agent vs Claude Code vs Devin
- AI agent use cases by job
- Privacy and approval checklist
- Compare two agents side by side
- Latest agent updates
Sources and history
- https://code.claude.com/docs/en/overview · official overview · read 22 October 2026
- https://code.claude.com/docs/en/permissions · official permission configuration · read 22 October 2026
- https://code.claude.com/docs/en/security · official security controls · read 22 October 2026
- https://code.claude.com/docs/en/data-usage · official training/retention documentation · read 22 October 2026
- https://claude.com/pricing · official plan/pricing page · read 22 October 2026
- https://www.anthropic.com/legal/privacy · official · read 22 October 2026
Change history
- 2026-10-09: Re-read official features, permissions, pricing and privacy sources; added product-specific evidence table and narrow-start steps. Vendor documentation, no hands-on tests.
- 2026-10-01: Initial documentation research. No hands-on testing.
- 2026-10-01: Anthropic's v2.1.287 release notes (1 October 2026) add Claude Mods plugins, a built-in side-agent mod and MCP URL prompts. Source: https://github.com/anthropics/claude-code/releases/tag/v2.1.287
- 2026-09-30: Release v2.1.286 (vendor release notes): permission prompts show an N-of-M count when several stack up.
- 2026-09-29: Release v2.1.285 (vendor release notes): allowedProviders managed setting; option to disable WebFetch.
- 2026-09-28: Release v2.1.284 (vendor release notes): Claude Sonnet 5.5 default Sonnet model on the API; vendor states 1M context, $2/$10 per Mtok.
- 2026-10-22: Field-level audit: data-usage and permissions docs re-read - all training/retention claims verified verbatim (5y/30d consumer, commercial no-train default, ZDR per-org, plaintext local transcripts, 5-year feedback retention); added per-session cloud deletion, telemetry-disable env vars, repo-root approval-rule saving; Anthropic privacy policy (10 Sep 2026) added as source.
- 2026-10-28: Field-level pricing audit: claude.com/pricing, Max plan help article and Claude Code cost docs re-read - Max $100 (5x) / $200 (20x) monthly-only confirmed, Enterprise $20/seat + API rates annual, usage credits at standard API rates, vendor cost guidance recorded. New pricing guide published; checked_label unchanged (not a full-record check).
- 2026-10-31: Field-level pricing/limits audit: plan tiers renamed (Max 5x, Ultra 10x weekly replacing Max5/Max20), monthly Claude Platform API credits documented (Max $100, Ultra $200), Ultra 5-hour limit removed for verified accounts, Team seat multipliers (Standard 1.25x / Premium 6.25x per-session) confirmed on support.claude.com. checked_label unchanged - not a full-record check.
- 2026-10-31: Scope correction after review: weekly multiples ARE published for individual plans (Pro 1x, Max 5x, Ultra 10x per claude.com/pricing table); the unpublished figure is the Team-seat weekly multiple (only per-session 1.25x/6.25x documented). Guide and note wording corrected; Reddit comment edited to match.
Documentation overview expanded with current pricing/access sources. No hands-on results claimed.
Report a correctionCosts in detail: see Claude Code pricing explained for plans, API billing and usage credits.