Compare
Cursor vs GitHub Copilot
Rankings as of
Last updated
Short answer: pick Cursor for this job: Daily driving an AI editor on a real repo. Pick GitHub Copilot for this job: Adding an agent without leaving the editor you have. Cursor scores 8.6 and is #1 in AI code editors. GitHub Copilot scores 7.8 and is #2 in AI code editors.
| Compared on | Cursor | GitHub Copilot |
|---|---|---|
| What it is | AI editor on a VS Code fork, with tab, inline edit, and an agent. | GitHub's AI pair programmer across VS Code, JetBrains, and its own app. |
| StackPick job | AI code editors, #1 | AI code editors, #2 |
| Best for | Daily driving an AI editor on a real repo | Adding an agent without leaving the editor you have |
| Score | 8.6 | 7.8 |
| Ease / Power / Price / Fit | 8 / 9 / 6 / 10 | 9 / 8 / 7 / 7 |
| Pricing | FreemiumFree tier and paid plans. Current prices: check site. | FreemiumFree tier and paid plans (Pro and above). Current prices: check site. |
| Visit | Visit | Visit |
Where Cursor fits
Cursor is an AI code editor from Anysphere, built as a fork of VS Code. It puts autocomplete, inline edits, and a repository agent in the same window. It is the default pick in this directory for people who want one editor to live in.
Best use cases
- Editing an existing codebase with an agent
- Keeping VS Code keybindings and extensions
- Shipping a small product from one window
Listed strengths
- VS Code-compatible, so most extensions and shortcuts carry over
- Agent, chat, and inline edit share the repo you already have open
- The product is aimed at working inside a codebase, not generating a toy app
Trade-off: You are on their editor fork, not stock VS Code Heavy agent use sits on a paid plan — current prices: check site
Where GitHub Copilot fits
GitHub Copilot is GitHub's AI coding assistant. It offers inline suggestions and an agent in VS Code, JetBrains IDEs, a Copilot app, and a CLI. It is the path of least resistance if your work already lives on GitHub and you do not want to switch editors.
Best use cases
- Autocomplete and agent chat inside VS Code or JetBrains
- Teams that already pay GitHub and want one vendor
- A CLI agent next to the editor plugin
Listed strengths
- Fits the editors people already use
- Deep tie-in to GitHub repositories, pull requests, and accounts
- A free tier exists alongside paid plans
Trade-off: The agent experience is split across the editor, the Copilot app, and the CLI Plan names and model access change — check site
Published prices
Prices change. Check the vendor page before you buy. A usage-based or credit-based plan can cost more than the subscription price.
Cursor
- Free. $0 per month (Source · checked ) Limited agent and chat requests.
- Plus. $8 per person per month (Source · checked ) Grok models only. Included usage is a weekly pool. After that pool, top-offs are extra. Prices exclude tax. $80 per person per year (Source · checked ) Grok models only. Annual charge published as $80/yr. Included usage is a weekly pool. After that pool, top-offs are extra. Prices exclude tax.
- Premium. $30 per person per month (Source · checked ) Included usage is a weekly pool. Third-party models are billed separately at API list price and are not part of this price. Prices exclude tax. $300 per person per year (Source · checked ) Annual charge published as $300/yr. Included usage is a weekly pool. Third-party models are billed separately at API list price and are not part of this price. Prices exclude tax.
- Super. $100 per person per month (Source · checked ) Included usage is a weekly pool. Third-party models are billed separately at API list price and are not part of this price. Prices exclude tax. $1,000 per person per year (Source · checked ) Annual charge published as $1,000/yr. Included usage is a weekly pool. Third-party models are billed separately at API list price and are not part of this price. Prices exclude tax.
- Ultra. $200 per person per month (Source · checked ) Included usage is a weekly pool. Third-party models are billed separately at API list price and are not part of this price. Prices exclude tax. $2,000 per person per year (Source · checked ) Annual charge published as $2,000/yr. Included usage is a weekly pool. Third-party models are billed separately at API list price and are not part of this price. Prices exclude tax.
- Teams · $30 seat. $30 per person per month (Source · checked ) Per seat per month. The docs list Teams at $30, $100, or $200 per seat and say the allowance matches the seat tier. Third-party models are extra. Prices exclude tax.
- Teams · $100 seat. $100 per person per month (Source · checked ) Per seat per month. The docs list Teams at $30, $100, or $200 per seat and say the allowance matches the seat tier. Third-party models are extra. Prices exclude tax.
- Teams · $200 seat. $200 per person per month (Source · checked ) Per seat per month. The docs list Teams at $30, $100, or $200 per seat and say the allowance matches the seat tier. Third-party models are extra. Prices exclude tax.
GitHub Copilot
- Free. $0 per month (Source · checked ) Limited AI credits. Inline suggestions are limited to 2,000 completions a month.
- Pro. $10 per person per month (Source · checked ) Includes 1,500 AI credits a month (1,000 base and 500 flex). Some users get Pro free. Usage past the allowance costs more.
- Pro+. $39 per person per month (Source · checked ) Includes 7,000 AI credits a month (3,900 base and 3,100 flex). Usage past the allowance costs more.
- Max. $100 per person per month (Source · checked ) Includes 20,000 AI credits a month (10,000 base and 10,000 flex). Usage past the allowance costs more.
- Business. $19 per person per month (Source · checked ) Per granted seat. Includes 1,900 AI credits per user a month, pooled. Usage past the pool is $0.01 per AI credit.
- Enterprise. $39 per person per month (Source · checked ) Per granted seat. Includes 3,900 AI credits per user a month, pooled. Usage past the pool is $0.01 per AI credit.
- Copilot access standalone. $10 per person per month (Source · checked ) For users without a GitHub Enterprise Cloud license. No included AI credit allowance. Metered usage is billed separately.
Where the score comes from
The 0.8 gap comes from ease (8 vs 9) and power (9 vs 8) and price (6 vs 7) and vibe-coder fit (10 vs 7). How scores work.
What changed recently
GitHub Copilot Fusion generally available
On October 28, 2026, GitHub Copilot Fusion became generally available. Selecting it does not pick one model. It routes and orchestrates models for each task, combining Project HydraFusion's multi-model orchestration with Copilot auto model selection. Effort levels are Fusion Standard, Fusion High, and Fusion Max. Workflows are Single (one model), Cascade (an efficient model drafts, then a quality check can escalate), and Critique (one model drafts, another reviews, and the first revises). GitHub says Copilot Fusion Max scored 60 on the Artificial Analysis Coding Agent Index, within two points of Claude Code with Opus 5.5 Max, at about half the average API cost per task, using about half as many tokens and taking about 40% less time per task. Fusion uses only models enabled in enterprise and organization policies. Enterprise administrators can disable a model for Fusion without disabling it for everyone, and can set Fusion, at any effort level, as the default. Each model Fusion uses is billed at that model's standard rate. For a limited time, paid Copilot plans get a 30% discount on model costs when using Fusion. It is available on all Copilot plans in Visual Studio Code, the GitHub Copilot app, GitHub Copilot CLI, and JetBrains IDEs. Previous auto, HydraFusion, or HydraFusion Max selections move to the corresponding Fusion effort levels.
Source for GitHub Copilot Fusion generally available (opens in a new tab)Copilot app projects and computer use
On October 28, 2026, the GitHub Copilot app added Projects in public preview. A project holds a goal plus context such as repositories, design mocks, Slack threads, or notes, and the models and tools for the job. Copilot runs as many agents as the work needs and brings back results, such as pull requests. Project automations can repeat a task, such as creating a promo video when a feature lands. A single-repository task can still start as a session from that repository. The app can use Slack and Figma context to research a request, draft a specification, or work through a design, and it can generate and edit images in chat. Computer use, in public preview on macOS and Windows, lets Copilot read app content, click controls, enter or edit text, and navigate across apps, including apps without an API, command-line interface, or MCP integration. Copilot asks for approval before controlling an app, and an organization can disable the feature in managed settings. Turn it on under Settings, Computer Use. On macOS, grant Accessibility and Screen Recording permissions.
Source for Copilot app projects and computer use (opens in a new tab)Copilot included with GitHub Enterprise
On October 28, 2026, GitHub said enterprises that work with a GitHub or Microsoft account team can get Copilot included with GitHub Enterprise for every licensed user. AI usage is metered from the first request against the enterprise budget, with no included usage allowance. Code completion and next edit suggestions keep working when no budget is available. Copilot Chat, Copilot code review, and Copilot in the cloud require available budget. An exhausted budget does not remove the seat. Users in the enterprise account who do not hold a GitHub Enterprise license get the same access through Copilot Standalone, at $10 per user per month. That access has the same features and models as Copilot Enterprise and does not include monthly AI credits per seat. It is available now for GitHub Enterprise Cloud customers who work with an account team. Self-serve availability is opening in stages, and current self-serve subscriptions are unaffected. Copilot Business and Copilot Enterprise remain available to purchase.
Source for Copilot included with GitHub Enterprise (opens in a new tab)Security extension for the Copilot app
On October 28, 2026, the GitHub security extension for the GitHub Copilot app entered public preview. Where code scanning is already enabled, it lists open code scanning alerts by severity, with search and filters, and can open an alert's details and affected code. Selecting one or more alerts and asking Copilot to Explain or Fix changes only the local working copy. It shows linked pull requests, and dismissing an alert is sent for approval when the organization uses delegated alert dismissal. /security-review checks the current changes and says when the code has changed since the last review. Install it with copilot plugin install github-security@awesome-copilot, or from Customize in the Copilot app. Explain, Fix, and /security-review use the selected model and consume AI credits. Browsing and dismissing alerts do not. Any Copilot plan can install the extension and run /security-review. Seeing, fixing, and dismissing existing alerts requires permission to view them. Private repositories need GitHub Code Security. Copilot Business and Copilot Enterprise need the GitHub Copilot app policy enabled. It runs on github.com and GitHub Enterprise Cloud with data residency, not on GitHub Enterprise Server.
Source for Security extension for the Copilot app (opens in a new tab)GitHub intelligence: memory, dreaming, and code search
On October 28, 2026, GitHub introduced GitHub intelligence for agents, with memory, dreaming, and code search. GitHub Copilot Memory is generally available on paid Copilot plans. Memories of personal preferences and repository conventions can be created in the Copilot app, Copilot CLI, VS Code, the Copilot cloud agent, Copilot code review, Slack, Teams, and GitHub Mobile. Sessions can generate and curate memories. GitHub says that among reviewed Copilot CLI public-preview sessions where the agent used memory, 93% showed better adherence to developer preferences and 42% showed more efficient workflows. Personal memories can be viewed or deleted in Copilot settings. Copilot dreaming, in public preview, is opt-in and consumes AI credits. Dream types are personal memory curation, repository customization (including proposed pull requests that update skills and custom instructions), and code review customization that turns recurring accepted review feedback into guidance. Individuals enable personal curation in Copilot settings and repository dreams per repository. Organization and enterprise administrators enable dreaming through Copilot policies. GitHub code search lets Copilot look across related repositories for exact text, symbols, regular expressions, and semantic matches, including through /research.
Source for GitHub intelligence: memory, dreaming, and code search (opens in a new tab)Shared Copilot Automations
On October 28, 2026, shared Copilot Automations started rolling out. A shared automation is visible to everyone with read access to the repository and editable by anyone with write access. AI credits are billed to the organization or user that owns the repository, and actions on GitHub are attributed to Copilot rather than to one person. The automation stays with the repository if its creator leaves, and change history records how the tools, triggers, and prompt evolved. When creating an automation on github.com, the GitHub Copilot app, or Visual Studio Code, choose Shared under Type. The type cannot be changed later. An organization-owned repository also needs the policy that allows use of the Copilot cloud agent billed to the organization. The rollout covers Copilot Pro, Pro+, Max, Business, and Enterprise, and availability may vary.
Source for Shared Copilot Automations (opens in a new tab)Copilot in VS Code, Universe releases
On October 28, 2026, GitHub Copilot in Visual Studio Code added ways to keep one agent session across clients and machines. A cloud agent session started from the Agents window keeps running on GitHub's infrastructure after the laptop closes, and the same session can continue in VS Code, the Copilot app, GitHub Mobile, github.com, or Copilot CLI, including sessions started in a Slack or Teams direct message. Agent Host isolates sessions from individual VS Code windows so work continues after the project window closes. Remote SSH and dev tunnels can run that host on another machine, which has to stay running. The editor and the Agents window stay on the same live session. From a project folder, code agent host --github-environment lets GitHub Mobile steer the agent on that machine. The Copilot harness, built on the Microsoft Copilot SDK, is now the default for new sessions. VS Code can install Copilot CLI through its Windows installer, when adding VS Code to the path on macOS, or by running copilot on Linux. The Agents window can run models and harnesses in parallel, ask a Judge model to recommend one, and use Synthesize to combine attempts. That comparison is in preview. Computer use is experimental: enable chat.agentHost.computerUse.enabled, restart, and run /computer on. Each application requires approval. The Agent Host Protocol lets another client connect to code agent host, with libraries for TypeScript, Rust, Go, Kotlin, and Swift. Customizations in the Agents window browse skills, MCP servers, and plugins. The Customization Marketplace is in preview. Administrators can require or block named plugins and marketplaces, and .github/copilot/settings.json can register default plugin marketplaces without enforcing them. Copilot connectors, in preview on all plans, connect a service such as Slack, Notion, or Microsoft Learn once and reuse it across Copilot clients on the Copilot harness. Business and Enterprise administrators need to allow Editor preview features for the marketplace and connectors.
Source for Copilot in VS Code, Universe releases (opens in a new tab)Image generation in Copilot chat
On October 28, 2026, GitHub Copilot chat can generate and edit images from natural language. The selected reasoning model calls an image-generation tool powered by GPT Image 2.5 Flare, previews the image inline, and saves it to the project. It works in VS Code, the GitHub Copilot app, and Copilot CLI. Organization and enterprise owners can turn it off by disabling the image generation model in Copilot model policies. A visible "Made with AI" watermark is opt-in and off by default. Image generation is in public preview for Copilot Pro, Pro+, Business, and Enterprise. It is billed separately from the chat model, based on image tokens that count toward the plan's AI credits.
Source for Image generation in Copilot chat (opens in a new tab)Copilot Fusion can route to local models
On October 28, 2026, GitHub Copilot Fusion added experimental routing between supported on-device models and cloud models in Copilot CLI, the Copilot app, and Visual Studio Code. On supported Windows devices, MAI Code 1.1 Flash can be downloaded through the Windows ML provider. In the CLI, enable experimental mode and follow the prompts in /model. In the app, configure Windows ML under Settings, Model providers, enable Local model auto routing under Settings, Experiments, and start a new session. Windows ML local models are enabled by default on Windows. In VS Code, enable chat.copilot.localModel.enabled. Select Standard in Copilot Fusion to let Copilot choose between local and cloud models, or select the local model directly. On Windows, macOS, and Linux, Copilot CLI can also route to a manually configured MAI Code 1.1 Flash or Qwen3.8 Flash Next served by a local OpenAI-compatible server. Discovering a model through bring-your-own-key configuration does not by itself make it eligible for Fusion. The Copilot app can select compatible local models through bring-your-own-key, but its intelligent routing currently supports managed Windows ML models only. Routing decisions still happen in the cloud, so local inference does not make the session offline.
Source for Copilot Fusion can route to local models (opens in a new tab)GitHub Agentic Workflows generally available
On October 28, 2026, GitHub Agentic Workflows became generally available. Markdown workflow files compile into GitHub Actions YAML and run a coding agent for tasks such as issue triage, CI failure analysis, documentation updates, and test writing. The default engine is GitHub Copilot CLI, which requires a Copilot license, and a workflow can bring its own coding agent. Agents follow integrity filter rules for GitHub content, run with read-only permissions by default, and execute in a sandboxed container behind the Agent Workflow Firewall. Outputs go through the safe outputs process, and a threat detection job scans proposed changes before they are applied. Since the public preview, workflows can run on Actions Runner Controller runners with Docker-in-Docker, gh aw forecast includes threat detection credits and monthly ranges, a model provider can be chosen per workflow, a model router can optimize for task type and difficulty, and agents can run in a Cloud Hypervisor or NVX micro-VM. It is generally available on github.com for GitHub Free, Team, and Enterprise.
Source for GitHub Agentic Workflows generally available (opens in a new tab)Copilot SDK is becoming Microsoft Copilot SDK
On October 28, 2026, GitHub said the GitHub Copilot SDK is becoming the Microsoft Copilot SDK, the programmable interface for the Microsoft Copilot harness used across Microsoft and GitHub products. The SDK repository, branding, and documentation are being updated in phases. Existing package names, namespaces, and some documentation may still say GitHub Copilot SDK during the transition. GitHub says no immediate changes are required for existing users, and support for the SDK stays the same.
Source for Copilot SDK is becoming Microsoft Copilot SDK (opens in a new tab)Copilot code review Max and approvals
On October 28, 2026, Copilot code review added Max, in public preview, and made Copilot approvals generally available for Copilot Pro, Pro+, Max, Business, and Enterprise. Max joins Lite and Balanced. It runs several independent review agents across models from different providers, then an aggregation agent reconciles their findings. Max takes longer and uses more AI credits than Lite or Balanced. It can be selected for one pull request or set as the default for a repository, organization, or enterprise, and each level can override the one above it. Administrators can set a maximum effort level so higher levels are unavailable. Approvals are off by default. When they are on, every review includes an approval assessment, and Copilot's approval counts toward required approvals. New commits dismiss that approval. Administrators turn approvals on at the enterprise, organization, or repository level, and repository administrators can limit which file paths Copilot may approve.
Source for Copilot code review Max and approvals (opens in a new tab)Agent Merge on GitHub pull requests
On October 28, 2026, Agent Merge was added to pull requests on GitHub. It was already available in the GitHub Copilot app and Visual Studio Code. Select Watch and fix in the pull request merge box and choose whether Copilot fixes failing Actions workflows, resolves merge conflicts, or both. When a selected blocker appears, Copilot works on it in a cloud development environment. Agent Merge can be enabled by default for every pull request you open, and it can be combined with auto-merge so GitHub merges the pull request once requirements are met. It is available on paid Copilot plans, subject to organization and enterprise policies.
Source for Agent Merge on GitHub pull requests (opens in a new tab)Cloud Copilot Automations in VS Code
On October 28, 2026, Copilot Automations in Visual Studio Code can run in the cloud. Personal scheduled automations keep running when Visual Studio Code is closed. Personal automations can also run on GitHub events, such as an issue being assigned or a pull request being opened, and shared cloud automations can be created for the repository. Update to Visual Studio Code 1.144 and enable chat.automations.cloud.enabled. Automations are in the Automations tab of the Agents window. Copilot Automations is available on Copilot Pro, Pro+, Max, Business, and Enterprise.
Source for Cloud Copilot Automations in VS Code (opens in a new tab)Copilot Automations can propose their own improvements
On October 28, 2026, Copilot Automations can learn from outcomes on GitHub and propose improvements to themselves. Examples GitHub gives are whether people change labels an automation applied, whether developers accept its review comments, and whether maintainers merge the pull requests it opens. A proposed change to the prompt, tools, or triggers is sent for review before it is applied. Asking Copilot to set up a self-improving automation can create a group, such as a review automation on new pull requests and a weekly automation that proposes refinements to it. Copilot Automations is available on Copilot Pro, Pro+, Max, Business, and Enterprise.
Source for Copilot Automations can propose their own improvements (opens in a new tab)Copilot Automations triggers, tools, and credit limits
On October 28, 2026, Copilot Automations added triggers, tools, and AI credit limits. The Trigger an automation REST API can start an automation from an external system. Twenty-four more GitHub events can start one, across issues, pull requests, discussions, and code scanning, secret scanning, and Dependabot alerts. A trigger's "Can be triggered by" setting defaults to Only users and can be set to Users and Copilot so another automation's event fires it. Automation run succeeded and Automation run failed triggers can chain automations. Twenty new GitHub tools include uploading image or video attachments, retrying workflow runs, merging pull requests, updating comments, marking a pull request ready or converting it to a draft, hiding comments and reviews, removing reactions, and reading or commenting on discussions. An automation can also use selected tools from a custom MCP server added in the repository's settings. Optional credit limits can be set per run, day, week, or month. A per-run limit stops that run. A daily, weekly, or monthly limit blocks new runs until the period resets. Automations without limits are unchanged. Copilot Automations is available on Copilot Pro, Pro+, Max, Business, and Enterprise, in repositories where you have write access.
Source for Copilot Automations triggers, tools, and credit limits (opens in a new tab)GitHub-verified Copilot connectors
On October 28, 2026, GitHub-verified MCP servers, called connectors, started rolling out in public preview. Connect a service once, with no local server to install, and use it in the GitHub Copilot app, Copilot CLI, VS Code, Copilot in the cloud, and GitHub Mobile. At launch, 26 services can be connected, including Slack, Figma, Notion, Sentry, Linear, Atlassian Rovo, Cloudflare, Vercel, and Work IQ. In the Copilot app, open Customize and select Connect. In Copilot CLI, run /mcp and use the Connectors tab. In VS Code, connect from Customizations in the Agents window. On github.com, use the Copilot customization page. Copilot uses a connected service's tools when they are relevant to the request, and the Copilot app can use a connected service in scheduled automations. The rollout covers all Copilot plans. Copilot Business and Copilot Enterprise need the Editor preview features policy. If an enterprise MCP allowlist is set in managed settings, an administrator also has to add GitHub-verified MCP servers to it. Some services also need an administrator to allow access on that service's side.
Source for GitHub-verified Copilot connectors (opens in a new tab)Connected Copilot cloud sessions
On October 28, 2026, GitHub made a connected Copilot cloud experience generally available on paid Copilot plans, rolling out starting October 28. A session can start on github.com, GitHub Mobile, Copilot CLI, the Copilot app, VS Code, or from Slack or Microsoft Teams, and continue on another of those surfaces with the same session list. By default, every session runs in a cloud sandbox on GitHub-managed infrastructure. Sandboxes have no one-hour limit on total running time, and a snapshot is saved when a sandbox shuts down so the session can resume later. Billing for cloud sandbox usage begins in November 2026. The included Actions entitlement is now one dollar-based pool for standard GitHub-hosted runners, cloud sandboxes, and, on Team and Enterprise Cloud, larger hosted runners, instead of a fixed number of standard runner minutes. Each product keeps its own published rate. Sessions that use Actions-based self-hosted runners or copilot-setup-steps.yml still need Actions as the environment. Running Copilot CLI with --environment-host registers your own computer or VM. Cloud sessions include Bash, the GitHub CLI, code search, connectors, custom MCP servers that use key-based authentication, skills, and slash commands such as /rubber-duck and /context on github.com and GitHub Mobile. On GitHub Mobile, a task can be described by voice or with an attached image or file. Access is governed by the Copilot in the cloud policy, and a repository previously opted out of the Copilot cloud agent stays opted out. Without write access to a repository, Copilot there is read-only. Copilot Free can keep using Copilot Chat on github.com and GitHub Mobile.
Source for Connected Copilot cloud sessions (opens in a new tab)Copilot in JetBrains, Universe releases
On October 28, 2026, GitHub Copilot in JetBrains IDEs added Copilot Fusion, with Standard, High, and Max effort levels. Fusion replaces the Auto model option and is rolling out gradually. GitHub says Fusion use is discounted 30% for the first 30 days. Local sandboxing is generally available, so tools and commands Copilot starts run with restricted access to the filesystem, network, credentials, and other system capabilities. Next edit suggestions are generally available. The Microsoft Copilot agent harness is the default when it is available. A session sidebar can open sessions side by side, and settings can choose the default permission mode for new sessions. The update also improves edit reliability, cancellation recovery, and selected-code context.
Source for Copilot in JetBrains, Universe releases (opens in a new tab)GitHub Copilot CLI 1.0.105
Released October 27, 2026. Selecting Copilot Fusion High or Max in /model now works from long-context sessions.
Source for GitHub Copilot CLI 1.0.105 (opens in a new tab)Copilot server-to-server authentication
On October 27, 2026, GitHub Copilot added server-to-server authentication for GitHub Apps installed on organizations, in public preview. Services and agents built with the Copilot SDK can make requests for an organization with a short-lived installation access token, without a signed-in user's credentials. The app needs the read-only Copilot Requests organization permission and must be installed on the organization. Usage is attributed and billed to the organization that owns the installation, and that organization's model policies, budgets, and spending controls apply. Organization owners can see which apps have access, find app-attributed usage in AI usage CSV reports in the app_client_id field, and stop an app by suspending or uninstalling it.
Source for Copilot server-to-server authentication (opens in a new tab)GitHub Copilot CLI 1.0.104
Released October 27, 2026. The managed model fusion starts sessions on Auto and applies fusionTier settings. Interactive and SDK Autopilot sessions keep waiting for attached background tasks instead of stopping after COPILOT_TASK_WAIT_TIMEOUT_SECONDS; -p --autopilot still honors that timeout. When a saved Auto preference is no longer available, Auto falls back to its default preference instead of failing each turn. Assisted Permissions are available without enabling experimental mode.
Source for GitHub Copilot CLI 1.0.104 (opens in a new tab)GPT-6.1 Terra in GitHub Copilot
On October 26, 2026, GPT-6.1 Terra became generally available in GitHub Copilot. GitHub says it is designed for everyday agentic coding and terminal work at a lower cost than GPT-6.1 Sol, and that in early testing it solved noticeably more terminal and C# coding tasks than GPT-5.6 Terra. It is available to Copilot Pro, Pro+, Max, Business, and Enterprise users in the model picker in Visual Studio Code, Visual Studio, Copilot CLI, the GitHub Copilot cloud agent, the GitHub Copilot app, github.com, GitHub Mobile on iOS and Android, JetBrains IDEs, Xcode, and Eclipse. Rollout is gradual. It is billed at provider list pricing under usage-based billing. Copilot Enterprise and Copilot Business admins manage access through the model policy. Under default model enablement, new models are enabled unless an admin has turned off the global default or disables this model.
Source for GPT-6.1 Terra in GitHub Copilot (opens in a new tab)Copilot assisted permissions generally available
On October 26, 2026, assisted permissions became generally available in GitHub Copilot CLI, the GitHub Copilot app, and Visual Studio Code. When Copilot requests permission to run a command, access a file system path, or open a URL, a large language model evaluates the request. Requests classified as clearly safe proceed automatically. Other requests require approval. In the CLI, run /permissions and select assisted. In the Copilot app, open the mode picker, click Tool permissions, and select Assisted. In Visual Studio Code, open the permissions picker and select Assisted permissions. Enterprise admins can block Allow All while keeping Assisted available, or disable Assisted separately, and can choose the default permission mode for new sessions. If that default is unavailable or prohibited by policy, the session starts with manual approval.
Source for Copilot assisted permissions generally available (opens in a new tab)
Alternatives
Devin Desktop (7.3), Zed (7.5), Continue (7.1).
FAQ
- Should I pick Cursor or GitHub Copilot?
- Pick Cursor for this job: Daily driving an AI editor on a real repo. Pick GitHub Copilot for this job: Adding an agent without leaving the editor you have. Cursor scores 8.6 and is #1 in AI code editors. GitHub Copilot scores 7.8 and is #2 in AI code editors.
- What do Cursor and GitHub Copilot cost?
- Cursor: Free tier and paid plans. Current prices: check site. GitHub Copilot: Free tier and paid plans (Pro and above). Current prices: check site.
- Are these scores benchmarks?
- Initial editorial estimate. Not a measured benchmark. Price means value for an indie budget, not the sticker price.
- Do affiliate links change Cursor or GitHub Copilot’s rank?
- Affiliate links may be used to monetize, but they never affect scores or rankings, and rankings are never sponsored.
Initial editorial estimate. Not a measured benchmark. Prices: check each vendor’s site. How scores work.
Some links may earn us a commission. It never changes scores or order.
Newsletter
Get this comparison when the scores move
Cursor vs GitHub Copilot. One email when rankings change or one of these tools ships something that matters. No spam, unsubscribe anytime.