GitHub announced that Copilot Edits mode is now generally available, exiting preview. The feature lets you make changes across multiple files from a single prompt, similar to Cursor’s Composer or Windsurf’s Cascade.
For VS Code + Copilot users, this is a meaningful capability that wasn’t available before.
What it does
You describe a change. Copilot Edits:
- Identifies which files need changes
- Proposes changes for each
- Shows a unified diff
- You accept or reject per-file
This is the workflow that has been Cursor’s competitive advantage for VS Code users. Copilot now offers it natively in VS Code.
Comparison to Cursor Composer
Both tools handle similar tasks. The differences are subtle:
Cursor Composer:
- More mature; longer track record
- Better UX for plan-then-execute workflow
- Tighter integration with Cursor’s codebase indexing
Copilot Edits:
- Available in unmodified VS Code (no fork required)
- Integrates with GitHub’s broader ecosystem
- Available on Copilot Business and Enterprise tiers
For users on plain VS Code, Copilot Edits eliminates the main reason to consider Cursor. For users already on Cursor, no need to switch unless other factors apply.
Pricing
Copilot Edits is included in:
- Copilot Pro ($19/month)
- Copilot Business ($19/seat/month)
- Copilot Enterprise ($39/seat/month)
No additional cost. The feature is part of the standard subscription.
What’s mature about it
After running it for a few weeks:
- Handles 5-10 file changes reliably
- Diff preview is clean
- Accept/reject UX is good
- Performance is acceptable (slower than Cursor Composer but workable)
For routine multi-file changes, the tool is ready for daily use.
What’s still rough
A few remaining gaps:
- Larger refactors (>15 files) sometimes lose coherence
- Long-running edits don’t have great progress indicators
- The “what files will change?” planning step is less explicit than Cursor’s
- Sometimes proposes changes you didn’t ask for
These are similar to Cursor’s early Composer issues. Iteration over time should close them.
What this signals
GitHub closing a Cursor-shaped gap is significant. Cursor’s competitive advantage on multi-file editing was real for over a year. Copilot finally matching the capability changes the calculus for some users.
For Cursor: this puts pressure on differentiating elsewhere. Cursor still has strengths (codebase indexing, Composer’s polish, etc.) but the multi-file gap was the biggest single advantage.
For Copilot users who’d been considering Cursor: this is one less reason to switch.
For VS Code users on no AI tool: the bar to start using one just got lower. Copilot Edits is good enough for daily use.
Worth using?
For Copilot users on Pro+: yes. The feature is useful and costs nothing extra. Use it for multi-file work.
For Cursor users considering switching to VS Code + Copilot: possible if you don’t use Cursor-specific features (Tab, Composer Agent, BugBot). The capability gap is smaller now.
For users on other AI tools: this doesn’t change much for you.
The category trajectory
The “multi-file editing” feature is becoming standard across AI tools. Cursor pioneered it; Windsurf added it; Copilot now has it stable. Cline has had it since launch (different shape).
A year from now, expect every major AI coding tool to have this capability. The differentiation moves to:
- How well it works for large refactors
- How smoothly the planning/execution split works
- How well it integrates with team workflows
These are the next-tier differentiators. Multi-file editing is becoming table stakes.
Closing
A useful release for a large user base (Copilot Pro+ subscribers). Closes a real gap. Doesn’t dramatically reshape the market, but does shift it incrementally toward parity.
For VS Code users wondering if their Copilot Pro subscription is worth it: yes, more so now than it was. Multi-file editing is a real productivity feature.
