Pick GitHub Copilot for AI in every editor your team uses and on GitHub, billed from one pool of AI credits; pick Claude Code for Anthropic's terminal-first agent on Claude alone. Copilot's cloud agent and CLI read CLAUDE.md and load .claude/skills, so one repo can serve both.
Zest reads each engineer's Claude Code and GitHub Copilot Chat sessions (model, tokens, skills and MCP tools), joins them to the pull requests they led to, and shows both side by side. One workspace price: 5 engineers pay $49/mo on Pro.
$100/mo — Claude Team Standard at $20 a seat, billed annually ($25 monthly).[7]
$95/mo — Copilot Business at $19 a seat, with 1,900 pooled AI credits.[8]
Where it runs
Terminal CLI, VS Code and JetBrains extensions, a desktop app, the web and mobile, plus Slack and GitHub Actions.[3]
Agent mode in VS Code, Visual Studio, JetBrains, Xcode and Eclipse; the Copilot CLI and app; a cloud agent on GitHub.[1]
Models
Claude models only (Fable, Opus, Sonnet, Haiku); Anthropic doesn't support routing Claude Code to other models.[4]
OpenAI, Anthropic, Google, xAI (Grok) and other vendors' models, picked per chat.[9]
Project instructions
CLAUDE.md and .claude/rules/; AGENTS.md only when there is no CLAUDE.md, or through an @import.[10]
.github/copilot-instructions.md and .github/instructions; AGENTS.md in VS Code chat, and AGENTS.md and CLAUDE.md in the cloud agent and CLI.[5]
Skills, subagents and hooks
Skills (SKILL.md, invoked as /skill-name), custom subagents in .claude/agents, and lifecycle hooks.[11]
Agent skills (.github, .claude or .agents skills), custom agents, prompt files and hooks.[6]
MCP servers
Local stdio or remote HTTP MCP servers, added with claude mcp add.[12]
In IDEs, the CLI, the app and the cloud agent; for Business and Enterprise the MCP policy is off by default.[13]
Team analytics, built in
Team and Enterprise dashboard: daily users, sessions, lines accepted, accept rate and PRs with Claude Code; API on Enterprise.[14]
A 28-day usage metrics dashboard, code generation and impact dashboards, and a per-user REST API.[15]
Checking your own usage
/usage (also /cost and /stats) shows plan usage, session cost and a 24h/7d breakdown by skill, subagent and MCP server.[16]
Copilot settings show usage this cycle in AI credits; the Copilot CLI's /usage shows tokens and credits per model.[17]
Each tool's column is read from its vendor's own docs and pricing page, dated in the sources below.
ON YOUR OWN TEAM
Measure both with Zest
Claude Code and GitHub Copilot Chat sessions side by side, per engineer
The model, skills and MCP tools behind each session
Which tool's sessions end in merged pull requests
A daily standup written from both
Winding /Teams Last 30 days
Zest
3 Members 1 Agent
Team overview
67%
AI Adoption▲ 34 pts
240
PRs Merged▲ 101
96.1h
Median AI Time▲ 9.5h
57.2h
Build Hours▲ 20.3h
This week
Member
AI
PRs/wk
AI Task
Plan
Impl
Last Standup
AI Stack
22.8/wk
28 min ago
15.8/wk
12 min ago
4/wk
Aug 14
—
2 hours ago
Current AI models & harnesses As of Sep 8
Claude CodeFable 5.1 (max) (with fallback)70.4 · Coding Agent Index
CodexGPT-6 Astra (max)67.0 · Coding Agent Index
Muse CodeMuse Spark 1.3 (xhigh)64.2 · Coding Agent Index
Grok BuildGrok 4.5 (high)64.1 · Coding Agent Index
Kimi Code CLIKimi K362.6 · Coding Agent Index
OpencodeGemini 3.8 Flash (high)61.2 · Coding Agent Index
Cursor CLIComposer 2.5 Fast38.3 · Coding Agent Index
Demo setups use current model families. The pairings above are the combinations benchmarked by Artificial Analysis; rankings measure performance, not popularity.
Illustrative daily trends · Other totals: last 30 days. Build Hours: this week, model-estimated activity including overlap; not engineer hours.
USED BY ENGINEERING TEAMS AT
Claude Code or GitHub Copilot: which one fits your team
Pick Copilot if your team works across editors. Agent mode runs in VS Code, Visual Studio, JetBrains IDEs, Xcode and Eclipse, every plan includes the Copilot CLI and app, and a cloud agent works on GitHub. Each chat picks a model from OpenAI, Anthropic, Google, xAI and others. Inline completions stay unlimited on paid plans, and Business seats pool their AI credits across the organization.
Pick Claude Code if your engineers want an agent in the terminal on Claude models only, and the same agent in VS Code, JetBrains, a desktop app and the web. It comes with every paid Claude plan, and each seat has its own allowance, reset on a rolling five-hour window with a weekly limit on paid plans.
The two meet on GitHub. On Copilot's paid plans you can assign an issue to Anthropic Claude as a third-party coding agent, in public preview: it runs on the Claude Agent SDK with Sonnet, Opus and Fable models, and bills GitHub Actions minutes and AI credits, not a Claude plan.
Claude Code vs GitHub Copilot: config files and commands
Copilot reads several Claude Code files: its cloud agent, CLI and code review read CLAUDE.md, and it loads skills from .claude/skills. Copilot Chat in VS Code is the exception. It reads AGENTS.md and .github/copilot-instructions.md, not CLAUDE.md.
From Claude Code's and GitHub Copilot's docs, read October 5, 2026.
Claude Code
GitHub Copilot
Instructions
CLAUDE.md and .claude/rules/; AGENTS.md only when there is no CLAUDE.md
.github/copilot-instructions.md, .github/instructions/, AGENTS.md; CLAUDE.md in the cloud agent and CLI
Skills
.claude/skills/<name>/SKILL.md, run as /name
.github/skills, .claude/skills or .agents/skills
Subagents
Markdown files in .claude/agents/
Custom agents in .github/agents/
Hooks
hooks in .claude/settings.json
.github/hooks/*.json
MCP servers
claude mcp add; shared servers in .mcp.json
servers in .vscode/mcp.json; repository settings for the cloud agent
From a script
claude -p "…"
copilot -p "…" (the Copilot CLI)
Pull request review
@claude through GitHub Actions; Code Review on Team and Enterprise
Copilot code review, requested or automatic
MCP servers: .mcp.json vs .vscode/mcp.json
The same MCP server needs two entries under two different keys: mcpServers in Claude Code's .mcp.json, servers in VS Code's .vscode/mcp.json. On Copilot Business and Enterprise seats, MCP stays off until an admin turns on the MCP servers in Copilot policy.
Claude Code and GitHub Copilot, from each vendor's pricing page in October 2026:
Claude Code comes with Claude Pro at $20 a month ($17 billed yearly), Max from $100 and Team seats at $25 ($20 billed yearly). Every plan's limits reset on a rolling five-hour window, and paid plans add weekly limits on top. More on Claude Code pricing.
Copilot Business is $19 a seat, with 1,900 pooled AI credits.
What our own team can tell you
Copilot isn't in our numbers. Of the 866 agent-written pull requests merged in our two repos from August 12 to October 4, 2026, Claude Code wrote 822, Codex 31 and Copilot none, so this page compares the two tools' docs, not our results.
Running Claude Code and GitHub Copilot on one repository
Put the instructions both should follow in AGENTS.md: Copilot reads it in VS Code chat, the cloud agent and the CLI, and Claude Code reads it when there is no CLAUDE.md, or through @AGENTS.md in one, as below. Put skills in .claude/skills, which both load. GitHub's own numbers for Copilot are in Copilot usage metrics.
CLAUDE.md
@AGENTS.md
## Claude Code
Use plan mode for changes under `src/billing/`.
TRY IT ON YOUR TEAM
See what your team ships with AI.
Starter is free (3 seats, no credit card). Pro is $49 a month with 5 seats and Max is $149 a month with 10 seats — priced per workspace, not per engineer, with extra seats at $19 a month.
Copilot, for a team on many editors that wants pooled credits and inline completions; Claude Code, for terminal-first work on Claude models. Copilot offers Claude models too, so the choice is the agent and the billing more than the model.
Can GitHub Copilot run Claude?+
Yes, two ways: Claude models such as Opus 5.5 in Copilot's model picker, and Anthropic Claude as a coding agent on GitHub, in public preview. Both draw on Copilot's AI credits, not a Claude plan.
Does Zest capture Copilot inline completions?+
No. Zest's VS Code extension reads Copilot Chat sessions (the models, skills and tools each one used), and GitHub's own metrics stay the source for completions.