Claude Code
Anthropic's terminal agent that plans, edits, runs tests, and commits - fully interactive with your repo. The coding agent with the most MCP depth.
Delv Safety Grade: B
Score 72/100 · assessed 2026-04-18
Claude Code is Anthropic's official autonomous coding agent with full filesystem and shell access. The maintainer score is excellent given it's a first-party Anthropic product. However, permissions are extremely broad: it writes arbitrary files, executes shell commands, and commits to repos without sandboxing. The supply chain score is middling because there's no public repository or package distribution - it's delivered through Anthropic's infrastructure, which is trustworthy but opaque. Transparency suffers from lack of open source code or detailed technical documentation about safety boundaries. No known incidents, but the autonomy level (multi-file edits, test execution, git operations) means a prompt injection or logic error could cause significant repo damage. Suitable for experienced developers who understand the risk surface, less so for production environments or shared codebases without careful oversight.
Green flags
- Official Anthropic product with enterprise-grade maintainer
- MCP-native architecture allows scoped tool integration
- Interactive approval loops reduce blind automation risk
- No known security incidents or credential leaks
- Designed for terminal use where user oversight is natural
Red flags
- No public repo or source code available for audit
- Unrestricted filesystem write and shell execution without sandbox
- Autonomous git commits could push breaking changes
- Broad permissions with minimal documented safety boundaries
- Opaque distribution model limits supply chain verification
Permissions requested
Pricing
Platforms
Review
Pay for this if you do solo refactors, have a test suite, and want an agent that iterates without hand-holding. Skip it if you prefer inline suggestions or work in codebases without tests.
Good at
- Autonomously loops through edit-test-fix cycles without human approval per step
- Native MCP support lets it query live systems, databases, and APIs mid-task
- Handles multi-file refactors with full repo context better than Cursor or Copilot
- Plans work upfront so you can review the approach before it starts editing
- Commits changes with meaningful messages after validating tests pass
Watch out
- Slower than autocomplete tools for single-function edits
- Planning phase can feel verbose when you just need a quick fix
- Sometimes overwrites comments or formatting you wanted to keep
- Value drops sharply if your codebase lacks a test suite
- Less transparent than Aider about what it's changing before it does it
Use cases
- Long coding sessions with full repo context
- Running and fixing failing tests in a loop
- Codebase refactors that span many files
- Prototyping from a spec in conversation