Agent Rankの内訳
- 自律性
- 8
- 機能
- 6
- 連携
- 4
- 料金
- 8
- 完成度
- 10
- 検証性
- 10
自律性、機能、連携、料金、成熟度、編集部の検証を基に自動算出。デプロイごとに更新されます。 どのように算出されているか?
機能
- コード実行
- ツール利用
- メモリ
連携
- IDE
- VS Code
- Version control
- GitHub
料金プラン
- +エージェント実行回数に制限あり
- +すべてのエディタ機能
- +コミュニティサポート
- +無制限のエージェント実行
- +すべての Pro モデル
- +バックグラウンドエージェント
- +優先サポート
- +Pro のすべての機能
- +管理ダッシュボード
- +SSO
- +利用分析
- +SOC 2
Our take on Cursor Agent
Cursor's background agent turns the editor everyone already loves into a multi-file refactor machine. The pricing is reasonable, the diff UX is the cleanest in the category, and the productivity gain is real — but it shines as an assistant, not as an autonomous worker.
- +Inline diff approval is the best UX in the category, hands down
- +$20/mo unlocks 500 fast requests + unlimited slow — generous for solo devs
- +Background agent works while you keep coding in another window
- +Repository-aware indexing means it knows your existing patterns
- −Best results require manual context selection (@file, @docs) — not zero-effort
- −Cannot truly work autonomously for hours without supervision (yet)
- −Cursor Pro is required for the background agent; the free tier is much weaker
- −Lock-in is mild but real — you're committing to a VS Code fork
- ·Solo developers shipping continuous features at high velocity
- ·Teams doing repository-wide refactors (renames, API migrations, test scaffolding)
- ·Pair programming on unfamiliar codebases — Cursor explains as it edits
- ·Highly senior engineers sometimes find it slows them down on micro-edits
- ·Large monorepos can confuse the indexer; segment with .cursorignore
What changed when Cursor added a real agent
For years, Cursor was "VS Code with great inline AI." That's still true — but in late 2024 they shipped a background agent mode that elevates it from copilot to junior teammate. You hand it a task ("Add a /webhooks endpoint that verifies HMAC, queue jobs, write tests"), it disappears for 5-15 minutes, and comes back with a diff you can scroll through and accept hunk-by-hunk.
This is meaningful. Previously you had to drive Cursor with chat. Now Cursor drives itself. The difference shows up most on tasks where the spec is clear but the mechanical work is tedious — exactly the work that burns senior engineer time.
The diff UX deserves its own paragraph
Every coding agent shows you "here's what I changed." Cursor's implementation is the cleanest:
- File-by-file navigation, with a sticky overview panel.
- Hunk-level accept/reject, not just "approve all".
- Live preview of the resulting file as you toggle hunks on/off.
- Comments inline explaining why the agent made each change.
After a week of use, this UX becomes a moat. Switching to a tool that dumps a unified diff feels primitive.
Where it gets uneven
The single biggest performance variable is context selection. If you mention
@codebase and let Cursor index everything, you get a 70%-good answer. If you
carefully @-mention the 3 files that matter, you get a 95%-good answer. The skill
ceiling on prompting matters more than people admit.
Two specific failure modes we hit repeatedly:
-
Large monorepos — past ~500k LOC, the indexer slows down and starts giving stale recommendations. Mitigate with
.cursorignorelisting build outputs, generated SDKs, and historical archives. -
Context drift on long sessions — after ~30 minutes of conversation, Cursor sometimes forgets earlier decisions. Restarting the chat with a fresh prompt summarizing the goal usually fixes it.
Pricing math
Cursor Pro is $20/month — same as ChatGPT Plus or Claude Pro. For that you get:
- 500 "fast" requests (low-latency, frontier models)
- Unlimited "slow" requests (queue when fast is exhausted)
- Background agent access
- Repository indexing
For a developer who'd otherwise pay individually for Claude Pro + GitHub Copilot ($30/mo combined), Cursor Pro is a clear win. For a team, the Business plan is $40/seat/month and includes admin controls, privacy mode (your code never trains models), and SSO.
Honest comparison
- vs Cline: Cursor is more polished, less transparent. Cline is more transparent, less polished. If you want to see every prompt, choose Cline. If you want fewer decisions, choose Cursor.
- vs Devin: Devin runs longer and more autonomously, but costs 25× more. Cursor's background agent is the right tool for 90% of tasks Devin can do.
- vs Copilot: Different categories now. Copilot is autocomplete-plus. Cursor is closer to a junior dev sitting at your desk.
Bottom line
Cursor is the default recommendation for most developers in 2025. It's not the most autonomous, the most transparent, or the most experimental — but it's the agent that consistently delivers value without ceremony. If you're starting from zero, start here.
複数ファイルの変更にわたって Cursor エディタを操作するバックグラウンドエージェントです。 サブスクリプションプランから始めましょう。
よくある質問
Cursor の料金はいくらですか?+
Cursor には4つの料金プランがあります。Hobby(無料、補完回数に制限あり)、Pro(月額 $20 の定額制、無制限のエージェント実行と Cursor Tab)、Business(5人以上のチーム向けシート単価 $40、SSO と管理ダッシュボード付き)、Ultra(フロンティアモデルへのアクセスを必要とするパワーユーザー向け月額 $200)です。多くの現場エンジニアには Pro プランが最適です。
Cursor は月額 $20 の価値がありますか?+
毎日コーディングするエンジニアであれば、価値はあります。Cursor Tab のオートコンプリートだけで料金を正当化できることが多く、2026年のエディタ内AI補完として最高水準です。Composer(複数ファイルの編集)、エージェントモード(より長い自律ループ)、MCP サポートを加えると、今年最も使用されているAIコーディングエージェントとなります。
Cursor と GitHub Copilot の比較は?+
Cursor は日常的なICエンジニアリング向けです — より優れたタブ補完、より積極的なエージェントモード、洗練された MCP 対応。GitHub Copilot(Pro月額 $10)は JetBrains/Visual Studio を使用するエンジニア、IP補償が必要なチーム、または GitHub エコシステムに深く根ざしたユーザー向けです。2026年時点で両者ともエージェントモードを搭載しており、差は小さくなっています。
Cursor は MCP サーバーに対応していますか?+
はい — Cursor は Model Context Protocol サポートを最初に搭載した IDE のひとつです。設定UIから数分で MCP サーバー(GitHub、Linear、Slack、Notion、Postgres、Sentry など)を追加できます。MCP のインストール体験は、2026年のコーディングエージェントの中で最も洗練されています。
ユーザーレビュー
レビューを書く →Be the first to review. We verify every reviewer by email.