Agentic Index
Anthropic Claude Code vs Google Jules (2026)
Anthropic Claude Code last verified ·Google Jules last verified
Claude Code is interactive and Jules is asynchronous. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Claude Code runs in your terminal under your direction, with plan review and a permission mode that decides which steps wait for your approval. Jules, Google's cloud agent, takes a GitHub issue into its own virtual machine, implements the change, runs your tests, and returns a pull request, with a free tier of 15 tasks a day.
On the Agentic Index coding agent ranking, neither Anthropic Claude Code nor Google Jules clears the bar, which asks for all five merge loop capabilities documented in full. Anthropic Claude Code does not document knowledge grounding and RAG in full; Google Jules does not document knowledge grounding and RAG in full, nor testing, debugging and optimization. 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 Google Jules 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 steer complex work interactively and want oversight controls at every step.
- Extensibility is the differentiator, with MCP, subagents, hooks, and an SDK for custom workflows.
- You need browser use and deep verification loops.
Choose Google Jules if
- You want to queue many well scoped tasks in parallel cloud machines and review the pull requests later.
- The free tier is genuinely useful at 15 tasks a day, and the $19.99 Google AI Pro plan raises that to 100.
- Your work starts as GitHub issues, and plan approval before execution gives enough steering.
| Feature | A Anthropic Claude Code |
G Google Jules |
|---|---|---|
| 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 |
||
|
Google JulesIntegrations & Tool Calling Deep GitHub integration covers issue labels, branches, pull requests and reading and responding to PR comments, MCP servers connect Linear, Stitch, Neon, Tinybird, Context7 and Supabase by API key in Settings, a Render integration detects failed builds and pushes fixes, and the REST API wires Jules into Slack, Linear, Jira and CI pipelines including GitHub Actions. GitHub is the only source control host. The agent runs shell commands, installs dependencies and executes builds inside its VM with repository level environment variables. Sourcejules.google/docs/changelog 2026-02-02 and 2025-10-03, docs/integrations/renderread 2026-10-28 |
||
|
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 |
||
|
Google JulesWorkflow Orchestration A task runs as a multi step plan the agent produces before writing code, with an Interactive Plan mode where it asks clarifying questions and refines the approach collaboratively, a Critic agent performing adversarial review of every proposed change during generation, a Planning Critic reviewing auto approved plans and reported to cut task failure rates by 9.5 percent, a CI Fixer loop that detects failures, fixes, commits and resubmits, and up to five parallel sessions on one prompt via the CLI --parallel flag, within the plan's concurrency limit of 3, 15 or 60 tasks. Sourcejules.google/docs/changelog 2026-01-26-1, 2026-02-19 and 2025-11-10, docs/cli/reference and docs/usage-limitsread 2026-10-28 |
||
|
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 |
||
|
Google JulesTriggers & Channel Coverage Tasks start from a jules label on a GitHub issue, the web app, the Jules Tools CLI, a REST API for CI/CD and chat integrations, scheduled recurring tasks (daily, weekly or monthly) with pause and resume, proactive suggested tasks where Jules scans a repository for TODO comments and surfaces work, pull request comments which the agent reads and acts on, and automatic triggers on CI failures in GitHub Actions and failed Render builds. No inbound webhook is documented. Sourcejules.google/docs/guides/scheduled-tasks, docs/guides/running-tasks and docs/changelog 2025-12-10, 2026-01-26 and 2026-02-19; jules.google/docs/changelog/2025-12-101read 2026-10-28 |
||
| 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 |
||
|
Google JulesKnowledge Grounding & RAG Each task clones the repository into its VM and reads it directly, with AGENTS.md conventions read from the repository root, a file selector to scope context, image upload and web search for current documentation. Suggested Tasks scan up to five repositories for TODO comments. Context is assembled per task, and the docs describe no persistent index, graph or embeddings layer over the customer's code. Sourcejules.google/docs, docs/guides/suggested-tasks and docs/environmentread 2026-10-28 |
||
|
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 |
||
|
Google JulesMemory & State Persistence Repository Memory saves the user's preferences, nudges and corrections during a task and references them on later tasks in that repository, toggled on or off per repository under Knowledge. The changelog is the only page that describes it. Memory has no stated lifetime and no documented way to review or delete entries, and environment snapshots and variables are setup state, not memory. Sourcejules.google/docs/changelog 2025-09-30read 2026-10-28 |
||
| 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 |
||
|
Google JulesHuman Oversight & Guardrails The agent writes a step by step plan the user approves, edits or rejects before any code is written, with an Interactive Plan mode asking clarifying questions first, and the user can chat with it at any point. If the user leaves, the plan auto approves on a timer, and the API's requirePlanApproval option is off by default, so a Planning Critic reviews plans that are auto approved. Work lands on a branch and the user chooses when to publish or open a pull request, a Critic agent adversarially reviews each proposed change during generation, tasks can be paused, resumed or deleted mid run, and commit authorship is configurable so changes are attributed to Jules, co-authored, or the user. Sourcejules.google/docs/guides/review-plan, docs/api/reference and docs/changelog 2026-01-26-1 and 2026-02-19; jules.google/docs/changelog/2025-08-082read 2026-10-28 |
||
|
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 |
||
|
Google JulesSecurity, Identity & Governance Jules isolates each task in a cloud VM, reaches repositories only as granted through the GitHub app, stores integration API keys encrypted, does not train on private repositories and tells users they are responsible for the code they run. There is no access surface (SSO, roles, organization administration) and no attestation or trust page, and paid plans are sold to individual Google accounts only. Sourcejules.google/docs/faq and docs/usage-limitsread 2026-10-28 |
||
|
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 |
||
|
Google JulesObservability & Auditability Each session carries a collection of activities representing the steps the agent took. Google calls them immutable, following an event source pattern and usable to reconstruct the session, and they are retrievable through the REST API with a createTime range cursor. The web app shows a real time activity feed, per task logs and task history per repository, the full changeset is downloadable in git patch format, and the critic agent's step by step evaluation is visible in the UI as it runs. No organization audit log is documented. Sourcejules.google/docs/changelog 2026-01-26-4 and 2025-09-03, docs/guides/coderead 2026-10-28 |
||
|
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 |
||
|
Google JulesDeployment & Data Residency Every task runs in a fresh, short lived Ubuntu VM in Google's cloud with internet access, whose toolchain the customer shapes with a setup script, snapshots and environment variables. That configures the environment, not where it runs. There is no region choice, customer VPC, on premises or tenant option, so a customer with a different residency requirement has no other answer. Sourcejules.google/docs/environment and docs/faqread 2026-10-28 |
||
| 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 |
||
|
Google JulesPrebuilt Agents, Templates & Packs Sample prompts ship as one click starting points, three scheduled task templates (Performance, Design and Security) start recurring tasks, suggested tasks let the agent propose work it has found in the repository, and MCP integrations are offered from a vendor curated list of vetted servers. There is no library of prebuilt agents, installable skills or marketplace, and the community prompt list lives in a GitHub repository. Sourcejules.google/docs/guides/scheduled-tasks, docs and docs/changelog 2025-09-02 and 2026-02-02; jules.google/docs/changelog/2025-09-02read 2026-10-28 |
||
| 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 |
||
|
Google JulesModel Flexibility & Routing Every model Jules runs is Google's Gemini. The changelog makes Gemini 3 Flash the base model on all tiers and Gemini 3.1 Pro the default for Pro subscribers, which is a tier choice within one maker, while the homepage and usage page still name Gemini 2.5 Pro and Gemini 3 Pro. There is no user model choice, no other maker and no bring your own model path. Sourcejules.google/docs/changelog 2026-03-09 and 2026-01-30, docs/usage-limitsread 2026-10-28 |
||
|
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 |
||
|
Google JulesAPIs, SDKs & MCP Extensibility A REST API at jules.googleapis.com/v1alpha, in alpha, authenticates with an X-Goog-Api-Key header (up to three keys) and exposes Sources, Sessions (create, list, approve plan, send message, auto create PR, repoless sessions) and Activities with git patch output. A Jules Tools CLI installs via npm as @google/jules with jules remote new, list and pull, parallel execution and local patch application, a Gemini CLI extension exposes Jules as a slash command, and MCP server support connects a vetted set of servers by API key. Sourcejules.google/docs/api/reference, docs/api/reference/authentication, docs/cli/reference and docs/changelog 2026-02-02; jules.google/docs/changelog/2026-02-02read 2026-10-28 |
||
|
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 |
||
|
Google JulesTesting, Debugging & Optimization The agent runs the project's existing test suite and iterates when tests fail, writes tests on its own, and the CI Fixer detects a failed GitHub Actions check, works through a fix and resubmits the pull request in a loop. A Critic agent adversarially reviews proposed changes and a Planning Critic reviews plans, both internal quality mechanisms, and Run to Validate checks environment setup scripts. These verify the customer's code and the agent's own output. There is no harness for customers to evaluate or regression test agent behavior. Sourcejules.google/docs/changelog 2026-02-19 and 2026-01-26-1, docs/environmentread 2026-10-28 |
||
| 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 |
||
|
Google JulesBrowser & Computer Use The default Jules base image includes Playwright and ChromeDriver for front end testing, and the agent renders a running web application and returns a screenshot of the front end alongside its code changes when asked to verify its work, with images shown in the diff viewer. With Gemini 3 Pro, visual verification of web app outcomes is more precise, and Jules can also search the web for documentation and code examples during a task. Sourcejules.google/docs/changelog 2025-08-07 and 2025-11-19, docs/environmentread 2026-10-28 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | A Anthropic Claude Code |
G Google Jules |
|---|---|---|
|
Entry price Lowest public entry point |
From $17 per month for Claude Pro billed annually, or $20 monthly. | Free · Jules in Pro via Google AI Pro $19.99/mo |
|
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. | hybrid |
|
Variable cost Workload / overage exposure |
High variable cost | Low 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
Google Jules
-
· Agent capability
Sessions in Jules can continue until November 11, 2026, after which Jules turns read only, and the product winds down for good on December 31, 2026 as Google unifies its agentic coding work.
Source
More comparisons with Anthropic Claude Code or Google Jules
Other matchups in coding agents
Not the pairing you were after? These compare a different set of coding agents on the same 14 capabilities.