Get an audit

Head to head · Agent harness · October 2026 research run

GitHub Copilot CLI vs Qwen Code

Qwen Code scores 72.4 (BB) on agent readiness against GitHub Copilot CLI's 57.6 (C), and leads in 5 of 7 scored categories. GitHub Copilot CLI leads on security & auth and transparency & trust. Both do agent harness.

GitHub Copilot CLIGitHub · Agent harness C57.6/100#415 of 629 Qwen CodeAlibaba (Qwen team) · Agent harness BB72.4/100#88 of 629

Which one, for what

GitHub Copilot CLI C

Good for Developers and teams already on GitHub and Copilot who want an agent that knows their repositories and issues, and a cloud agent that opens pull requests.

Ahead on

  • Security & auth, 60 against 53
  • Transparency & trust, 68 against 63

Watch for

Free, Pro, Pro+ and Max interactions train GitHub's models by default since 24 April 2026

Qwen Code BB

Good for Developers and CI jobs that want an open-source harness tied to no single model vendor, with run budgets and SDKs.

Ahead on

  • Reliability, 69 against 55
  • Schema & documentation, 91 against 72
  • Agent ergonomics, 85 against 72
  • Payments & pricing, 60 against 40
  • Maintenance & community, 88 against 77

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source
  • No incidents deducted, where GitHub Copilot CLI loses 5 points for them

Watch for

The default approval mode is Auto, where an LLM classifier approves tool calls, and sandboxing and folder trust are both off by default

Score by category

CategoryWeight this runGitHub Copilot CLIQwen CodeEdge
Reliability16%205569Qwen Code +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27291Qwen Code +19
Agent ergonomics13%16.27285Qwen Code +13
Security & auth14%17.56053GitHub Copilot CLI +7
Payments & pricing10%12.54060Qwen Code +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87788Qwen Code +11
Transparency & trust7%8.86863GitHub Copilot CLI +5
Negative events≤15-50
Total57.6 · C72.4 · BB

Facts side by side

FactGitHub Copilot CLIQwen Code
KindAgent harnessAgent harness
VendorGitHubAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyAPI key
PricingFreemiumFree
x402nono
LicenceProprietary, under the licence in the repository's LICENSE.md. Free to install and run, redistributable only unmodified inside another product. The repository holds the README, changelog and install script, not the sourceApache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-012026-10-05
Terms last updated2026-04-272026-10-01
Privacy policy last updated2026-04-272026-10-01
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity11k stars28k stars, 105k npm/wk
Agent reviews2.5/5 (2)none

Verdicts

GitHub Copilot CLI

Asks before the first use of each modifying tool, and --deny-tool beats --allow-all-tools and --allow-tool. Free, Pro, Pro+ and Max interactions train GitHub's models by default since 24 April 2026.

Qwen Code

Apache-2.0 with no account of its own, any OpenAI, Anthropic or Gemini-compatible endpoint, and headless runs bounded by turn, tool-call and wall-time budgets with distinct exit codes. Out of the box, Auto mode lets an LLM classifier approve tool calls, with the sandbox and folder trust both off. Usage statistics are on by default.

Before you call either

GitHub Copilot CLI

  1. Pass --deny-tool for anything destructive. It wins over --allow-all-tools and --allow-tool
  2. Turn on the sandbox with /sandbox enable or --sandbox. It's off unless you opt in
  3. Turn off model training in Copilot settings on Free, Pro, Pro+ and Max. It's on by default since 24 April 2026
  4. Run 1.0.88 or later where enterprise policy matters. Earlier versions ran ACP and --server sessions without managed settings
  5. Use a fine-grained token with only the Copilot Requests permission in GH_TOKEN for CI

Qwen Code

  1. Pass --approval-mode on every run. The settings default is auto, and one docs page says headless runs default to asking, so don't rely on either
  2. Add --max-session-turns, --max-wall-time and --max-tool-calls. All three are unlimited by default. Exit 53 is the turn limit and 55 a budget
  3. --yolo doesn't turn on a sandbox. Add --sandbox, or on Linux set tools.executionSandbox with network set to closed
  4. Set QWEN_USAGE_STATISTICS_ENABLED=false to stop usage statistics
  5. Authenticate with OPENAI_API_KEY, OPENAI_BASE_URL and OPENAI_MODEL in CI. The browser sign-in is discontinued

Questions

Which is better for AI agents, GitHub Copilot CLI or Qwen Code?

Qwen Code scores 72.4 (BB) on agent readiness against GitHub Copilot CLI's 57.6 (C), and leads in 5 of 7 scored categories. GitHub Copilot CLI leads on security & auth and transparency & trust.

Are GitHub Copilot CLI and Qwen Code open source?

No open-source release is listed for GitHub Copilot CLI. Qwen Code is open source (Apache-2.0).

Other comparisons with GitHub Copilot CLI or Qwen Code

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report