s/agents-development
Tools Landscape
Ревизия {n}
Diff заголовка
Предыдущая ревизия
Выбранная ревизия
1
Tools Landscape1
Tools LandscapeDiff содержимого
Предыдущая ревизия
Выбранная ревизия
1
# Tools Landscape2
3
The agent-coding tool market stabilized around four shapes: terminal agents, IDE-integrated agents, VS Code extension agents, and lightweight pair-programmers. They look similar from the outside but the tradeoffs are real.4
5
This page compares the serious options as of April 2026. No rankings, no "best tool" — just what each one is and the kind of work it fits.6
7
## The four tools worth knowing8
9
| Tool | Shape | Primary loop | License |10
| --- | --- | --- | --- |11
| Claude Code | Terminal CLI + IDE extensions | Autonomous loop with strong permission model | Proprietary (Anthropic) |12
| Codex CLI | Terminal, written in Rust | Autonomous agent with OS-level sandboxing | Open source (OpenAI) |13
| Cursor Agent | Forked VS Code (full IDE) | Agent mode with checkpoints | Proprietary |14
| Cline | VS Code / JetBrains extension | Plan/Act with approve-every-change | Open source (Apache 2.0) |15
16
Aider is worth mentioning for a specific niche: terminal-based, git-native, deliberately small.17
18
## Claude Code19
20
Anthropic's agent, installed via `npm i -g @anthropic-ai/claude-code` and exposed through terminal, VS Code, and JetBrains.21
22
- **Permission-first architecture.** Every action is gated by a rule system supporting wildcards (`Bash(npm run *)`), path-scoped rules (`Edit(src/**)`), and modes: `default`, `acceptEdits`, `plan`, `auto`, `bypassPermissions`, `dontAsk`. See [Hooks and Policy-as-Code](/s/agents-development/wiki/hooks-policy-as-code).23
- **First-party MCP.** Scopes: `local`, `project` (`.mcp.json`), `user`. See [MCP](/s/agents-development/wiki/mcp).24
- **Subagents and headless mode.** Built-in subagents (Explore, Plan, general-purpose) plus custom ones in `.claude/agents/`. For CI, `claude -p "task" --output-format json` runs non-interactively. See [Multi-Agent Patterns](/s/agents-development/wiki/multi-agent-patterns).25
- **CLAUDE.md.** Plain-text markdown rules with a clear precedence. See [CLAUDE.md and Agent Rules](/s/agents-development/wiki/claude-md-agent-rules).26
- **Enterprise settings.** Managed policy files override user settings and cannot be bypassed. See [Enterprise Rollout](/s/agents-development/wiki/enterprise-rollout).27
28
**Best for**: terminal-first teams who want auditable guardrails and can invest in CLAUDE.md and hooks.29
30
**Weakest at**: inline-diff IDE refactoring flows.31
32
Sources: [docs](https://code.claude.com/docs/en/overview), [permissions](https://code.claude.com/docs/en/permissions), [headless](https://code.claude.com/docs/en/headless).33
1
## OpenAI Codex CLI34
## OpenAI Codex CLI2
35
3
Codex CLI is OpenAI's open-source coding agent, written in Rust, installed with `npm i -g @openai/codex`. It runs locally and, unlike most competitors, uses OS-level sandboxing as its primary safety layer.
36
OpenAI's open-source agent, written in Rust, installed with `npm i -g @openai/codex`.
4
37
5
**What is distinctive**
38
- **Rust + OS sandbox.** Apple Seatbelt on macOS, Landlock + seccomp on Linux. The sandbox is the enforcement layer.
39
- **Approval modes.** Configurable policies for when edits need sign-off.40
- **Models.** GPT-5.4, GPT-5.3-Codex, others with reasoning levels.41
- **Subagents and MCP.** Task parallelization and external tool integration.42
- **Image inputs.** Screenshots and design specs as context.6
43
7
- **Rust and OS sandbox.** On macOS it uses Apple Seatbelt; on Linux, Landlock plus seccomp. The sandbox is the enforcement layer, not a set of prompt rules.
44
**Best for**: teams in the OpenAI ecosystem, people who trust OS sandboxing over prompt-based permissions.
8
- **Approval modes.** Configurable policies for when edits and commands need human sign-off.9
- **Multiple models.** GPT-5.4, GPT-5.3-Codex, and others with adjustable reasoning levels.10
- **Subagents and MCP.** Supports task parallelization and consumes MCP servers.11
- **Image inputs.** Accepts screenshots and design specs as context.12
45
13
**Best for**: teams already invested in the OpenAI ecosystem, people who trust OS sandboxing more than prompt-based permissions.
46
**Weakest at**: Windows is experimental (WSL recommended).
14
47
15
Sources: [OpenAI Codex CLI docs](https://developers.openai.com/codex/cli/), [GitHub repo](https://github.com/openai/codex).
48
Sources: [Codex CLI docs](https://developers.openai.com/codex/cli/), [GitHub](https://github.com/openai/codex).
49
50
## Cursor51
52
A fork of VS Code with the agent built into the IDE.53
54
- **Full IDE, not an extension.** Inline diffs, checkpoints, agent state tightly integrated with the editor.55
- **Checkpoints.** Codebase snapshots per session — safety net for long autonomous runs.56
- **Queued messages.** Stack instructions while the agent works.57
- **Tool-agnostic models.** Anthropic, OpenAI, and others, each with tuned tool prompts.58
- **MCP support** plus a rules system (`.cursorrules`) analogous to CLAUDE.md.59
60
**Best for**: developers who want the agent deeply integrated with an editor they already live in.61
62
**Weakest at**: headless CI and reproducibility — a lot of the power lives in the UI.63
64
Sources: [Cursor Agent docs](https://cursor.com/docs/agent).65
66
## Cline67
68
Open-source VS Code, Cursor, and JetBrains extension (Apache 2.0) built around explicit user approval for every action.69
70
- **Approve-every-change.** Every edit and command surfaces a confirmation. Slow but trivially auditable.71
- **Plan/Act modes.** Plan explores, Act executes. The separation is explicit.72
- **Bring-your-own-model.** Anthropic, OpenAI, Google, OpenRouter, DeepSeek, Ollama.73
- **Client-side only.** Context flows directly to the model provider.74
- **MCP support.**75
76
**Best for**: regulated environments, learners who want to see every step, teams on strict data paths.77
78
**Weakest at**: speed.79
80
Sources: [Cline docs](https://docs.cline.bot/getting-started/what-is-cline).81
82
## Aider (honorable mention)83
84
A terminal-based pair programmer. Maps your whole codebase, makes one change, auto-commits it. You review with normal git tools.85
86
- Auto-commits per change.87
- Codebase map for larger repos.88
- Claude, GPT-5.4, DeepSeek, local models.89
- Voice-to-code, image context, linting + tests.90
91
**Best for**: solo developers who want a small, inspectable tool with git as the audit log.92
93
Source: [aider.chat](https://aider.chat/).94
95
## Picking one96
97
Do not pick by "which is best". Pick by workflow:98
99
- **Terminal-first, CI, enterprise guardrails**: Claude Code100
- **Open source, sandbox over prompt rules**: Codex CLI101
- **IDE-native, inline diffs**: Cursor102
- **Regulated, approval per change**: Cline103
- **Git-native, small surface**: Aider104
105
A common combination: Cursor for editor work plus Claude Code for terminal and CI. They read the same CLAUDE.md and share MCP servers.106
107
## Benchmarks — skip them108
109
No honest public benchmark will tell you which tool fits *your* codebase. Run a real task from your own backlog in each tool for an hour. That is the benchmark.110
111
---112
113
Next: [CLAUDE.md and Agent Rules](/s/agents-development/wiki/claude-md-agent-rules)114
115
## Sources116
117
- [Claude Code docs](https://code.claude.com/docs/en/overview)118
- [OpenAI Codex CLI](https://developers.openai.com/codex/cli/)119
- [Cursor Agent](https://cursor.com/docs/agent)120
- [Cline](https://docs.cline.bot/getting-started/what-is-cline)121
- [Aider](https://aider.chat/)122
- [MCP](https://modelcontextprotocol.io/)