Agentic Index
Anthropic Claude Code vs Goose (2026)
Anthropic Claude Code last verified ·Goose last verified
Claude Code is the deepest single vendor coding agent and Goose is the open, any model alternative. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Claude Code brings subagents, plan mode, browser use, and strong verification, tied to Claude models. Goose runs locally under a permissive license with any provider, including local models, trading some polish for control and zero tool cost.
On the Agentic Index coding agent ranking, neither Anthropic Claude Code nor Goose clears the bar, which asks for all five merge loop capabilities documented in full. Neither documents knowledge grounding and RAG in full. 3 of the 96 vendors in the lane clear it. See the coding agent ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Anthropic Claude Code and Goose are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,140 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Anthropic Claude Code if
- You want frontier agent capability with safety tooling such as permissions, checkpoints, sandboxing, and plan review.
- Plugin evals, a Chrome integration that drives a real browser session, and OpenTelemetry traces come built in.
- Bundling with your Claude plan beats managing separate infrastructure.
Choose Goose if
- Your code cannot leave your machine, and local models through Ollama are a requirement.
- You want model portability across Anthropic, OpenAI, Google, and open weights.
- Open source under the Linux Foundation fits your procurement and longevity criteria.
| Feature | A Anthropic Claude Code |
G Goose |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
Anthropic Claude CodeIntegrations & Tool Calling MCP servers connect the agent to tools, databases, APIs, issue trackers and monitoring systems at local, project and user scopes, with OAuth 2.0 sign in for remote servers, claude.ai connectors, and managed settings that allow or deny servers across an organization, alongside built in file, search, shell and web tools. Sourcecode.claude.com/docs/en/mcp and docs/en/chromeread 2026-10-24 |
||
|
GooseIntegrations & Tool Calling The agent reads and writes files, executes shell commands, builds and runs software, runs tests and calls external APIs in the developer's own environment, with more than 70 MCP extensions connecting SaaS applications, data sources and development environments; tools are individually configurable and can be turned off, including native ones, and MCP Apps provide a UI proxy surface. Sourcegoose-docs.ai extensions docs and github.com/aaif-goose/gooseread 2026-08-30 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
Anthropic Claude CodeWorkflow Orchestration Subagents are workers Claude spawns for delegated tasks, and agent teams let a lead agent supervise long running peer sessions that share a task list. Dynamic workflows go further. Claude writes a JavaScript script that runs dozens to hundreds of subagents in the background, up to 1,000 per run and 16 at a time by default, asks before a run starts (every run in Manual mode, the first launch in Auto mode), and the script can be saved and rerun as a command. Sourcecode.claude.com/docs/en/workflowsread 2026-10-24 |
||
|
GooseWorkflow Orchestration Recipes package instructions, prompt, extensions, parameters and sub_recipes into a reusable shareable unit defined by a YAML or JSON schema, with template variables filled at runtime. Larger workflows are composed from sub-recipes, subagents run sub-recipes in isolated execution contexts and can run concurrently, and a scheduler runs recipes on cron or set frequencies unattended. Sourcegoose-docs.ai/docs/guides/recipes and goose-docs.ai scheduling docsread 2026-08-30 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
Anthropic Claude CodeTriggers & Channel Coverage Cloud scheduled tasks, in research preview, run a saved prompt against chosen repositories on a schedule, on an HTTP POST to the task's own endpoint, or on GitHub pull request and release events, so they keep working with the laptop closed. GitHub Actions and GitLab CI/CD automate code review and issue triage in CI, GitHub Code Review reviews every pull request automatically, and the agent answers @Claude in Slack and runs from the terminal, desktop, IDEs, the web and headless scripts. Sourcecode.claude.com/docs/en/routines and docs/en/overviewread 2026-10-24 |
||
|
GooseTriggers & Channel Coverage Invocation spans a native desktop application on macOS, Linux and Windows, a full command line interface for terminal and scripting workflows, and a REST API with an OpenAPI specification and generated TypeScript SDK for embedding; a scheduler runs recipes at a set frequency or on a custom cron schedule unattended, and a gateway provides remote access. Sourcegoose-docs.ai scheduling and CLI docs, and the goose-server API referenceread 2026-08-30 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
Anthropic Claude CodeKnowledge Grounding & RAG The agent grounds itself in the customer's repository by reading and searching it directly on each run, with project instructions from CLAUDE.md or AGENTS.md and path scoped rules, and MCP connections reach the customer's databases, issue trackers and internal APIs. Context is gathered fresh on each run, and Anthropic does not describe an index, graph or embeddings layer that persists between runs. Sourcecode.claude.com/docs/en/memory and docs/en/mcpread 2026-10-24 |
||
|
GooseKnowledge Grounding & RAG The agent works in the developer's actual environment, reading files and running commands directly, and reaches external content repositories, business applications and data sources through MCP extensions, with the ability to discover new systems on the fly. Project guidance follows the AGENTS.md standard, an AAIF sibling project. Goose does not describe codebase indexing, embeddings or a retrieval architecture. Sourcegoose-docs.ai and aaif.io/projects/gooseread 2026-08-30 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
Anthropic Claude CodeMemory & State Persistence Auto memory, on by default in local sessions, holds notes Claude writes itself as it works, such as corrections the user gives and approaches the user confirms. It is scoped per repository and shared across worktrees, loaded into every session through a MEMORY.md index, kept outside the transcript retention sweep until the user or Claude edits or deletes it, and browsable and editable through /memory. CLAUDE.md files are standing instructions the user writes, separate from this memory. Sourcecode.claude.com/docs/en/memoryread 2026-10-24 |
||
|
GooseMemory & State Persistence The built in Memory extension stores what the user teaches goose (commands, snippets, preferences) as files per project or globally, loads them into every session and exposes remember, retrieve and remove tools, and sessions are resumable. The store is written at the user's instruction. Sourcegoose-docs.ai/docs/mcp/memory-mcp and docs/guides/logsread 2026-09-29 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
Anthropic Claude CodeHuman Oversight & Guardrails Auto mode is the starting mode for interactive terminal and VS Code sessions from v2.1.283. A separate classifier model reviews each action before it runs and blocks what it judges unsafe, the user's ask and deny rules still apply, and an organization can turn auto mode off in managed settings. Manual mode starts read only and asks before edits, shell commands and network requests, with approve once or allow from then on and fail closed matching for unmatched commands. Plan mode researches and proposes changes without editing, and claude -p and Agent SDK runs start in Manual. Sourcecode.claude.com/docs/en/permission-modes and docs/en/securityread 2026-10-24 |
||
|
GooseHuman Oversight & Guardrails Permission modes set how much goose may do alone. Manual Approval asks for confirmation before using any tool or extension, Smart Approval approves low risk actions and flags the rest for approval, Chat Only allows no tool use, and granular per tool permissions refine both. Completely Autonomous is the default, though, so approval applies only once a stricter mode is chosen. Sourcegoose-docs.ai/docs/guides/managing-tools/goose-permissionsread 2026-09-29 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
Anthropic Claude CodeSecurity, Identity & Governance A SOC 2 Type 2 report and an ISO 27001 certificate sit in the Anthropic Trust Center. Claude Code adds permission modes, sandboxed shell commands with filesystem and network isolation, command injection detection, trust verification for new folders and MCP servers, keychain credential storage, managed settings for organization enforcement and a HackerOne disclosure program. Under commercial terms Anthropic does not train models on Claude Code code or prompts unless the customer opts in. Sourcecode.claude.com/docs/en/security and docs/en/data-usageread 2026-10-24 |
||
|
GooseSecurity, Identity & Governance Goose secures work through its architecture and configuration. The agent runs locally under the user's own credentials with bring your own keys, tools can be disabled one by one and scoped per recipe and subagent, and code need never leave the machine. There is no hosted service, no accounts and no organization layer, so there is no SSO, RBAC, audit logging or attestation, and none is claimed. The project is vendor neutral under the Agentic AI Foundation, which publishes a project health score for it. Sourcegoose-docs.ai and aaif.io/projects/gooseread 2026-08-30 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
Anthropic Claude CodeObservability & Auditability OpenTelemetry exports metrics, events and optional traces, with a tool decision event for every permission accept or reject and a tool result event for every completed tool call, and OTEL_LOG_TOOL_DETAILS adds commands, MCP server and tool names and inputs. Telemetry endpoints set in managed settings override developer settings, and all operations in cloud sessions are logged for audit. Sourcecode.claude.com/docs/en/monitoring-usage and docs/en/securityread 2026-10-24 |
||
|
GooseObservability & Auditability Every session is kept as a record in a local SQLite database holding session metadata and the full conversation of messages and tool interactions, beside command history and system log files, all stored on the user's machine and never sent to external servers. Past sessions are browsable and resumable in the CLI and desktop app, so the user holds the execution history, though there is no organization level export. Sourcegoose-docs.ai/docs/guides/logsread 2026-09-29 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
Anthropic Claude CodeDeployment & Data Residency Claude Code runs on the developer's own machine by default, and Remote Control keeps code execution and file access local. Cloud sessions run in isolated Anthropic managed VMs with network access limited by default, or an organization routes them, scheduled tasks included, to self hosted environments on its own infrastructure. Prompts and outputs travel over TLS 1.2 or later, and at rest the Anthropic API uses AES-256 disk encryption, while Amazon Bedrock, Google Cloud's Agent Platform and Microsoft Foundry apply their own keys, with customer managed keys available on the first two. Commercial data is kept 30 days by default, and Zero Data Retention is turned on per organization for qualified Claude for Enterprise accounts. Sourcecode.claude.com/docs/en/data-usage and docs/en/securityread 2026-10-24 |
||
|
GooseDeployment & Data Residency Goose runs entirely on the developer's own machine as an Apache 2.0 licensed Rust binary, as a desktop app for macOS, Linux and Windows or a CLI, so code and data stay local. With an Ollama or LM Studio provider and a locally hosted model it operates fully offline with no API keys and no external network calls, which suits air gapped environments, and an Inference Mesh supports local models. Sourcegoose-docs.ai and github.com/aaif-goose/gooseread 2026-08-30 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
Anthropic Claude CodePrebuilt Agents, Templates & Packs Plugins package skills, agents, hooks and MCP servers as one installable unit, and Anthropic's official marketplace is added the first time an interactive terminal session starts, browsable from the /plugin Discover tab or Claude Marketplace on the web, with a context cost estimate for each official plugin and named plugins such as commit-commands. Saved workflows and the bundled /deep-research workflow run as commands, and workflows can ship inside plugins. Sourcecode.claude.com/docs/en/plugins and docs/en/workflowsread 2026-10-24 |
||
|
GoosePrebuilt Agents, Templates & Packs A Recipe Cookbook publishes ready to use recipes for common development scenarios, shareable by URL and launchable with a single click, alongside an extension catalog of more than 70 MCP extensions installable into the agent and a skills system for role based specialization. Custom slash commands can be bound to recipes in any chat session. Sourcegoose-docs.ai/docs/guides/recipes and goose-docs.ai extensions catalogread 2026-08-30 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
Anthropic Claude CodeModel Flexibility & Routing Every model Claude Code runs is Anthropic's. The customer picks among Claude models per session or subagent and picks where they are served (the Claude API, Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry), but not the model maker, and Anthropic does not support routing Claude Code to non-Claude models through any gateway. Sourcecode.claude.com/docs/en/llm-gatewayread 2026-10-24 |
||
|
GooseModel Flexibility & Routing More than 30 LLM providers are supported, including Anthropic, OpenAI, Google, Groq, Mistral, Cohere, Amazon Bedrock and local inference through Ollama and LM Studio, configurable per session and per recipe. A Provider trait allows custom provider integrations and an Inference Mesh serves local models. The project is bring your own key throughout, and multi model use lets different models review each other's work. Sourcegoose-docs.ai provider docs and goose-docs.ai/docs/guidesread 2026-08-30 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
Anthropic Claude CodeAPIs, SDKs & MCP Extensibility The Claude Agent SDK gives the same tools, agent loop and context management that power Claude Code as a Python and TypeScript library, with hooks, subagents, MCP, permissions, sessions, skills and plugins, and the CLI can be driven from any language with -p and JSON output. Sourcecode.claude.com/docs/en/agent-sdk/overviewread 2026-10-24 |
||
|
GooseAPIs, SDKs & MCP Extensibility Goose was one of the first public MCP clients, and its Extensions are MCP servers, with a catalog of more than 70 and the ability to discover new systems on the fly. A goose-server REST API with an OpenAPI specification and generated TypeScript SDK supports embedding, custom MCP servers and tools can be built, a Provider trait allows custom LLM integrations, and white labeled distributions with preconfigured providers and branding are a supported build target. The whole project is Apache 2.0 in Rust at github.com/aaif-goose/goose. Sourcegoose-docs.ai extensions and API docsread 2026-08-30 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
Anthropic Claude CodeTesting, Debugging & Optimization claude plugin eval runs a suite of realistic prompts against a plugin and scores the results, grading each case with a regex over the reply, a check that a particular tool was called, or a rubric a second model judges. It compares the run against a no plugin baseline and gates CI on the score, so a team can catch regressions when its plugin changes or a new model ships. Sourcecode.claude.com/docs/en/plugin-evalsread 2026-10-24 |
||
|
GooseTesting, Debugging & Optimization The repository carries an evals/harbor directory for running goose against benchmark tasks, so a customer can evaluate the agent's behavior with the project's own harness, and recipes support structured response schemas and retries for deterministic checks. Sourcegithub.com/aaif-goose/gooseread 2026-09-29 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
Anthropic Claude CodeBrowser & Computer Use The Chrome integration lets the agent work in a visible browser window with the user's logins, navigating, clicking, typing, filling forms, uploading files, reading console errors and DOM state and saving screenshots, in Chrome, Edge and other Chromium browsers. Site permissions come from the extension, and the agent pauses for logins and CAPTCHAs. Computer use extends this to native macOS apps. Sourcecode.claude.com/docs/en/chromeread 2026-10-24 |
||
|
GooseBrowser & Computer Use The built in Computer Controller extension automates everyday computer tasks, controlling applications and system settings through macOS UI automation via the third party Peekaboo CLI and scraping the web. Interface control comes from that outside engine, and browser control otherwise comes from catalog extensions such as Playwright, Selenium and Browserbase that the user installs. Sourcegoose-docs.ai/docs/mcp/computer-controller-mcpread 2026-09-29 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | A Anthropic Claude Code |
G Goose |
|---|---|---|
|
Entry price Lowest public entry point |
From $17 per month for Claude Pro billed annually, or $20 monthly. | Free and open source. |
|
Pricing confidence How public the numbers are |
Public, exact | Public, exact |
|
Billing Primary billing axis |
Subscription per user (Pro, Max) or per seat (Team, Enterprise), each with plan usage limits, or per token on the Claude API. | No subscription. The only cost is model usage, billed by the provider behind the user's own API key, or nothing for a local model. |
|
Variable cost Workload / overage exposure |
High variable cost | Medium variable cost |
|
Free tier / trial Try before you buy |
No free tier
|
Free tier
|
|
Buying motion Self-serve vs sales call |
Self-serve | Self-serve |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
Anthropic Claude Code
-
· Human approval / guardrails
A new permission setting in Claude Code 2.1.319 denies any tool call that would otherwise wait on a permission prompt and lets the turn carry on, in terminal sessions, subagents and teammates.
Source -
· Security / enterprise
MCP server blocklists in Claude Code 2.1.318 now reach further.
Source -
· Observability / auditability
Claude Code 2.1.317 adds a cost report to the Claude apps gateway admin API, returning past spend over a date range in total, per developer, per day or per IdP group.
Source
Goose
-
· Workflow orchestration
Subagents that failed or were canceled can now be resumed in Goose v1.56.0 instead of started over.
Source -
· Human approval / guardrails
Release 1.55.0 of goose binds subagents to their parent's hooks, goose mode and tool approvals, so work the agent delegates runs under the same checks as the parent session.
Source -
· Security / enterprise
Goose version 1.45.0 introduces several new capabilities, including support for the latest Gemini models and a configurable GOOSE_DOCS_ROOT environment variable for air-gapped documentation access.
Source
More comparisons with Anthropic Claude Code or Goose
Other matchups in coding agents
Not the pairing you were after? These compare a different set of coding agents on the same 14 capabilities.