Claude Code, Codex and Cursor vs GitHub Copilot

GitHub Copilot in September 2026 is a full coding-agent platform: a cloud agent in GitHub Actions, a desktop app, a CLI, hooks, MCP, Agent Skills, and, on Pro+ and above, the same frontier models Claude Code and Codex use. Claude Code, Codex, and Cursor differ from Copilot in harness depth, where the agent runs, hard session limits, and billing, not in whether the agent can act.

Your company pays for Copilot Business. Two engineers ask for Claude Code, one wants Cursor, and finance asks whether that is a second bill for the same thing. Many comparisons still describe the 2023 autocomplete Copilot, so they answer a question nobody is asking any more.

This page is for the developer choosing a primary agent and for the tech lead or CTO deciding whether a second tool earns its cost. It is the head-to-head. For Copilot’s own surfaces, setup and billing in depth, see GitHub Copilot as a coding agent.

What this Copilot comparison gives you

• A side-by-side table of Copilot, Claude Code, Codex, and Cursor on the axes that decide the choice, each fact dated.
• A decision table that maps your situation to a primary agent.
• A same-issue bake-off you can run this week, with two copy-paste prompts and the command that starts each agent.
• The verification gates that make the result trustworthy without anyone reading every line.
• The comparison mistakes that produce the wrong answer, and how to undo them.

How does GitHub Copilot compare with Claude Code, Codex, and Cursor?

Copilot facts below were checked on 2026-09-26 against GitHub’s docs source, and its models and billing cells were re-checked on 2026-10-12 against GitHub’s docs source and changelog. Claude Code facts were checked on 2026-09-26 against the Claude Code docs and Codex facts against the Codex CLI 0.157.1 and its repository, except the default-model cells and the Codex billing cell, which were updated on 2026-10-12. Cursor facts were read on cursor.com on 2026-10-12, except the hard-limits cell, which stays unverified.

Axis	GitHub Copilot	Claude Code	Codex	Cursor
Background agent	Cloud agent in an ephemeral GitHub Actions environment; start it from an issue, the Agents tab, @copilot on a pull request, Slack, Teams or an automation	Claude Code on the web, Routines, claude-code-action@v1 in GitHub Actions, GitLab CI/CD	Codex cloud, codex exec in any CI, openai/codex-action@v1	Cloud Agents in isolated VMs; Automations on schedules, Slack, Linear and webhooks
Local agent	Copilot CLI, the desktop Copilot app (Interactive, Plan, Autopilot), agent mode in VS Code and JetBrains	CLI, desktop app, VS Code and JetBrains extensions	CLI, desktop app (codex app, macOS and Windows), IDE extension	The Cursor editor’s agent and the Agents Window, with Agent, Ask, Plan and Debug modes; the agent CLI
Instruction files	.github/copilot-instructions.md, .github/instructions/**/*.instructions.md, and agent instructions such as AGENTS.md	CLAUDE.md; reads AGENTS.md when there is no CLAUDE.md (v2.1.277+)	AGENTS.md	Rules in .cursor/rules/*.mdc; reads AGENTS.md in the project root and subdirectories, and CLAUDE.md the same way
Extensibility	Hooks, MCP (GitHub and Playwright servers on by default for the cloud agent), Agent Skills via gh skill, custom agents	Hooks (33 events), subagents, skills, plugins and marketplaces, MCP	Hooks, subagents, skills, plugins, MCP, rules	Hooks, subagents, skills, plugins, MCP, rules
Headless and scripted runs	copilot -p "…" with --allow-tool / --deny-tool	claude -p with --output-format json	codex exec with --output-schema	agent -p "…" in the Cursor CLI
Parallel work	App sessions each on their own worktree and branch; several cloud-agent tasks	--worktree, background sessions, /batch, subagents	--worktree, subagents, cloud tasks	Worktrees, subagents, Cloud Agents
Review of agent pull requests	Copilot code review; by default the cloud agent also runs security validation and a Copilot code review pass before finishing (a repository admin can switch these off)	/code-review, Ultrareview, managed Code Review (Team and Enterprise; generally available per Anthropic, checked 2026-10-16)	/review, codex review, @codex review on GitHub and GitLab	Bugbot
Models	A multi-vendor picker: Claude Opus 5.5, GPT-6.1 Sol, GPT-6 Astra and GPT-6 Sol on Pro+, Max, Business and Enterprise (not Pro), Claude Sonnet 5.5 and Claude Haiku 5.5 on all five paid plans, plus Gemini, Grok, Kimi and Microsoft models (checked 2026-10-12)	Default Claude Opus 5.5 (v2.1.280+)	Default GPT-6.1 Sol (Codex CLI 0.159.1+)	No single default model (Cursor, checked 2026-10-12)
Billing	Usage in GitHub AI Credits ($0.01 each) since 2026-06-01, plus Actions minutes for the cloud agent	Subscription plans with five-hour and weekly windows, or API rates	Included in ChatGPT Plus, Pro, Business, Edu and Enterprise; Plus and Business show local-message estimates per five hours, weekly limits may apply, and “Pro plans currently have no five-hour limit” (OpenAI pricing page, checked 2026-10-12)	Subscription plans (Pro, Pro+, Ultra, Teams) with included usage, then pay-as-you-go at the model’s API rate (cursor.com, checked 2026-10-12)
Hard limits	Cloud agent: one repository, one branch and one pull request per task, 59-minute sessions, GitHub-hosted repositories only	Plan usage windows	Plan usage windows	Not re-verified for this date

Two rows decide most choices. The models row shows that the model is no longer a reason to switch: a Copilot Pro+ or Business seat already reaches Claude Opus 5.5, GPT-6.1 Sol and GPT-6 Astra. The hard limits row shows where Copilot’s cloud agent stops: work that spans repositories, runs longer than an hour in one session, or lives outside GitHub. Current model prices are on the models hub, and plan prices are in the pricing analysis.

Which agent should be your primary tool?

Start from where your work comes from and how you prove it is done, not from a feature list.

Your situation	Primary agent	Why
Code on GitHub, work arrives as small, well-specified issues, one bill matters	GitHub Copilot	The cloud agent turns an issue into a pull request inside your existing permissions, checks and billing
Engineers live in the terminal and want deterministic hooks, subagents, plugins, and claude -p in scripts	Claude Code	The deepest local harness of the four; see Claude Code
You want GPT-6.1 Sol (Codex’s default since CLI 0.159.1) or GPT-6 Astra in OpenAI’s own harness, codex exec in CI, or review mentions on GitLab	Codex	Codex’s harness and cloud tasks are not tied to GitHub; see Codex
Engineers want an IDE-first agent with visual diffs and cloud agents started from the editor	Cursor	Plans are compared in the pricing analysis and models on the models hub; see Cursor
Code on GitLab, Bitbucket, or self-hosted Git	Claude Code or Codex	Copilot’s cloud agent works only with repositories hosted on GitHub
Tasks regularly exceed an hour or touch several repositories	Claude Code, Codex, or Cursor for those tasks	The cloud agent’s 59-minute cap and one-repository scope cannot be extended
You already pay for Copilot and want a first look at Claude and Codex before buying seats	Copilot’s third-party Claude and Codex agents	They run inside your Copilot subscription (public preview), but in Copilot’s cloud environment, not the Claude Code or Codex CLI harness, so they preview the models and agent loop, not your local hooks and plugins

If you already pay for Copilot, the practical question is rarely “which one tool”. It is whether a second agent earns its cost for specific task classes while Copilot keeps the issue-sized backlog work. Adding Claude Code or Codex alongside Copilot covers that setup and a two-week pilot. For Claude Code against Cursor, see Cursor vs Claude Code.

Run a same-issue bake-off between Copilot and another agent

A comparison you run on your own repository beats any table, including the one above. You need a repository with CI, one issue written as a spec, and the setup-steps workflow for Copilot; the rest is the agents’ run time.

1. Pick one real issue of the class you care about. A cross-module refactor, a dependency upgrade, or a small feature. Avoid toy tasks: every agent passes them.

2. Give every agent the same instructions. Copilot, Codex, and Claude Code can all read AGENTS.md, but Copilot also reads .github/copilot-instructions.md and Claude Code prefers CLAUDE.md when one exists. If those files disagree, you are comparing instruction files, not agents. Run the parity audit prompt below first, and keep one source with rules sync. For Cursor, generate its Rules from the same source with rules sync.

3. Write the issue as a spec with testable acceptance criteria. Use the task prompt below as the issue body. Criteria an agent can check are covered in acceptance criteria.

4. Start each agent on its own branch. Use the tabs below. Where you can, pin the same model family in each tool, so the result measures the harness.

5. Score the pull requests with the same gates. CI result on first push, acceptance criteria proven by a test, files changed outside scope, and rework needed. The scoring prompt and the pilot measures are in the Copilot pilot guide; the site’s one bake-off protocol for more than two agents is in the coding-agent landscape.

Copy-paste prompt: audit instruction parity before a bake-off

Audit this repository's agent instruction files before we compare coding agents.

1. List every file an agent may read as instructions: AGENTS.md at any depth,
   CLAUDE.md, .github/copilot-instructions.md, .github/instructions/**/*.instructions.md,
   and any Cursor rules directory.
2. For each file, extract the build, test, lint and typecheck commands, the forbidden
   actions, and the coding conventions it states.
3. Output a table: one row per rule, one column per file, marking where a rule is missing
   or contradicts another file (for example two different test commands).
4. Propose a single AGENTS.md that contains every rule once, and list which files should
   then only point to it.

Do not edit any file. Report only.

Copy-paste prompt: the bake-off task, used unchanged for every agent

Add per-IP rate limiting to POST /api/auth/login.

Context: the Express app is in src/server/, routes in src/server/routes/auth.ts,
middleware in src/server/middleware/. Follow the middleware pattern in
src/server/middleware/requestId.ts. Do not add a new dependency if the existing
stack can do this.

Acceptance criteria (each needs a test that fails before your change):
1. The sixth failed login from one IP within 60 seconds returns 429 with a Retry-After header.
2. A successful login resets that IP's counter.
3. Requests from other IPs are unaffected.
4. The limit and window come from config, with defaults 5 and 60 seconds.

Before you finish: run the full test suite, lint and typecheck, and paste the exact
commands with their last lines of output. In the pull request description, map each
criterion to the test that proves it, and list any file you changed outside
src/server/ with the reason.

Replace the paths with a real endpoint and middleware from your repository; keep the four-part structure of context, criteria, gates, and evidence.

GitHub Copilot

Paste the task prompt as the body of a new issue and assign the issue to Copilot, or start it from the Agents tab and pick a model. Make sure .github/workflows/copilot-setup-steps.yml installs your toolchain, or the agent cannot run your tests. To run the same issue through the Claude or Codex agent inside Copilot, assign the issue to that agent instead. By default, workflows on the agent’s pull request wait until someone clicks Approve and run workflows; a repository admin can turn that requirement off, which GitHub warns exposes Actions secrets to unreviewed code.

Claude Code

Start a session on its own worktree and paste the task prompt:

claude --worktree rate-limit-login

Claude Code starts in auto mode on v2.1.283 or later (both release channels on 2026-10-12) for interactive sessions. Press Shift+Tab to switch to plan mode first if you want to approve the plan before any edit. Push the branch and open the pull request from the session.

Codex

Start a session on a managed worktree and paste the task prompt:

codex --worktree

Codex asks before it leaves its sandbox under the default on-request approval policy. Use /review before you push, so Codex reviews its own diff against the criteria.

Cursor

Open the agent on a separate worktree, switch to Plan Mode, and paste the task prompt. Approve the plan, let the agent implement it, and open the pull request. To run it in the background instead, start a Cloud Agent from the same prompt.

How do you verify the bake-off result without reading every line?

The comparison is only as good as the checks both pull requests must pass. Use the same gates for every agent and let a human judge the evidence, not the code style.

• Same required checks. Branch protection runs your type check, lint, and tests on every pull request, whichever agent opened it. A red check on first push counts against that agent.
• Criteria mapped to tests. Each pull request description must map every acceptance criterion to a test. An unmapped criterion counts as unproven. This is the evidence bundle reviewers read instead of the diff.
• Built-in scanning, where it exists. By default the Copilot cloud agent runs security validation (checks for issues such as hardcoded secrets and insecure dependencies) and a Copilot code review pass before it finishes. A repository admin can switch these off under Settings → Copilot → Cloud agent → Validation tools, so confirm they are on before the bake-off. Run equivalent scanners in CI for the other agents, so no agent gets a free pass.
• An independent reviewer. Review each pull request with an agent from a different vendor than its author, for example Copilot code review on the Claude Code branch and /code-review on the Copilot branch. Reviewing agent pull requests covers the layered review.
• Rework after merge. Track fix commits to the same files for 14 days. A fast pull request that needs a follow-up fix loses to a slower one that does not.
• A named human signs off. The engineer who owns the acceptance criteria approves the merge and records which agent won and why. On the Copilot branch, the approval of the person who assigned the issue does not count toward the repository’s required approvals, as GitHub documents, so name a second approver in advance.

What goes wrong when teams compare Copilot with other agents?

• The comparison describes old Copilot. Tables that mark Copilot “No” for multi-file edits, command execution, or MCP are out of date. Re-check against GitHub’s docs and date every cell, as the table above does.
• Different models, different conclusions. Copilot on a cheap model against Claude Code on Claude Opus 5.5 measures the model. Pin the same family in both tools, or run two rounds and report both.
• The cloud agent times out on a large task. A session stops at 59 minutes and cannot be extended. Split the issue into smaller ones, or give that task class to a local agent.
• The cloud agent never opens a pull request. A ruleset or branch protection rule the agent cannot satisfy, such as one that allows only specific commit authors, blocks it. For rulesets, add Copilot as a bypass actor, as GitHub documents.
• Setup steps are missing, so tests never run. Without copilot-setup-steps.yml the cloud agent cannot install your toolchain, and its pull request arrives unverified. Run the workflow from the Actions tab until it is green.
• Instruction files disagree. Two test commands in two files produce two different “correct” answers. Run the parity audit and keep one source.
• A pinned model disappears. Claude Opus 4.7, Kimi K2.7 Code, Gemini 3.5 Flash, and Gemini 3.6 Flash left Copilot on 2026-10-02 (GitHub’s changelog names Claude Opus 5.5, Kimi K3 and Gemini 3.8 Flash as replacements, and GitHub’s deprecation table lists no further retirement, checked 2026-10-12). Re-run the bake-off on the replacement before you draw conclusions.
• Cost is compared per seat only. Copilot bills AI Credits and Actions minutes; the others bill usage windows or API rates. Compare cost per merged, non-reverted pull request, as the economics of agent-built software defines it.

Where to go next with the Copilot decision

• GitHub Copilot as a coding agent: the cloud agent, the app, the CLI, billing, and org policy in depth.
• Adding Claude Code or Codex alongside Copilot: one repository for two agents, and a two-week pilot.
• The coding-agent landscape beyond the big three: Copilot next to Gemini CLI, Kiro, OpenCode, and the rest.
• Background and cloud agents compared: Copilot’s cloud agent next to Claude Code on the web, Codex cloud, and Cursor Cloud Agents.
• Pricing analysis: plan prices for every tool on one page.
• Avoiding lock-in: which assets travel between agents and which do not.