By now, you’ve likely sensed the growing frustration within the community about recent changes to GitHub Copilot. Many of us are just waiting for our credits to run out before exploring alternatives. Considering the allowance reset on June 30, I estimate that by around July 10, a large portion of your user base will begin migrating en masse. And let’s be honest, GPT-4.1 just isn’t cutting it for most of us. So, what can be done to stop users from switching their subscription to Cursor? A simple yet powerful move: Include Claude Sonnet 4 in the Copilot standar models, not necessarily in the Pro plan, but at least in Pro+. While you may not have the same influence over Anthropic as you do with OpenAI, you are still the only major player positioned to pull this off. Doing so could not only keep your users but bring a significant share of the Cursor and Windsurf user base. I understand this isn't an easy financial decision, but with Opus 4 already available in the Enterprise plan, moving Sonnet 4 to the included tier and adding Opus 4 to the premium tier for solving complex problems would maybe help this work out? With the timeline in mind, you have about 20 days to either lead this race or get left behind.

508

@Adventurous_Emu_5520

GitHub Copilot vs Cursor in 2025: Why I'm paying half price for the same features

# After researching both GitHub Copilot and Cursor extensively, I wanted to share my findings for anyone trying to decide between these AI coding assistants. # Price Comparison * **GitHub Copilot Pro**: $10/month with unlimited standard usage (fair use policies apply) * **Cursor Pro**: $20/month but only includes 500 "fast" premium requests, with additional charges for exceeding this limit * Some users report paying over $44 when exceeding Cursor's request limits, while Copilot maintains a predictable monthly cost # Feature Comparison Both tools now offer nearly identical capabilities: * AI code completion * Chat interfaces for coding assistance * Agent modes for autonomous coding tasks * Codebase understanding # What changed recently Copilot has caught up to Cursor with its agent mode in VSCode. Previously, Cursor had an edge here, but Copilot's agent mode is now available in VSCode Insiders and rolling out to stable VSCode, making the tools functionally equivalent for most developers. # My conclusion Why pay $20+ for Cursor when GitHub Copilot does the same thing for $10? Unless there's something specific about Cursor's editor you prefer, Copilot seems like the better value, especially if you're already using VSCode. What's your experience with either tool? Has anyone found features in Cursor that justify the price difference?

506

@hollandburke

Beast Mode V3 is here

Hi friends! Burke here again from the VS Code team with v3 of the 4.1 Beast Mode chat mode file. 👉 [4.1 Beast Mode v3](https://gist.github.com/burkeholland/88af0249c4b6aff3820bf37898c8bacf) **What's New** * Built on top of OpenAI's own [prompting guide](https://cookbook.openai.com/examples/gpt4-1_prompting_guide) with an opinionated workflow layered in. * The new workflow emphasizes Google search using fetch to get the model to act more like a human and do some research. I feel like all agents should just do this. It's what I do, why wouldn't the model do this too. * I've really tried a bunch of different things to get 4.1 to keep going no matter what. You'll see some tweaks in the head of the prompt to that effect. * I've reordered the workflow steps to be very prescriptive so that 4.1 will do more leg work to understand before taking action and will test it's work. * Tweaks to workflow sections to be more prescriptive about what tools to use and how. * Communication guidelines so that at the very least it doesn't sound like it doesn't care at all about my request 😂 A few other notes... * Some folks have asked about how to use this. You can use it as a simple instruction file, but I recommend using Insiders and this as a custom chat mode as I feel like I get better behavior this way - although I don't have a benchmark to back that up. Go to Ask/Edit/Agent picker -> Configure Modes -> Add new chat mode. * The tooling for custom chat modes is still a bit touch and go in Insiders. If you try to disable or enable a tool from the tool picker, it will open the mode and try to add/remove them from the front matter. You're just going to have to work with this and add the tools array if you need to. This experience will improve. * I've seen some folks complain that this mode doesn't work for them at all. If you trying to one-shot big changes/features, I would suggest breaking your workflow down into **research**, **plan** and **architect** steps. The idea is that you have 4.1 do research, then create a PRD, then write a tech spec. Then you implement the tech spec. This is a workflow that has been documented by Nicholas Zakas [here](https://humanwhocodes.com/blog/2025/06/persona-based-approach-ai-assisted-programming/) and Austen Stone [here](https://austen.info/blog/github-copilot-agent-mcp/). * It's still not Claude - but it's definitely not the 4.1 you know today. I'm using this and getting solid results. Not perfect. It doesn't always complete. Sometimes it puts the imports below the code - it's 4.1. But it's a marked improvement even over v2. Thanks again and always open to feedback, suggestions, tweaks. We appreciate you all! EDIT: u/debian3 reminded me - we are working on improving 4.1 right now in the product. And since we're open source now (yay!) you can follow the progress in [this issue](https://github.com/microsoft/vscode/issues/253678). I just wanted to get you what I had today ASAP.

504

@debian3