This is week 3 of my "I Used It for a Week" series. I reviewed Cursor (the speed demon) and Kiro (the spec planner). Now it's time for the one most developers actually use: GitHub Copilot.
Here's the thing about Copilot — I used it for over a year before trying Cursor and Kiro. It was my baseline. The tool I compared everything else to. Going back to it after two weeks with the competition was... revealing.
The Setup
Unlike Cursor and Kiro, Copilot isn't a standalone editor. It's an extension that lives inside your existing IDE — VS Code, JetBrains, Neovim, Xcode, even Eclipse. That's its biggest strength and its biggest limitation.
I installed it in VS Code (my default before the Cursor experiment) and picked up right where I left off. All my extensions, all my settings, zero switching cost. If you've never used an AI coding tool before, this is the easiest possible starting point.
What Still Works Well
Inline completions are solid
Copilot's bread and butter — the ghost text that appears as you type — is still good. It predicts the next few lines based on your current file and open tabs. For writing boilerplate, implementing interfaces, and filling in repetitive patterns, it saves real time.
A ProductHunt reviewer summed it up: "It saves time by suggesting accurate code snippets and helps me stay in flow while coding." That matches my experience. For straightforward coding, Copilot just works.
IDE flexibility is unmatched
This is Copilot's trump card. Cursor locks you into their VS Code fork. Kiro is also VS Code-based. Copilot works in everything. If you're a JetBrains user (IntelliJ, PyCharm, WebStorm), Copilot is basically your only option among the big three.
For teams with mixed IDE preferences, this matters a lot.
Agent mode has caught up (mostly)
Copilot launched agent mode in February 2025, and by 2026 it's genuinely useful. You can ask it to plan changes, edit multiple files, run terminal commands, and iterate until the task is done. The coding agent can even turn GitHub Issues into pull requests autonomously.
With the March 2026 update, you can now select GPT-5.4 for agent mode across all supported IDEs. The quality jump from the older models is noticeable.
The GitHub ecosystem
Copilot's integration with GitHub is seamless in ways the competition can't match. Code review suggestions on pull requests, automated security scanning, Copilot Workspace for planning features directly from issues — if your team lives on GitHub, this ecosystem is valuable.
The Copilot SDK (production-ready since January 2026) lets enterprises build custom agents trained on their own architectural patterns. With 4.7 million paid users, the ecosystem is massive.
Price
The free tier gives you 2,000 completions and 50 agent/chat requests per month. That's enough to evaluate it properly. Pro at $10/month is the cheapest paid option among the big three — half the price of Cursor's $20/month.
What Frustrated Me (Coming Back From Cursor and Kiro)
Context awareness is shallow
This is where Copilot falls hardest behind. After using Cursor's deep codebase indexing and Kiro's spec-driven context, Copilot's understanding of my project felt surface-level.
Copilot primarily works from the current file and open tabs. It doesn't index your entire repository the way Cursor does. In testing across projects exceeding 10,000 lines, suggestions were accurate only about 50% of the time. It frequently suggested APIs and methods that didn't exist in my codebase.
One TrustRadius reviewer nailed it: "Copilot is not the best at analyzing large monolithic codebases and placing them in their context."
No next-edit prediction
After two weeks of Cursor's Tab-Tab-Tab workflow — where it predicts not just the current line but your next edit location — going back to Copilot's basic inline suggestions felt like downgrading. Copilot completes the line you're on. Cursor anticipates where you're going next. That difference compounds over a full day of coding.
Multi-file editing is weaker
Copilot's agent mode can edit multiple files, but it doesn't match Cursor's subagent system or Kiro's spec-guided implementation. The trade-off is architectural: Copilot works through extension APIs rather than controlling the whole editor environment. It can't understand your codebase as deeply because it's a guest in someone else's house.
For quick single-file edits, this doesn't matter. For large refactoring across 10+ files, the difference is stark.
No spec workflow, no hooks
Kiro's spec-driven approach and Agent Hooks have no equivalent in Copilot. There's no way to define requirements before coding, no automated triggers on file changes, and no structured planning workflow. Copilot is reactive — it responds to what you're doing. It doesn't help you figure out what you should be doing.
Security concerns are real
Multiple reviews and studies flag that Copilot can suggest insecure code patterns. Since it learns from public repositories, it sometimes pulls in outdated or vulnerable patterns. This isn't unique to Copilot — all AI coding tools have this risk — but Copilot's shallower context awareness means it's less likely to understand your project's specific security requirements.
The Pricing Breakdown
| Plan | Price | Key Features |
|---|---|---|
| Free | $0 | 2,000 completions, 50 chat/agent requests |
| Pro | $10/month | Unlimited completions, premium model access |
| Pro+ | $39/month | More premium requests, coding agent |
| Business | $19/user/month | Organization management, policy controls |
| Enterprise | $39/user/month | SSO, SCIM, audit logs, IP indemnity |
The free tier is genuinely useful for evaluation. Pro at $10/month is the sweet spot for individuals. But note: heavy agent usage on Pro can hit limits, pushing you toward Pro+ at $39/month — which is nearly double Cursor's flat $20.
The Three-Tool Comparison
After using all three for a week each, here's my honest ranking by category:
| Category | Winner | Runner-up | Third |
|---|---|---|---|
| Inline completions | Cursor (next-edit) | Copilot | Kiro |
| Multi-file refactoring | Cursor (subagents) | Kiro (spec-guided) | Copilot |
| Planning & architecture | Kiro (specs) | Copilot (Workspace) | Cursor |
| IDE flexibility | Copilot (all IDEs) | — | Cursor/Kiro (VS Code only) |
| Codebase understanding | Cursor (deep index) | Kiro (spec context) | Copilot |
| Price (value) | Copilot ($10/mo) | Cursor ($20/mo) | Kiro (variable) |
| Ecosystem | Copilot (GitHub) | Kiro (AWS) | Cursor |
| Speed of small edits | Cursor | Copilot | Kiro |
| Code quality | Kiro (spec-driven) | Cursor | Copilot |
My Verdict After 7 Days
Copilot is the Toyota Corolla of AI coding tools. It's reliable, affordable, works everywhere, and gets the job done. There's a reason 4.7 million developers pay for it.
But after experiencing Cursor's speed and Kiro's discipline, Copilot feels like it's coasting on distribution rather than innovation. The GitHub integration and IDE flexibility keep it relevant, but the core AI experience — context awareness, multi-file editing, intelligent suggestions — is falling behind.
Would I keep paying? Only if I needed JetBrains support or was on a team standardized on GitHub's ecosystem. For VS Code users, Cursor is a better tool at twice the price — and the productivity gains more than cover the difference.
Who should use it:
- JetBrains users (no real alternative)
- Teams already deep in the GitHub ecosystem
- Developers who want the cheapest entry point
- Anyone who doesn't want to switch editors
Who should look elsewhere:
- VS Code users who want the best AI experience (→ Cursor)
- Solo developers building features from scratch (→ Kiro)
- Anyone doing heavy multi-file refactoring
- Developers who want deep codebase understanding
Tips If You're Starting
- Use agent mode, not just inline suggestions — the inline completions are table stakes now, the agent is where the value is
- Try GPT-5.4 as your model — it's a significant upgrade over the default
- Open relevant files in tabs — Copilot uses open tabs for context, so more tabs = better suggestions
- Don't trust security-sensitive suggestions blindly — review anything touching auth, encryption, or user data
- Consider the free tier first — 2,000 completions/month is enough to decide if it's for you
That's three weeks, three tools. My current setup: Cursor for daily coding, Kiro for new features, Copilot retired. Your mileage may vary — the best tool is the one that matches how you think, not how I think.
Originally published at https://www.aimadetools.com
Top comments (0)