The Cursor Effect: How GitHub Copilot is Responding to Peer Pressure

Intent The AI Coding Assistant arena is heating up. In recent months, excitement around Cursor IDE has sparked curiosity among developers. Rightfully so—Cursor’s entry into the IDE space with a deeply integrated AI experience turned heads. It hasn’t just plugged in AI; it’s trying to reshape the entire development experience around it, from agentic workflows to seamless chat-first coding. Naturally, this raises a question for me: Is GitHub Copilot keeping up? Before we think about shifting direction or adopting a Multi-IDE working model, we need a shared understanding of what’s already available to us—especially within the latest VS Code + Copilot ecosystem. Otherwise, we risk comparing tools unfairly, based on outdated versions or impressions shaped by trend cycles rather than facts. It's crucial that we evaluate them fairly—not against past memories, but against their most current, full-featured releases. Let’s take a step back and look at what GitHub Copilot now brings to the table—especially the capabilities rolled out in recent months that may go unnoticed if your IDE isn’t up to date. Along the way, in this post, I will briefly unpack some of the recent concepts shaping AI-assisted development workflows—like Modes of working with Code AI, Next Edit Suggestions (NES), Model Selection, and AI Rules. This post is about clarity—not conclusions. Model Awareness & Flexibility In the past, GitHub Copilot was synonymous with “the OpenAI model behind the curtain.” But that’s no longer the case. Copilot has evolved into a model-flexible platform, supporting a wide range of top-tier models—empowering developers to tailor their experience based on speed, reasoning depth, task complexity, or preference.

Apr 19, 2025 - 06:05
 0
The Cursor Effect: How GitHub Copilot is Responding to Peer Pressure

Intent

The AI Coding Assistant arena is heating up. In recent months, excitement around Cursor IDE has sparked curiosity among developers. Rightfully so—Cursor’s entry into the IDE space with a deeply integrated AI experience turned heads. It hasn’t just plugged in AI; it’s trying to reshape the entire development experience around it, from agentic workflows to seamless chat-first coding.

Naturally, this raises a question for me: Is GitHub Copilot keeping up?

Before we think about shifting direction or adopting a Multi-IDE working model, we need a shared understanding of what’s already available to us—especially within the latest VS Code + Copilot ecosystem. Otherwise, we risk comparing tools unfairly, based on outdated versions or impressions shaped by trend cycles rather than facts. It's crucial that we evaluate them fairly—not against past memories, but against their most current, full-featured releases.

Let’s take a step back and look at what GitHub Copilot now brings to the table—especially the capabilities rolled out in recent months that may go unnoticed if your IDE isn’t up to date.

Along the way, in this post, I will briefly unpack some of the recent concepts shaping AI-assisted development workflows—like Modes of working with Code AI, Next Edit Suggestions (NES), Model Selection, and AI Rules.

This post is about clarity—not conclusions.

Model Awareness & Flexibility

In the past, GitHub Copilot was synonymous with “the OpenAI model behind the curtain.” But that’s no longer the case. Copilot has evolved into a model-flexible platform, supporting a wide range of top-tier models—empowering developers to tailor their experience based on speed, reasoning depth, task complexity, or preference.