Head to head · Agent harnesses · October 2026 research run

GitHub Copilot CLI vs goose

goose scores 75 (BB) on agent readiness against GitHub Copilot CLI's 58.5 (C), and leads in 6 of 7 scored categories. GitHub Copilot CLI leads on transparency & trust. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

GitHub Copilot CLI C

Best 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

  • Transparency & trust, 74 against 67

Watch for

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

goose BB

Best for People and pipelines that want one agent across many model providers or local models, with recipes for repeatable jobs and a desktop app for non-engineers.

Ahead on

  • Reliability, 77 against 55
  • Schema & documentation, 81 against 72
  • Agent ergonomics, 82 against 72
  • Security & auth, 77 against 65
  • Payments & pricing, 90 against 60
  • Maintenance & community, 86 against 77

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it
  • Open source

Watch for

Autonomous mode, which approves every tool call, is the default

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing goose +30

GitHub Copilot CLI 60

Harness reading of the published rubric. No payment protocol (0). Plan prices are public without a login, re-read on the docs plans page on 4 November. Pro $10, Pro+ $39, Max $100 a month, Business $19 and Enterprise $39 a seat, with usage past an organisation's pool at $0.01 per AI credit (20). Copilot Free includes the CLI with an allowance of AI credits and auto model selection only, and no card per the 2 October check (20). A person signs in to GitHub or creates the token (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

goose 90

No payment protocol (0). Free and Apache-2.0 with nothing to buy, so 20, 20 and 20 on the last three lines. It runs local models, including built-in local inference, with no signup. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Reliability goose +22

GitHub Copilot CLI 55

Local-package reading. npm, Homebrew, WinGet and an install script for Linux, macOS and Windows, with PowerShell 6 or newer named for Windows, though the npm package declares no engines, per the 17 October check (20). No public CI or test suite, since the source isn't published, and the repository holds only the README, licence, changelog, install script and a container folder, per a clone on 4 November (0). About 1,900 open issues and 28 open pull requests, labelled by area and platform with a triage label and no-response automation, per the 1 October check, not re-read on 4 November (12). A dated changelog for every release, with breaking changes marked BREAKING, though they ship in 1.0.x patch versions, and 1.0.103 removed the --no-remote flag without the label (8). 1.0 since March 2026, at 1.0.105 on 27 October per the changelog and tag (15). Same reading as Claude Code and Cursor CLI, which are also closed source. 20+0+12+8+15 = 55.

goose 77

Read as a local package, which is how the 1 October dossier read it. Desktop builds and a CLI for macOS, Linux and Windows (a Windows NSIS installer from 1.56.0), Homebrew casks, a download script on GitHub releases, an npm package that installs the binary (@aaif/goose-acp) and a GHCR image, with Rust 1.94.1 as the minimum for source builds (20). A CI workflow runs on every push to main, with cargo-deny, cargo-machete, MCP and tool-call conformance and an OpenSSF Scorecard job beside it. The Actions page loaded on 1 October showed only passing runs from March 2026, and GitHub pages refused our requests on 6 and 17 October and 1 November, so the current state is unconfirmed (18). 266 to 271 open issues on 1 October, many from that week with no reply, including open reports that the default mode approves every tool call (#12567) and that schedules can overwrite each other (#12613), per the 1 October check, not re-read since (15). Weekly minor releases with notes written by a release-notes workflow whose sections are Features, Bug Fixes, Improvements and Documentation, with no breaking-change section. 1.55.0 dropped background subagents (delegate(..., async: true) and GOOSE_MAX_BACKGROUND_TASKS) and 1.57.0 dropped the developer tools that delegated file reads and terminal commands to an ACP editor, each edited out of the code and docs with no earlier notice (9). 1.57, stable (15).

Security & auth goose +12

GitHub Copilot CLI 65

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Since 1.0.100 (19 October 2026) --disable-client-telemetry turns off the telemetry the CLI sends, which the command reference says doesn't affect server-side telemetry. Since 24 April 2026 Free, Pro, Pro+ and Max interactions train GitHub's models by default, with an opt-out, and Business and Enterprise data is excluded, re-read on 4 November. A fine-grained token with only the Copilot Requests permission works for CI (16). Asks before the first use of each modifying tool, deny rules that beat --allow-all-tools, URL and path permissions, trusted directories and enterprise managed settings. Local sandboxing is generally available since 1.0.93 (7 October 2026) and off by default, enterprises can require it fail-closed, and since 1.0.100 the sandbox allows local network access by default. Assisted Permissions, where a model approves requests it judges safe, left experimental mode in 1.0.104. The CLI still can't enforce two organisation MCP policies (17). The sandbox proxy filters hosts, sandboxed shells withhold GITHUB_TOKEN since 1.0.92, and content exclusion applies, but we found no prompt-injection guidance for the CLI (9). OpenTelemetry export with GenAI spans, opt-in, with enterprise capture controls since 12 October, and session logs (13). Two advisories with CVEs in 2026 and none since on OSV, re-read on 4 November, but no SECURITY.md in the repository and an expired security.txt on github.com per the 26 September check, which the proxy still refuses. We didn't check GitHub's bug bounty (10). SOC 2 isn't scored on the framework reading. 16+17+9+13+10 = 65.

goose 77

Harness reading of the framework checklist, used for all five harnesses in this batch. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Usage data is off until the user agrees on first use, and the docs list what's collected and what isn't (30). Four modes (autonomous, smart approval, manual approval, chat only), per-tool always, ask or never rules, and an extension allowlist fetched from GOOSE_ALLOWLIST, which from 1.57.0 must be HTTPS and blocks installs when the policy can't be read, but autonomous is the default (the first-run prompt for the mode still preselects Auto in 1.57.0) and there's no sandbox, with the docs pointing to a VM or container (11). Pattern and optional ML prompt-injection detection and an adversary reviewer for shell calls, both off until turned on, plus a prompt-injection caution in SECURITY.md (11). Session logs, a diagnostics report and a Langfuse tracing guide (12). SECURITY.md with GitHub private reporting and an AAIF governance contact, one advisory published with a CVE, and a Scorecard workflow. A second CVE, CVE-2026-109561 (low, Manual Approval bypassed by persisted read-only annotations after Smart Approval, fixed in 1.44.0), was published by NVD on 12 October from a third party, with no goose advisory of its own. No bug bounty, and goose-docs.ai/.well-known/security.txt returned 404 on 6 and 17 October and 1 November (13).

Agent ergonomics goose +10

GitHub Copilot CLI 72

Framework reading, adapted to a harness driven by a pipeline. --available-tools and --excluded-tools shape the tool list and --deny-tool removes tools, and MCP tool discovery recovers without a restart (20). --max-autopilot-continues caps autopilot, and a turn timeout applies to background work in -p (15). JSON output, and a 2026 release replaced a misleading auth error with the real cause (12). --resume and --continue, and permission prompts survive a resumed session (15). An SDK exists, per the changelog, but we didn't check its languages, and a headless run needs explicit allow flags to do anything (10).

goose 82

Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. The built-in extensions are few, and Code Mode lets the model find MCP tools through code instead of loading every definition (23). --max-turns (default 1000), GOOSE_MAX_TOKENS and automatic context compaction, though 1000 turns is a high default for an unattended run (16). goose run --output-format json or stream-json for scripts (15). Recipes can retry with success checks and an on_failure command, and sessions resume (17). A Rust core with Python and Java SDK builds, and one command runs a task, but a provider has to be configured first and the default mode approves everything (11).

Schema & documentation goose +9

GitHub Copilot CLI 72

Framework reading. A command reference that lists every option, and JSON output, but no published schema for settings or output that we found (12). docs.github.com/llms.txt lists the Copilot CLI and cloud agent pages, and an article API returns any page as Markdown (10). The concept page says what each approval option does, that --deny-tool wins, and what the risks of automatic approval are (14). Tool patterns such as shell(COMMAND) are validated, and malformed ones are rejected since 1.0.x (10). Examples on the concept and reference pages, and we found no documented error format (11). A dated changelog per release with breaking changes marked (15).

goose 81

Recipes have a documented schema with typed parameters and a response JSON Schema for structured output, and config and environment variables are documented in tables, but we found no OpenAPI spec for the goose server (18). llms.txt at goose-docs.ai, which now covers goose and the goose Development Kit (10). Permission modes come with a best-for column and the security pages say what each guard catches and misses (15). Recipe parameters take types and requirement levels, and retries take typed success checks (12). Many tutorials, a headless guide that tells scripts to check exit codes, and a known-issues page (13). Dated, written notes on every GitHub release, with no changelog file (13).

Maintenance & community goose +9

GitHub Copilot CLI 77

1.0.105 on 27 October 2026 per the changelog and its tag, 8 days before this check. Tags 1.0.106-1 to 1.0.106-8 (30 October) are pre-releases with no changelog entry and don't count (30). 25 dated releases from 1.0.79 (10 August) to 1.0.105 (27 October) in the 90 days from 6 August (20). Issues are labelled and triaged, with automation for stale and unanswered reports, though about 1,900 stay open, per the 1 October check (14). An SDK the changelog keeps updating (session APIs, MCP management, OAuth tokens), languages unchecked (10). Closed source and a bundled npm build, so no CI or dependency health to read (3). 30+20+14+10+3 = 77.

goose 86

v1.57.0 tagged on 27 October 2026, after v1.56.0 on 22 October (30). 13 releases in the 90 days from 3 August, 1.46.0 (11 August) to 1.57.0, about one a week, plus GDK alpha tags (20). Issues move through a public board with Inbox and Ready columns and some new reports get a label within a day, but many of the week's reports had no reply on 1 October, and pull requests that don't implement a Ready issue are closed, per the 1 October check, not re-read since (15). Desktop, CLI, npm and GHCR builds ship from the same tag, and Python and Java SDK builds run in CI (13). cargo-deny, cargo-machete, Dependabot and Scorecard workflows, every GitHub Action pinned to a commit SHA since 29 September, and jsonwebtoken removed on 26 October to stop ignoring its cargo-deny advisories, with the current CI state unconfirmed (8).

Score by category

CategoryWeightGitHub Copilot CLIgooseEdge
Reliability16%5577goose +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7281goose +9
Agent ergonomics13%7282goose +10
Security & auth14%6577goose +12
Payments & pricing10%6090goose +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7786goose +9
Transparency & trust7%7467GitHub Copilot CLI +7
Negative events≤15-8-5
TotalC 58.5/100BB 75/100

Facts side by side

FactGitHub Copilot CLIgoose
KindAgent harnessAgent harness
VendorGitHubAgentic AI Foundation (originally Block)
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyNone
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-272026-10-27
Terms last updated2026-04-27no document linked
Privacy policy last updated2026-04-27no document linked
Customer content may train modelsyes, with an opt-outnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity11k stars55k stars
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

GitHub Copilot CLI

Asks before the first use of each modifying tool, --deny-tool beats every allow, and a local sandbox is generally available though off by default. Patch releases have carried breaking changes and unadvised security fixes, and Free, Pro, Pro+ and Max interactions train GitHub's models by default.

goose

Telemetry off until the user opts in, with the collected fields listed. Autonomous mode, which approves every tool call, is the 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 by default
  3. Pin the CLI version in scripts. Patch releases have removed flags such as --no-remote
  4. Add --disable-client-telemetry if client telemetry shouldn't leave the machine
  5. Move off Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra before 16 November 2026

goose

  1. Set GOOSE_MODE=smart_approve or approve before a run. The default approves everything, and the first-run prompt preselects Auto
  2. Pass --max-turns with a real limit. The default is 1000
  3. Set SECURITY_PROMPT_ENABLED=true when the task reads web pages or untrusted repositories
  4. Use --output-format json and --no-session in CI, and check the exit code
  5. Pin the goose version in CI. Minor releases have removed functions, such as delegate(..., async: true) in 1.55.0, without notice

Questions

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

goose scores 75 (BB) on agent readiness against GitHub Copilot CLI's 58.5 (C), and leads in 6 of 7 scored categories. GitHub Copilot CLI leads on transparency & trust.

Are GitHub Copilot CLI and goose open source?

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

Other comparisons with GitHub Copilot CLI or goose

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.