44 of 51 criteria have a sourced finding; 44 were also cross-checked by a second agent. Every comparison that includes Jules links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
Client access: Jules has a browser client; mobile action parity was not established. Jules Tools is an npm-installed remote-session CLI with a TUI dashboard. Web: start, approve or revise the plan, chat feedback, pause and resume, publish branch or PR. CLI: start, list and pull sessions. Browser notifications can signal completion or need for input. The same Google account sees its sessions in the web app and in Jules Tools (remote list); a device handoff was not tested. Not established: desktop os, mobile apps, mobile browser, editor extensions.
Scope
Surfaces: Jules Tools remote-session CLI, Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: desktop_os, mobile_apps, mobile_browser, editor_extensions. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
9 atomic answers
Desktop os [unknown] Not established for desktop os in the named first-party source pass. Product access and scenario tests were not run.
Mobile apps [unknown] Not established for mobile apps in the named first-party source pass. Product access and scenario tests were not run.
Browser [supported] Jules has a browser client; mobile action parity was not established. Sources: jules:nov07-setup.
Mobile browser [unknown] Not established for mobile browser in the named first-party source pass. Product access and scenario tests were not run.
Cli [supported] Jules Tools is an npm-installed remote-session CLI with a TUI dashboard. Sources: jules:nov07-cli.
Editor extensions [unknown] Not established for editor extensions in the named first-party source pass. Product access and scenario tests were not run.
Notifications [supported] Browser notifications can signal completion or need for input. Sources: jules:nov07-setup.
Cross device continuity [partial] The same Google account sees its sessions in the web app and in Jules Tools (remote list); a device handoff was not tested. Sources: jules:b10j-cli, jules:b10j-repo.
Agent and model choice: Only the Jules agent runs tasks; the complete plan comparison lists Gemini models only and no other coding harness. Jules documents Gemini model access across its plans; separate external coding harness support is not established. No other harness can run, so mixed operation does not apply. Not established: custom adapters, session integration.
Scope
Surfaces: Jules web/cloud, Jules Tools remote-session CLI · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: custom_adapters, session_integration. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
5 atomic answers
Harnesses [unsupported] Only the Jules agent runs tasks; the complete plan comparison lists Gemini models only and no other coding harness. Sources: jules:b10j-limits, jules:b10j-start.
Model providers [supported] Jules documents Gemini model access across its plans; separate external coding harness support is not established. Sources: jules:gap07-limits.
Custom adapters [unknown] Not established for custom adapters in the named first-party source pass. Product access and scenario tests were not run.
Session integration [unknown] Not established for session integration in the named first-party source pass. Product access and scenario tests were not run.
Mixed harness operation [unsupported] No other harness can run, so mixed operation does not apply. Sources: jules:b10j-limits.
Subscriptions, API keys and vendor credits: Jules Pro/Ultra benefits are included in corresponding Google AI plans for individual Gmail accounts. This is not Claude or ChatGPT coding-harness subscription reuse. Jules API keys (at most 3) access Jules itself; no bring-your-own model key is documented. Google account eligibility controls Jules access and paid upgrades. Paid plan upgrades require an individual Gmail account; Workspace/business upgrades are not established. Not established: vendor credits, local models, account switching.
Scope
Surfaces: Jules web/cloud, Jules Tools remote-session CLI · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: vendor_credits, local_models, account_switching. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
7 atomic answers
Agent subscriptions [supported] Jules Pro/Ultra benefits are included in corresponding Google AI plans for individual Gmail accounts. This is not Claude or ChatGPT coding-harness subscription reuse. Sources: jules:gap07-limits.
Api accounts [partial] Jules API keys (at most 3) access Jules itself; no bring-your-own model key is documented. Sources: jules:b10j-api.
Vendor credits [unknown] Not established for vendor credits in the named first-party source pass. Product access and scenario tests were not run.
Local models [unknown] Not established for local models in the named first-party source pass. Product access and scenario tests were not run.
Account switching [unknown] Not established for account switching in the named first-party source pass. Product access and scenario tests were not run.
Vendor account requirement [supported] Google account eligibility controls Jules access and paid upgrades. Sources: jules:gap07-limits.
Provider restrictions [supported] Paid plan upgrades require an individual Gmail account; Workspace/business upgrades are not established. Sources: jules:gap07-limits.
Repoless REST API sessions create an ephemeral cloud environment from a prompt without a source repository. Onboarding connects a Google account and grants the Jules GitHub App selected repository access. A task selects a repository/branch and optional setup script before cloud provisioning. Sign in with Google, connect GitHub, choose repo and branch, write a prompt and approve the plan. Jules works only on GitHub repositories the user grants; other version control is future work. Jules infers setup from the repository, AGENTS.md or README, and setup scripts can be validated with Run and Snapshot. Tasks run only in Google-hosted cloud VMs; no user-host onboarding exists.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
7 atomic answers
First task setup [supported] Sign in with Google, connect GitHub, choose repo and branch, write a prompt and approve the plan. Sources: jules:b10j-start.
No git [supported] Repoless REST API sessions create an ephemeral cloud environment from a prompt without a source repository. Sources: jules:gap07-outputs.
Local git without remote [unsupported] Jules works only on GitHub repositories the user grants; other version control is future work. Sources: jules:b10j-tasks.
Hosted git [supported] Onboarding connects a Google account and grants the Jules GitHub App selected repository access. Sources: jules:nov07-setup.
Prerequisite guidance [supported] Jules infers setup from the repository, AGENTS.md or README, and setup scripts can be validated with Run and Snapshot. Sources: jules:b10j-env.
Managed cloud setup [supported] A task selects a repository/branch and optional setup script before cloud provisioning. Sources: jules:nov07-setup.
Byo vps onboarding [unsupported] Tasks run only in Google-hosted cloud VMs; no user-host onboarding exists. Sources: jules:b10j-faq, jules:b10j-env.
remote list, remote new and remote pull manage cloud sessions; --parallel creates several runs. REST resources include sources, sessions and activities for programmatic coding workflows. The TUI exposes session monitoring and side-by-side diffs; CLI operations require Google sign-in. Jules REST API authenticates with X-Goog-Api-Key; at most three keys exist at a time. The REST API is explicitly alpha and experimental, with changing schemas and keys possible. The @google/jules-sdk TypeScript SDK starts and monitors sessions. @google/jules-mcp exposes session create, list, state, reply/approve, review-context, diff and cache tools to other agents.
Scope
Surfaces: Jules Tools remote-session CLI, Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: webhooks. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
8 atomic answers
Cli [supported] remote list, remote new and remote pull manage cloud sessions; --parallel creates several runs. Sources: jules:nov07-cli.
Api [supported] REST resources include sources, sessions and activities for programmatic coding workflows. Sources: jules:nov07-api.
Sdk [supported] The @google/jules-sdk TypeScript SDK starts and monitors sessions. Sources: jules:b10j-npm-sdk.
Mcp server [supported] @google/jules-mcp exposes session create, list, state, reply/approve, review-context, diff and cache tools to other agents. Sources: jules:b10j-npm-mcp.
Webhooks [unknown] Not established for webhooks in the named first-party source pass. Product access and scenario tests were not run.
Operations [supported] The TUI exposes session monitoring and side-by-side diffs; CLI operations require Google sign-in. Sources: jules:nov07-cli.
Authentication [supported] Jules REST API authenticates with X-Goog-Api-Key; at most three keys exist at a time. Sources: jules:gap07-api.
Stability [supported] The REST API is explicitly alpha and experimental, with changing schemas and keys possible. Sources: jules:gap07-api.
External tools and extensions: MCP client support covers only Linear, Stitch, Neon, Tinybird, Context7 and Supabase. Jules deliberately limits MCP to hand-selected servers; users cannot add their own servers or tools. Jules reads AGENTS.md at the repository root. Each MCP service connection uses that service's API key, entered in Settings and stored encrypted. Integrations request read-only access by default and servers are vetted for minimal permissions; per-tool user controls are not documented. Each user adds service connections in their own Jules Settings page; Jules provides the vetted servers. Not established: plugins.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: plugins. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
7 atomic answers
Mcp client [partial] MCP client support covers only Linear, Stitch, Neon, Tinybird, Context7 and Supabase. Sources: jules:b10j-cl-2026-02-02.
Plugins [unknown] Not established for plugins in the named first-party source pass. Product access and scenario tests were not run.
Custom tools [unsupported] Jules deliberately limits MCP to hand-selected servers; users cannot add their own servers or tools. Sources: jules:b10j-cl-2026-02-02.
Instructions import [supported] Jules reads AGENTS.md at the repository root. Sources: jules:b10j-start.
Permission scope [partial] Integrations request read-only access by default and servers are vetted for minimal permissions; per-tool user controls are not documented. Sources: jules:b10j-integrations, jules:b10j-cl-2026-02-02.
Integration owner [supported] Each user adds service connections in their own Jules Settings page; Jules provides the vetted servers. Sources: jules:b10j-cl-2026-02-02.
Client implementation: No desktop app is documented; Jules Tools is a terminal CLI/TUI. The @google/jules 0.1.42 npm package is a Node.js installer that downloads and runs a prebuilt Go platform binary. Not established: mobile implementation, hybrids.
Scope
Surfaces: Jules Tools remote-session CLI · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: mobile_implementation, hybrids. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
4 atomic answers
Desktop implementation [partial] No desktop app is documented; Jules Tools is a terminal CLI/TUI. Sources: jules:b10j-cli, jules:b10j-npm-cli.
Mobile implementation [unknown] Not established for mobile implementation in the named first-party source pass. Product access and scenario tests were not run.
Hybrids [unknown] Not established for hybrids in the named first-party source pass. Product access and scenario tests were not run.
Implementation evidence [supported] The @google/jules 0.1.42 npm package is a Node.js installer that downloads and runs a prebuilt Go platform binary. Sources: jules:b10j-npm-cli.
Applying the jules label to a GitHub issue starts work and returns a PR link; GitHub remains the issue system. Tasks are created from the web prompt box. Natural-language prompts with optional PNG/JPEG images. The jules label on a GitHub issue starts a task; no other import is documented. Sessions have stable IDs in the API and CLI. Jules comments on the labelled issue and links the pull request; issue edits stay in GitHub.
Scope
Surfaces: Jules web/cloud, Jules Tools remote-session CLI · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: authoritative_tracker, sync, supported_edits. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
9 atomic answers
Local creation [supported] Tasks are created from the web prompt box. Sources: jules:b10j-running.
External import [partial] The jules label on a GitHub issue starts a task; no other import is documented. Sources: jules:b10j-running.
Chat git triggers [supported] Applying the jules label to a GitHub issue starts work and returns a PR link; GitHub remains the issue system. Sources: jules:nov07-tasks.
Authoritative tracker [unknown] Not established for authoritative tracker in the named first-party source pass. Product access and scenario tests were not run.
Sync [unknown] Not established for sync in the named first-party source pass. Product access and scenario tests were not run.
Supported edits [unknown] Not established for supported edits in the named first-party source pass. Product access and scenario tests were not run.
External roundtrips [partial] Jules comments on the labelled issue and links the pull request; issue edits stay in GitHub. Sources: jules:b10j-running.
A task presents step-by-step implementation plans with assumptions and setup details. Users request plan revisions through task chat. Plan steps and resulting implementation share the same task session. Jules revises plan steps in response to feedback. Jules replans on feedback; no plan revision history is documented. Session activities are immutable and retrievable through the API.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: acceptance_criteria. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
7 atomic answers
Plans [supported] A task presents step-by-step implementation plans with assumptions and setup details. Sources: jules:nov07-plan.
Acceptance criteria [unknown] Not established for acceptance criteria in the named first-party source pass. Product access and scenario tests were not run.
Editors [supported] Users request plan revisions through task chat. Sources: jules:gap07-plans.
Revisions [partial] Jules replans on feedback; no plan revision history is documented. Sources: jules:b10j-plan, jules:b10j-running.
Implementation links [supported] Plan steps and resulting implementation share the same task session. Sources: jules:gap07-plans.
Amendment [supported] Jules revises plan steps in response to feedback. Sources: jules:gap07-plans.
Restart persistence [partial] Session activities are immutable and retrievable through the API. Sources: jules:b10j-cl-2026-01-26-4.
Jules loads AGENTS.md at the repository root. During a task Jules saves preferences, nudges and corrections and references them in later tasks in the same repository; memory can be toggled per repository. README and AGENTS.md give environment setup hints. Memory is kept per repository. Memory can be turned off per repository; deleting individual memories is not documented.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: skills, provenance, correction, freshness, takeover_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
10 atomic answers
Instructions [supported] Jules loads AGENTS.md at the repository root. Sources: jules:nov07-setup.
Skills [unknown] Not established for skills in the named first-party source pass. Product access and scenario tests were not run.
Project docs [partial] README and AGENTS.md give environment setup hints. Sources: jules:b10j-env.
Memory [partial] During a task Jules saves preferences, nudges and corrections and references them in later tasks in the same repository; memory can be toggled per repository. Scope, provenance and deletion controls are not described. Sources: jules:gap07-memory.
Provenance [unknown] Not established for provenance in the named first-party source pass. Product access and scenario tests were not run.
Correction [unknown] Not established for correction in the named first-party source pass. Product access and scenario tests were not run.
Deletion [partial] Memory can be turned off per repository; deleting individual memories is not documented. Sources: jules:b10j-cl-2025-09-30.
Freshness [unknown] Not established for freshness in the named first-party source pass. Product access and scenario tests were not run.
Takeover continuity [unknown] Not established for takeover continuity in the named first-party source pass. Product access and scenario tests were not run.
Task creation accepts PNG/JPEG images totaling under 5 MB; this guide excludes follow-up image attachments. The agent works on the cloned repository in its VM; no indexing feature is documented. Context7 is among the allow-listed MCP servers. Only GitHub repositories the user grants are accessible.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: indexing, freshness, api_retrieval, citations, conflict_detection, review_enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
10 atomic answers
Code search [partial] The agent works on the cloned repository in its VM; no indexing feature is documented. Sources: jules:b10j-env.
Indexing [unknown] Not established for indexing in the named first-party source pass. Product access and scenario tests were not run.
External knowledge [partial] Context7 is among the allow-listed MCP servers. Sources: jules:b10j-cl-2026-02-02.
Multimodal inputs [supported] Task creation accepts PNG/JPEG images totaling under 5 MB; this guide excludes follow-up image attachments. Sources: jules:nov07-tasks.
Freshness [unknown] Not established for freshness in the named first-party source pass. Product access and scenario tests were not run.
Access scope [supported] Only GitHub repositories the user grants are accessible. Sources: jules:b10j-tasks.
Api retrieval [unknown] Not established for api retrieval in the named first-party source pass. Product access and scenario tests were not run.
Citations [unknown] Not established for citations in the named first-party source pass. Product access and scenario tests were not run.
Conflict detection [unknown] Not established for conflict detection in the named first-party source pass. Product access and scenario tests were not run.
Review enforcement [unknown] Not established for review enforcement in the named first-party source pass. Product access and scenario tests were not run.
Native issue management and idea backlog: Users create tasks, not issues. Tasks can be deleted permanently; there is no archive. Suggested TODO cards can be started or dismissed. Suggested tasks start with Start, and plans need approval unless the timer auto-approves. No external tracker is required; a prompt alone starts a task. Not established: edit, discuss, prioritize, label, assign, search, filter, reopen, project epic views, task session separation, metadata, durable states.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Google-hosted Jules and companion Jules Tools; targeted first-party pass 2026-11-13; published plans retain their pre-read-only scope and the November 11 turndown overrides new task access; no installed-product test; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: edit, discuss, prioritize, label, assign, search, filter, reopen, project_epic_views, task_session_separation, metadata, durable_states. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
17 atomic answers
Create [partial] Users create tasks, not issues. Sources: jules:b10j-running.
Edit [unknown] Not established for edit in the named first-party source pass. Product access and scenario tests were not run.
Discuss [unknown] Not established for discuss in the named first-party source pass. Product access and scenario tests were not run.
Prioritize [unknown] Not established for prioritize in the named first-party source pass. Product access and scenario tests were not run.
Label [unknown] Not established for label in the named first-party source pass. Product access and scenario tests were not run.
Assign [unknown] Not established for assign in the named first-party source pass. Product access and scenario tests were not run.
Search [unknown] Not established for search in the named first-party source pass. Product access and scenario tests were not run.
Filter [unknown] Not established for filter in the named first-party source pass. Product access and scenario tests were not run.
Archive [partial] Tasks can be deleted permanently; there is no archive. Sources: jules:b10j-tasks.
Reopen [unknown] Not established for reopen in the named first-party source pass. Product access and scenario tests were not run.
Project epic views [unknown] Not established for project epic views in the named first-party source pass. Product access and scenario tests were not run.
Idea parking [partial] Suggested TODO cards can be started or dismissed. Sources: jules:b10j-suggested.
Explicit dispatch [supported] Suggested tasks start with Start, and plans need approval unless the timer auto-approves. Sources: jules:b10j-suggested, jules:b10j-plan.
Task session separation [unknown] Not established for task session separation in the named first-party source pass. Product access and scenario tests were not run.
Metadata [unknown] Not established for metadata in the named first-party source pass. Product access and scenario tests were not run.
Durable states [unknown] Not established for durable states in the named first-party source pass. Product access and scenario tests were not run.
External tracker requirement [unsupported] No external tracker is required; a prompt alone starts a task. Sources: jules:b10j-start.
Agent-native issue operations: Session IDs are shared across the API, CLI and web URLs. Agents read session state and lists through MCP tools or the API. Agents create sessions through the API or MCP; Linear issues are reachable through the Linear MCP server. Not established: update, claim, assign, state changes, dependencies, children, results, human visibility, attribution, permissions, conflicts.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: update, claim, assign, state_changes, dependencies, children, results, human_visibility, attribution, permissions, conflicts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Humans request edits to the proposed plan through chat; direct structured requirements editing is not established. Jules revises its task plan from feedback. Approve plan permits implementation, but the docs also describe timer-based automatic approval.
Scope
Surfaces: Jules web/cloud, Jules Tools remote-session CLI · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: persistent_requirements, revisions, implementation_links, later_retrieval, drift_detection, review_integration. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
Persistent requirements [unknown] Not established for persistent requirements in the named first-party source pass. Product access and scenario tests were not run.
Human edits [partial] Humans request edits to the proposed plan through chat; direct structured requirements editing is not established. Sources: jules:gap07-plans.
Agent edits [supported] Jules revises its task plan from feedback. Sources: jules:gap07-plans.
Revisions [unknown] Not established for revisions in the named first-party source pass. Product access and scenario tests were not run.
Approvals [partial] Approve plan permits implementation, but the docs also describe timer-based automatic approval. Sources: jules:gap07-plans.
Implementation links [unknown] Not established for implementation links in the named first-party source pass. Product access and scenario tests were not run.
Later retrieval [unknown] Not established for later retrieval in the named first-party source pass. Product access and scenario tests were not run.
Drift detection [unknown] Not established for drift detection in the named first-party source pass. Product access and scenario tests were not run.
Review integration [unknown] Not established for review integration in the named first-party source pass. Product access and scenario tests were not run.
The guide lists Free/Pro/Ultra daily task caps of 15/100/300 and concurrent caps of 3/15/60, checked 7 November 2026; shutdown timing takes precedence. Several tasks run simultaneously, each in its own VM. Plans allow 3, 15 or 60 concurrent tasks. The repo view lists running, completed, failed and waiting tasks; API sessions report eight states.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: observed_concurrency. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
5 atomic answers
Concurrent sessions [supported] Several tasks run simultaneously, each in its own VM. Sources: jules:b10j-tasks.
Quotas [supported] The guide lists Free/Pro/Ultra daily task caps of 15/100/300 and concurrent caps of 3/15/60, checked 7 November 2026; shutdown timing takes precedence. Sources: jules:nov07-limits.
Observed concurrency [unknown] Not established for observed concurrency in the named first-party source pass. Product access and scenario tests were not run.
Status visibility [supported] The repo view lists running, completed, failed and waiting tasks; API sessions report eight states. Sources: jules:b10j-repo, jules:b10j-api-sessions.
Ownership and dispatch: Adding the jules label to a GitHub issue assigns it to Jules; there is no other assignment model. Not established: human assignment, claims, queues, routing, duplicate prevention, ownership enforcement.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: human_assignment, claims, queues, routing, duplicate_prevention, ownership_enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
7 atomic answers
Human assignment [unknown] Not established for human assignment in the named first-party source pass. Product access and scenario tests were not run.
Agent assignment [partial] Adding the jules label to a GitHub issue assigns it to Jules; there is no other assignment model. Sources: jules:b10j-running.
Claims [unknown] Not established for claims in the named first-party source pass. Product access and scenario tests were not run.
Queues [unknown] Not established for queues in the named first-party source pass. Product access and scenario tests were not run.
Routing [unknown] Not established for routing in the named first-party source pass. Product access and scenario tests were not run.
Duplicate prevention [unknown] Not established for duplicate prevention in the named first-party source pass. Product access and scenario tests were not run.
Ownership enforcement [unknown] Not established for ownership enforcement in the named first-party source pass. Product access and scenario tests were not run.
Inspectable delegation and communication: A code critic and a Planning Critic review Jules's work; users cannot define roles. A real-time activity feed shows each step, and the critic's analysis is visible as it works. Completed tasks keep full logs and diffs and can be reopened. Chat follow-ups continue a session, and the API sends messages to it. Critic agents run automatically inside Jules; external agents invoke Jules through the MCP server or SDK. Not established: model harness effort, messages, results return, cross harness, orchestration owner, activation, authentication.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Google-hosted Jules and companion Jules Tools; targeted first-party pass 2026-11-13; published plans retain their pre-read-only scope and the November 11 turndown overrides new task access; no installed-product test; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: model_harness_effort, messages, results_return, cross_harness, orchestration_owner, activation, authentication. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Model harness effort [unknown] Not established for model harness effort in the named first-party source pass. Product access and scenario tests were not run.
Messages [unknown] Not established for messages in the named first-party source pass. Product access and scenario tests were not run.
Results return [unknown] Not established for results return in the named first-party source pass. Product access and scenario tests were not run.
Cross harness [unknown] Not established for cross harness in the named first-party source pass. Product access and scenario tests were not run.
Orchestration owner [unknown] Not established for orchestration owner in the named first-party source pass. Product access and scenario tests were not run.
Activation [unknown] Not established for activation in the named first-party source pass. Product access and scenario tests were not run.
Authentication [unknown] Not established for authentication in the named first-party source pass. Product access and scenario tests were not run.
Live progress [supported] A real-time activity feed shows each step, and the critic's analysis is visible as it works. Sources: jules:b10j-code, jules:b10j-cl-2025-09-03.
Retained results [supported] Completed tasks keep full logs and diffs and can be reopened. Sources: jules:b10j-repo.
The UI can pause work and later unpause it; this was documented rather than tested. The chat accepts feedback while the task runs and can revise the approach or plan. The activity feed and notification badge expose errors and intervention requests. Tasks can be paused or permanently deleted; no separate stop that keeps history is documented. Paused tasks can be resumed. Browser notifications report completion or a need for input. Plans wait for approval but auto-approve on a timer; feedback requests show in the feed and as an awaiting-feedback state. Completed tasks keep their logs and diffs.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: escalation, chat_terminal_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
10 atomic answers
Pause [supported] The UI can pause work and later unpause it; this was documented rather than tested. Sources: jules:nov07-tasks.
Stop [partial] Tasks can be paused or permanently deleted; no separate stop that keeps history is documented. Sources: jules:b10j-tasks.
Resume [supported] Paused tasks can be resumed. Sources: jules:b10j-tasks.
Steer [supported] The chat accepts feedback while the task runs and can revise the approach or plan. Sources: jules:nov07-tasks.
Notifications [supported] Browser notifications report completion or a need for input. Sources: jules:b10j-start.
Pending decisions [partial] Plans wait for approval but auto-approve on a timer; feedback requests show in the feed and as an awaiting-feedback state. Sources: jules:b10j-plan, jules:b10j-api-sessions.
Escalation [unknown] Not established for escalation in the named first-party source pass. Product access and scenario tests were not run.
Visible errors [supported] The activity feed and notification badge expose errors and intervention requests. Sources: jules:gap07-errors.
Chat terminal parity [unknown] Not established for chat terminal parity in the named first-party source pass. Product access and scenario tests were not run.
Retained history [supported] Completed tasks keep their logs and diffs. Sources: jules:b10j-repo.
Fleet and epic management UI: Failed and waiting tasks are labelled, and a red badge marks errors. Each repository view keeps its task history. Not established: fleet fixture, parent child, dependencies, workload, navigation errors, fixture mode.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: fleet_fixture, parent_child, dependencies, workload, navigation_errors, fixture_mode. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
8 atomic answers
Fleet fixture [unknown] Not established for fleet fixture in the named first-party source pass. Product access and scenario tests were not run.
Parent child [unknown] Not established for parent child in the named first-party source pass. Product access and scenario tests were not run.
Dependencies [unknown] Not established for dependencies in the named first-party source pass. Product access and scenario tests were not run.
Attention [partial] Failed and waiting tasks are labelled, and a red badge marks errors. Sources: jules:b10j-repo, jules:b10j-errors.
History [supported] Each repository view keeps its task history. Sources: jules:b10j-repo.
Workload [unknown] Not established for workload in the named first-party source pass. Product access and scenario tests were not run.
Navigation errors [unknown] Not established for navigation errors in the named first-party source pass. Product access and scenario tests were not run.
Fixture mode [unknown] Not established for fixture mode in the named first-party source pass. Product access and scenario tests were not run.
Workflow flexibility and orchestration visibility: A prompt produces a plan to approve, then the task runs. Three templated scheduled tasks (performance, design, security) are offered; no workflow preset is required. Tasks are plain-language prompts. Feedback during a task makes Jules revise its approach or replan. Not established: growing epic, agent configuration, live roles, retained relationships, discoverability, auth friction.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: growing_epic, agent_configuration, live_roles, retained_relationships, discoverability, auth_friction. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
10 atomic answers
Quick task [supported] A prompt produces a plan to approve, then the task runs. Sources: jules:b10j-start.
Growing epic [unknown] Not established for growing epic in the named first-party source pass. Product access and scenario tests were not run.
Presets [partial] Three templated scheduled tasks (performance, design, security) are offered; no workflow preset is required. Sources: jules:b10j-scheduled.
Natural language [supported] Tasks are plain-language prompts. Sources: jules:b10j-running.
Agent configuration [unknown] Not established for agent configuration in the named first-party source pass. Product access and scenario tests were not run.
In run changes [supported] Feedback during a task makes Jules revise its approach or replan. Sources: jules:b10j-running.
Live roles [unknown] Not established for live roles in the named first-party source pass. Product access and scenario tests were not run.
Retained relationships [unknown] Not established for retained relationships in the named first-party source pass. Product access and scenario tests were not run.
Discoverability [unknown] Not established for discoverability in the named first-party source pass. Product access and scenario tests were not run.
Auth friction [unknown] Not established for auth friction in the named first-party source pass. Product access and scenario tests were not run.
Laptop-independent execution: Jules Tools is a remote-session client; the coding worker executes in Google cloud VMs. The published worker architecture is Google-hosted cloud VMs, not user-operated execution servers. Jules is hosted only. Tasks run in cloud-based VMs, separate from the browser client. A VM is provisioned automatically for each task. Compute is included in the Jules plan. Task VMs are short-lived; the service has been read-only since 2026-11-11 and ends 2026-12-31. Jules explicitly lets users leave the app after submitting a task; it continues autonomously. Notifications report completion or plan readiness; cross-device task takeover was not established. Not established: hybrid, resources, region.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Google-hosted Jules and companion Jules Tools; targeted first-party pass 2026-11-13; published plans retain their pre-read-only scope and the November 11 turndown overrides new task access; no installed-product test; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The scoped first-party source pass does not establish byo_remote, self_hosted, hybrid, provisioning, payer, resources, region, expiry. No hands-on scenario was run.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: hybrid, resources, region. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
12 atomic answers
Local [unsupported] Jules Tools is a remote-session client; the coding worker executes in Google cloud VMs. Sources: jules:facet38-client-architecture.
Byo remote [unsupported] The published worker architecture is Google-hosted cloud VMs, not user-operated execution servers. Sources: jules:facet38-client-architecture.
Self hosted [unsupported] Jules is hosted only. Sources: jules:b10j-faq.
Managed cloud [supported] Tasks run in cloud-based VMs, separate from the browser client. Sources: jules:nov07-faq.
Hybrid [unknown] Not established for hybrid in the named first-party source pass. Product access and scenario tests were not run.
Payer [supported] Compute is included in the Jules plan. Sources: jules:b10j-limits.
Resources [unknown] Not established for resources in the named first-party source pass. Product access and scenario tests were not run.
Region [unknown] Not established for region in the named first-party source pass. Product access and scenario tests were not run.
Expiry [partial] Task VMs are short-lived; the service has been read-only since 2026-11-11 and ends 2026-12-31. Sources: jules:b10j-env, jules:b10j-cl-2026-10-29.
Client disconnect [supported] Jules explicitly lets users leave the app after submitting a task; it continues autonomously. Sources: jules:gap07-faq.
Other device continuation [partial] Notifications report completion or plan readiness; cross-device task takeover was not established. Sources: jules:gap07-faq.
Each task runs in its own short-lived VM; no adversarial isolation test was run. Work starts from a chosen branch and is published as a new branch. Task VMs have internet access; no egress controls are documented. Repository environment variables are opt-in per task and fixed once it starts. Each task has its own VM, logs, environment and code changes.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: checkout, worktree, container, os_sandbox, filesystem, process, security_boundary. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
12 atomic answers
Checkout [unknown] Not established for checkout in the named first-party source pass. Product access and scenario tests were not run.
Worktree [unknown] Not established for worktree in the named first-party source pass. Product access and scenario tests were not run.
Container [unknown] Not established for container in the named first-party source pass. Product access and scenario tests were not run.
Vm [supported] Each task runs in its own short-lived VM; no adversarial isolation test was run. Sources: jules:nov07-environment.
Os sandbox [unknown] Not established for os sandbox in the named first-party source pass. Product access and scenario tests were not run.
Filesystem [unknown] Not established for filesystem in the named first-party source pass. Product access and scenario tests were not run.
Process [unknown] Not established for process in the named first-party source pass. Product access and scenario tests were not run.
Network [partial] Task VMs have internet access; no egress controls are documented. Sources: jules:b10j-faq.
Secrets [partial] Repository environment variables are opt-in per task and fixed once it starts. Sources: jules:b10j-cl-2025-10-01.
Code separation [supported] Each task has its own VM, logs, environment and code changes. Sources: jules:b10j-tasks.
Security boundary [unknown] Not established for security boundary in the named first-party source pass. Product access and scenario tests were not run.
Immutable API activities can be used to reconstruct the session’s history; this does not prove process recovery. Tasks continue after the user leaves the app. The service has been read-only since 2026-11-11 and ends 2026-12-31. Immutable session activities can reconstruct a session. Paused tasks resume. Users can rerun a task from its summary after editing the setup script or prompt.
Scope
Surfaces: Jules web/cloud, Jules Tools remote-session CLI · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: worker_crash, service_restart, process_reconnect, context_loss, duplicate_actions, multi_day_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
12 atomic answers
Client disconnect [supported] Tasks continue after the user leaves the app. Sources: jules:b10j-faq.
Worker crash [unknown] Not established for worker crash in the named first-party source pass. Product access and scenario tests were not run.
Service restart [unknown] Not established for service restart in the named first-party source pass. Product access and scenario tests were not run.
Expiry [partial] The service has been read-only since 2026-11-11 and ends 2026-12-31. Sources: jules:b10j-cl-2026-10-29.
Transcript reload [supported] Immutable session activities can reconstruct a session. Sources: jules:b10j-cl-2026-01-26-4.
Process reconnect [unknown] Not established for process reconnect in the named first-party source pass. Product access and scenario tests were not run.
State reconstruction [supported] Immutable API activities can be used to reconstruct the session’s history; this does not prove process recovery. Sources: jules:gap07-outputs.
Context loss [unknown] Not established for context loss in the named first-party source pass. Product access and scenario tests were not run.
Duplicate actions [unknown] Not established for duplicate actions in the named first-party source pass. Product access and scenario tests were not run.
Manual repair [supported] Users can rerun a task from its summary after editing the setup script or prompt. Sources: jules:b10j-errors.
Multi day continuity [unknown] Not established for multi day continuity in the named first-party source pass. Product access and scenario tests were not run.
Development environment reliability: Repository setup scripts install project dependencies. Successful setup snapshots are reused by future tasks from the repository. Run and Snapshot executes the script and captures the resulting prepared environment. Long-running development servers and watchers are not supported in setup scripts; discrete install/test commands are supported. Repository-level environment variables can be enabled for a task. Future tasks can reuse a successful prepared environment snapshot; exact invalidation behavior is not established. Jules infers setup from the repository, AGENTS.md or README. Not established: ports, collisions, automatic repair.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: ports, collisions, automatic_repair. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Caches [supported] Successful setup snapshots are reused by future tasks from the repository. Sources: jules:gap07-environment.
Snapshots [supported] Run and Snapshot executes the script and captures the resulting prepared environment. Sources: jules:gap07-environment.
Services [unsupported] Long-running development servers and watchers are not supported in setup scripts; discrete install/test commands are supported. Sources: jules:gap07-faq.
Ports [unknown] Not established for ports in the named first-party source pass. Product access and scenario tests were not run.
Secrets [supported] Repository-level environment variables can be enabled for a task. Sources: jules:b10j-cl-2025-10-01.
Duplicate installs [partial] Future tasks can reuse a successful prepared environment snapshot; exact invalidation behavior is not established. Sources: jules:gap07-environment.
Collisions [unknown] Not established for collisions in the named first-party source pass. Product access and scenario tests were not run.
Remote setup [supported] Jules infers setup from the repository, AGENTS.md or README. Sources: jules:b10j-env.
Automatic repair [unknown] Not established for automatic repair in the named first-party source pass. Product access and scenario tests were not run.
Jules retries eligible failed steps such as network or transient install failures. Persistent failures produce a failed task; the source does not specify provider-specific retries. Published rolling 24-hour task limits are 15/100/300, with concurrent limits 3/15/60 for Free/Pro/Ultra. Limits count tasks per rolling 24 hours; no per-task turn limit is documented.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: time_limits, token_limits, spend_limits, timeouts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
8 atomic answers
Time limits [unknown] Not established for time limits in the named first-party source pass. Product access and scenario tests were not run.
Turn limits [partial] Limits count tasks per rolling 24 hours; no per-task turn limit is documented. Sources: jules:b10j-limits.
Token limits [unknown] Not established for token limits in the named first-party source pass. Product access and scenario tests were not run.
Spend limits [unknown] Not established for spend limits in the named first-party source pass. Product access and scenario tests were not run.
Timeouts [unknown] Not established for timeouts in the named first-party source pass. Product access and scenario tests were not run.
Retries [supported] Jules retries eligible failed steps such as network or transient install failures. Sources: jules:gap07-errors.
Provider failures [partial] Persistent failures produce a failed task; the source does not specify provider-specific retries. Sources: jules:gap07-errors.
Enforcement [supported] Published rolling 24-hour task limits are 15/100/300, with concurrent limits 3/15/60 for Free/Pro/Ultra. Sources: jules:gap07-limits.
The live activity feed reports steps, outputs, errors and feedback requests. Activity records surface outputs and errors for completed steps. Completion summary includes changed files and added/changed lines. Completion summary includes total runtime. A failed step is shown in the feed and a red notification badge; persistent errors mark the task failed.
Scope
Surfaces: Jules web/cloud · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: traces, usage_export, agent_stats, project_stats, approval_status, reconnect_consistency, performance_method, responsiveness. No configured product fixture was run; documentation does not establish successful hands-on behavior.
13 atomic answers
Logs [supported] The live activity feed reports steps, outputs, errors and feedback requests. Sources: jules:gap07-review.
Traces [unknown] Not established for traces in the named first-party source pass. Product access and scenario tests were not run.
Failure reasons [supported] Activity records surface outputs and errors for completed steps. Sources: jules:gap07-review.
Usage export [unknown] Not established for usage export in the named first-party source pass. Product access and scenario tests were not run.
Task stats [supported] Completion summary includes changed files and added/changed lines. Sources: jules:gap07-review.
Agent stats [unknown] Not established for agent stats in the named first-party source pass. Product access and scenario tests were not run.
Project stats [unknown] Not established for project stats in the named first-party source pass. Product access and scenario tests were not run.
Time stats [supported] Completion summary includes total runtime. Sources: jules:gap07-review.
Failure status [supported] A failed step is shown in the feed and a red notification badge; persistent errors mark the task failed. Sources: jules:gap07-errors.
Approval status [unknown] Not established for approval status in the named first-party source pass. Product access and scenario tests were not run.
Reconnect consistency [unknown] Not established for reconnect consistency in the named first-party source pass. Product access and scenario tests were not run.
Performance method [unknown] Not established for performance method in the named first-party source pass. Product access and scenario tests were not run.
Responsiveness [unknown] Not established for responsiveness in the named first-party source pass. Product access and scenario tests were not run.
Per-task API and compute cost: The allowance is tasks per day and concurrent tasks by plan; no per-task cost is shown. Not established: task cost, session cost, child cost, epic cost, harness aggregation, billed vs estimated, tokens, provider reconciliation, compute cost, refresh delay, alerts, export, drilldown.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: task_cost, session_cost, child_cost, epic_cost, harness_aggregation, billed_vs_estimated, tokens, provider_reconciliation, compute_cost, refresh_delay, alerts, export, drilldown. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
14 atomic answers
Task cost [unknown] Not established for task cost in the named first-party source pass. Product access and scenario tests were not run.
Session cost [unknown] Not established for session cost in the named first-party source pass. Product access and scenario tests were not run.
Child cost [unknown] Not established for child cost in the named first-party source pass. Product access and scenario tests were not run.
Epic cost [unknown] Not established for epic cost in the named first-party source pass. Product access and scenario tests were not run.
Harness aggregation [unknown] Not established for harness aggregation in the named first-party source pass. Product access and scenario tests were not run.
Billed vs estimated [unknown] Not established for billed vs estimated in the named first-party source pass. Product access and scenario tests were not run.
Tokens [unknown] Not established for tokens in the named first-party source pass. Product access and scenario tests were not run.
Subscription allowance [partial] The allowance is tasks per day and concurrent tasks by plan; no per-task cost is shown. Sources: jules:b10j-limits.
Provider reconciliation [unknown] Not established for provider reconciliation in the named first-party source pass. Product access and scenario tests were not run.
Compute cost [unknown] Not established for compute cost in the named first-party source pass. Product access and scenario tests were not run.
Refresh delay [unknown] Not established for refresh delay in the named first-party source pass. Product access and scenario tests were not run.
Alerts [unknown] Not established for alerts in the named first-party source pass. Product access and scenario tests were not run.
Export [unknown] Not established for export in the named first-party source pass. Product access and scenario tests were not run.
Drilldown [unknown] Not established for drilldown in the named first-party source pass. Product access and scenario tests were not run.
Free, Pro and Ultra allow 3, 15 or 60 concurrent tasks. Task quotas are rolling 24-hour limits of 15, 100 or 300 by plan.
Scope
Surfaces: Jules web/cloud, Jules Tools remote-session CLI · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: queues, cpu_ram, backpressure, host_awareness, check_reuse, check_deduplication, bounded_tests, cancellation, fairness, recovery. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
Concurrency [supported] Free, Pro and Ultra allow 3, 15 or 60 concurrent tasks. Sources: jules:gap07-limits.
Queues [unknown] Not established for queues in the named first-party source pass. Product access and scenario tests were not run.
Cpu ram [unknown] Not established for cpu ram in the named first-party source pass. Product access and scenario tests were not run.
Backpressure [unknown] Not established for backpressure in the named first-party source pass. Product access and scenario tests were not run.
Host awareness [unknown] Not established for host awareness in the named first-party source pass. Product access and scenario tests were not run.
Check reuse [unknown] Not established for check reuse in the named first-party source pass. Product access and scenario tests were not run.
Check deduplication [unknown] Not established for check deduplication in the named first-party source pass. Product access and scenario tests were not run.
Bounded tests [unknown] Not established for bounded tests in the named first-party source pass. Product access and scenario tests were not run.
Cancellation [unknown] Not established for cancellation in the named first-party source pass. Product access and scenario tests were not run.
Fairness [unknown] Not established for fairness in the named first-party source pass. Product access and scenario tests were not run.
Recovery [unknown] Not established for recovery in the named first-party source pass. Product access and scenario tests were not run.
Shared limits [supported] Task quotas are rolling 24-hour limits of 15, 100 or 300 by plan. Sources: jules:gap07-limits.
Live human collaboration: Paid plans are for individual accounts only; Workspace upgrades are not offered. Not established: visibility, discussion, comments, presence, coprompting, ordering, conflicts, attribution, permissions, owner online.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Google-hosted Jules and companion Jules Tools; targeted first-party pass 2026-11-13; published plans retain their pre-read-only scope and the November 11 turndown overrides new task access; no installed-product test; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: visibility, discussion, comments, presence, coprompting, ordering, conflicts, attribution, permissions, owner_online. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
11 atomic answers
Visibility [unknown] Not established for visibility in the named first-party source pass. Product access and scenario tests were not run.
Discussion [unknown] Not established for discussion in the named first-party source pass. Product access and scenario tests were not run.
Comments [unknown] Not established for comments in the named first-party source pass. Product access and scenario tests were not run.
Presence [unknown] Not established for presence in the named first-party source pass. Product access and scenario tests were not run.
Coprompting [unknown] Not established for coprompting in the named first-party source pass. Product access and scenario tests were not run.
Ordering [unknown] Not established for ordering in the named first-party source pass. Product access and scenario tests were not run.
Conflicts [unknown] Not established for conflicts in the named first-party source pass. Product access and scenario tests were not run.
Attribution [unknown] Not established for attribution in the named first-party source pass. Product access and scenario tests were not run.
Permissions [unknown] Not established for permissions in the named first-party source pass. Product access and scenario tests were not run.
Plan restrictions [partial] Paid plans are for individual accounts only; Workspace upgrades are not offered. Sources: jules:b10j-limits.
Owner online [unknown] Not established for owner online in the named first-party source pass. Product access and scenario tests were not run.
Roles and access boundaries: Paid plans cover individual Google accounts only. Not established: organization roles, project roles, task roles, membership, sso, provisioning, unauthorized access, revocation.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Google-hosted Jules and companion Jules Tools; targeted first-party pass 2026-11-13; published plans retain their pre-read-only scope and the November 11 turndown overrides new task access; no installed-product test; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: organization_roles, project_roles, task_roles, membership, sso, provisioning, unauthorized_access, revocation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
9 atomic answers
Organization roles [unknown] Not established for organization roles in the named first-party source pass. Product access and scenario tests were not run.
Project roles [unknown] Not established for project roles in the named first-party source pass. Product access and scenario tests were not run.
Task roles [unknown] Not established for task roles in the named first-party source pass. Product access and scenario tests were not run.
Membership [unknown] Not established for membership in the named first-party source pass. Product access and scenario tests were not run.
Sso [unknown] Not established for sso in the named first-party source pass. Product access and scenario tests were not run.
Provisioning [unknown] Not established for provisioning in the named first-party source pass. Product access and scenario tests were not run.
Unauthorized access [unknown] Not established for unauthorized access in the named first-party source pass. Product access and scenario tests were not run.
Revocation [unknown] Not established for revocation in the named first-party source pass. Product access and scenario tests were not run.
Plan scope [supported] Paid plans cover individual Google accounts only. Sources: jules:b10j-limits.
The guide says an unattended plan eventually auto-approves on a timer; plan review is not an indefinite authorization gate. Environment variables are enabled per task and cannot change mid-task. Users publish the branch or PR; the API can auto-create PRs when asked. The API can require plan approval, and Reactive Mode limits PR-comment actions to @Jules mentions.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: command, tool, network, approver_identity, lifetime, allow, deny, revoke, tunnels, enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
14 atomic answers
Command [unknown] Not established for command in the named first-party source pass. Product access and scenario tests were not run.
Tool [unknown] Not established for tool in the named first-party source pass. Product access and scenario tests were not run.
Network [unknown] Not established for network in the named first-party source pass. Product access and scenario tests were not run.
Secret [partial] Environment variables are enabled per task and cannot change mid-task. Sources: jules:b10j-cl-2025-10-01.
Delivery [partial] Users publish the branch or PR; the API can auto-create PRs when asked. Sources: jules:b10j-code, jules:b10j-api.
Approver identity [unknown] Not established for approver identity in the named first-party source pass. Product access and scenario tests were not run.
Lifetime [unknown] Not established for lifetime in the named first-party source pass. Product access and scenario tests were not run.
Allow [unknown] Not established for allow in the named first-party source pass. Product access and scenario tests were not run.
Deny [unknown] Not established for deny in the named first-party source pass. Product access and scenario tests were not run.
Revoke [unknown] Not established for revoke in the named first-party source pass. Product access and scenario tests were not run.
Tunnels [unknown] Not established for tunnels in the named first-party source pass. Product access and scenario tests were not run.
Defaults [supported] The guide says an unattended plan eventually auto-approves on a timer; plan review is not an indefinite authorization gate. Sources: jules:nov07-plan.
Safer modes [partial] The API can require plan approval, and Reactive Mode limits PR-comment actions to @Jules mentions. Sources: jules:b10j-api, jules:b10j-cl-2025-09-23.
Enforcement [unknown] Not established for enforcement in the named first-party source pass. Product access and scenario tests were not run.
Session activities record the steps taken by user and agent. The API exposes activity collections with timestamp filters. API activities are documented as immutable once created. Activity immutability is a documented event-source contract; tamper resistance was not tested. Task history persists per repository.
Scope
Surfaces: Jules web/cloud, Jules Tools remote-session CLI · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: approvals, edits, discussion, decisions, cross_user_persistence, retention. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
11 atomic answers
Actions [supported] Session activities record the steps taken by user and agent. Sources: jules:gap07-outputs.
Approvals [unknown] Not established for approvals in the named first-party source pass. Product access and scenario tests were not run.
Edits [unknown] Not established for edits in the named first-party source pass. Product access and scenario tests were not run.
Discussion [unknown] Not established for discussion in the named first-party source pass. Product access and scenario tests were not run.
Decisions [unknown] Not established for decisions in the named first-party source pass. Product access and scenario tests were not run.
Cross user persistence [unknown] Not established for cross user persistence in the named first-party source pass. Product access and scenario tests were not run.
Cross session persistence [supported] Task history persists per repository. Sources: jules:b10j-repo.
Export [supported] The API exposes activity collections with timestamp filters. Sources: jules:gap07-outputs.
Mutability [supported] API activities are documented as immutable once created. Sources: jules:gap07-outputs.
Retention [unknown] Not established for retention in the named first-party source pass. Product access and scenario tests were not run.
Integrity [partial] Activity immutability is a documented event-source contract; tamper resistance was not tested. Sources: jules:gap07-outputs.
The expanded diff editor shows all files Jules changed. Users give real-time review feedback through the task chat. Users can ask Jules to revise logic, add tests or fix behavior from chat.
Scope
Surfaces: Jules web/cloud · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: pending_reviews, evidence_navigation, shipping_guidance, effort, missed_evidence, keyboard, narrow_screen, context_switching, roles, retained_context. No configured product fixture was run; documentation does not establish successful hands-on behavior.
13 atomic answers
Pending reviews [unknown] Not established for pending reviews in the named first-party source pass. Product access and scenario tests were not run.
Change understanding [supported] The expanded diff editor shows all files Jules changed. Sources: jules:gap07-review.
Evidence navigation [unknown] Not established for evidence navigation in the named first-party source pass. Product access and scenario tests were not run.
Comments [supported] Users give real-time review feedback through the task chat. Sources: jules:gap07-review.
Request changes [supported] Users can ask Jules to revise logic, add tests or fix behavior from chat. Sources: jules:gap07-review.
Shipping guidance [unknown] Not established for shipping guidance in the named first-party source pass. Product access and scenario tests were not run.
Effort [unknown] Not established for effort in the named first-party source pass. Product access and scenario tests were not run.
Missed evidence [unknown] Not established for missed evidence in the named first-party source pass. Product access and scenario tests were not run.
Keyboard [unknown] Not established for keyboard in the named first-party source pass. Product access and scenario tests were not run.
Narrow screen [unknown] Not established for narrow screen in the named first-party source pass. Product access and scenario tests were not run.
Context switching [unknown] Not established for context switching in the named first-party source pass. Product access and scenario tests were not run.
Roles [unknown] Not established for roles in the named first-party source pass. Product access and scenario tests were not run.
Retained context [unknown] Not established for retained context in the named first-party source pass. Product access and scenario tests were not run.
The feed includes mini diffs and a full changed-file diff editor. Jules can return a screenshot of the rendered frontend. Frontend verification can return visual test evidence with changes. Task logs and diffs are kept until shutdown and can be exported. Uploaded task images are not committed to the repository; other leakage paths are not documented.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: documents, recordings, previews, reviewer_outputs, gallery, task_links, revision_links, child_findings. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
13 atomic answers
Diffs [supported] The feed includes mini diffs and a full changed-file diff editor. Sources: jules:nov07-review.
Documents [unknown] Not established for documents in the named first-party source pass. Product access and scenario tests were not run.
Screenshots [supported] Jules can return a screenshot of the rendered frontend. Sources: jules:gap07-web-tests.
Recordings [unknown] Not established for recordings in the named first-party source pass. Product access and scenario tests were not run.
Previews [unknown] Not established for previews in the named first-party source pass. Product access and scenario tests were not run.
Test outputs [supported] Frontend verification can return visual test evidence with changes. Sources: jules:gap07-web-tests.
Reviewer outputs [unknown] Not established for reviewer outputs in the named first-party source pass. Product access and scenario tests were not run.
Gallery [unknown] Not established for gallery in the named first-party source pass. Product access and scenario tests were not run.
Task links [unknown] Not established for task links in the named first-party source pass. Product access and scenario tests were not run.
Revision links [unknown] Not established for revision links in the named first-party source pass. Product access and scenario tests were not run.
Child findings [unknown] Not established for child findings in the named first-party source pass. Product access and scenario tests were not run.
Prompt leakage [partial] Uploaded task images are not committed to the repository; other leakage paths are not documented. Sources: jules:b10j-running.
Verification and spec gates: Setup scripts can run tests before snapshotting. Setup scripts can include linters. CI Fixer responds to GitHub Actions failures on Jules-created PRs. A critic agent reviews code and a Planning Critic reviews auto-approved plans before execution. CI Fixer repairs and resubmits; the source does not establish an immutable merge gate. Users configure repository setup/validation commands; immutable required delivery gates were not established. Not established: types, spec checks, required checks, requirement conflicts, enforced policy.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: types, spec_checks, required_checks, requirement_conflicts, enforced_policy. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
11 atomic answers
Tests [supported] Setup scripts can run tests before snapshotting. Sources: jules:gap07-environment.
Spec checks [unknown] Not established for spec checks in the named first-party source pass. Product access and scenario tests were not run.
Required checks [unknown] Not established for required checks in the named first-party source pass. Product access and scenario tests were not run.
Failure blocking [partial] CI Fixer repairs and resubmits; the source does not establish an immutable merge gate. Sources: jules:gap07-ci.
Requirement conflicts [unknown] Not established for requirement conflicts in the named first-party source pass. Product access and scenario tests were not run.
Configured policy [partial] Users configure repository setup/validation commands; immutable required delivery gates were not established. Sources: jules:gap07-environment.
Enforced policy [unknown] Not established for enforced policy in the named first-party source pass. Product access and scenario tests were not run.
Commit authorship is configurable as Jules, coauthored or user-only. Publish branch and Publish PR push results to GitHub; PR creation is separate from merging. Jules automatically detects and fixes failing GitHub Actions checks on the PRs it creates. Publish branch pushes the work to a new GitHub branch. Jules responds to PR review comments with commits; Reactive Mode limits it to @Jules mentions.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: worktrees, rebase, conflicts, product_state. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
9 atomic answers
Branches [supported] Publish branch pushes the work to a new GitHub branch. Sources: jules:b10j-code.
Worktrees [unknown] Not established for worktrees in the named first-party source pass. Product access and scenario tests were not run.
Commits [supported] Commit authorship is configurable as Jules, coauthored or user-only. Sources: jules:gap07-ci.
Pull requests [supported] Publish branch and Publish PR push results to GitHub; PR creation is separate from merging. Sources: jules:nov07-review.
Comments [supported] Jules responds to PR review comments with commits; Reactive Mode limits it to @Jules mentions. Sources: jules:b10j-cl-2025-09-23.
Ci response [supported] Jules automatically detects and fixes failing GitHub Actions checks on the PRs it creates. Sources: jules:gap07-ci.
Rebase [unknown] Not established for rebase in the named first-party source pass. Product access and scenario tests were not run.
Conflicts [unknown] Not established for conflicts in the named first-party source pass. Product access and scenario tests were not run.
Product state [unknown] Not established for product state in the named first-party source pass. Product access and scenario tests were not run.
Merge and deployment authority: Users merge PRs in GitHub; the experimental fleet package can merge PRs sequentially. Not established: approve, release, deploy, exact revision, authority enforcement.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: approve, release, deploy, exact_revision, authority_enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
6 atomic answers
Approve [unknown] Not established for approve in the named first-party source pass. Product access and scenario tests were not run.
Merge [partial] Users merge PRs in GitHub; the experimental fleet package can merge PRs sequentially. Sources: jules:b10j-code, jules:b10j-npm-fleet.
Release [unknown] Not established for release in the named first-party source pass. Product access and scenario tests were not run.
Deploy [unknown] Not established for deploy in the named first-party source pass. Product access and scenario tests were not run.
Exact revision [unknown] Not established for exact revision in the named first-party source pass. Product access and scenario tests were not run.
Authority enforcement [unknown] Not established for authority enforcement in the named first-party source pass. Product access and scenario tests were not run.
The task summary identifies branch and commit details; a direct commit permalink was not established. Issue-triggered work returns a link to the PR for review. Publish branch or Publish PR exports work to GitHub; source distinguishes branch author and PR creator.
Scope
Surfaces: Jules web/cloud · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: build_links, deployment_links, retained_evidence, rollback, revert, stale_approval_invalidation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
Commit links [partial] The task summary identifies branch and commit details; a direct commit permalink was not established. Sources: jules:gap07-review.
Pr links [supported] Issue-triggered work returns a link to the PR for review. Sources: jules:nov07-tasks.
Build links [unknown] Not established for build links in the named first-party source pass. Product access and scenario tests were not run.
Deployment links [unknown] Not established for deployment links in the named first-party source pass. Product access and scenario tests were not run.
Delivery status [supported] Publish branch or Publish PR exports work to GitHub; source distinguishes branch author and PR creator. Sources: jules:gap07-review.
Retained evidence [unknown] Not established for retained evidence in the named first-party source pass. Product access and scenario tests were not run.
Rollback [unknown] Not established for rollback in the named first-party source pass. Product access and scenario tests were not run.
Revert [unknown] Not established for revert in the named first-party source pass. Product access and scenario tests were not run.
Stale approval invalidation [unknown] Not established for stale approval invalidation in the named first-party source pass. Product access and scenario tests were not run.
The hosted Jules application is governed by the vendor-authored Google Terms of Service linked from Jules. This does not assign that license to separate SDK/example code. The SDK and fleet packages are Apache-2.0, the MCP package is ISC and the GitHub Action is MIT. Public GitHub repositories exist for the Jules GitHub Action (MIT), Jules agent skills (Apache-2.0) and the jules-awesome-list prompt collection named as the @google/jules package repository. The jules-sdk repository returned 404 on 2026-11-22, but the published SDK, MCP and fleet npm packages ship readable code, and the SDK package's source map embeds its original TypeScript sources. The Jules Tools npm package only downloads a prebuilt binary, and the hosted Jules service and worker are closed.
Scope
Surfaces: Jules web/cloud, Jules Tools remote-session CLI · Version: Earlier findings: Google-hosted Jules and companion Jules Tools; targeted first-party pass 2026-11-13; published plans retain their pre-read-only scope and the November 11 turndown overrides new task access; no installed-product test; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13); google-labs-code GitHub repositories listed and npm package contents read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-22
The scoped first-party source pass does not establish client_license, hosted_extensions, source_visibility, source_revision, hosted_parity. No hands-on scenario was run.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: client_license, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
6 atomic answers
Client license [unknown] Not established for client license in the named first-party source pass. Product access and scenario tests were not run.
Server license [supported] The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage. Sources: jules:facet38-service-terms.
Source visibility [partial] Public GitHub repositories exist for the Jules GitHub Action (MIT), Jules agent skills (Apache-2.0) and the jules-awesome-list prompt collection named as the @google/jules package repository. The jules-sdk repository returned 404 on 2026-11-22, but the published SDK, MCP and fleet npm packages ship readable code, and the SDK package's source map embeds its original TypeScript sources. The Jules Tools npm package only downloads a prebuilt binary, and the hosted Jules service and worker are closed. Sources: jules:b10j-action, jules:c165-gh-repos, jules:b10j-sdk-repo, jules:b10j-npm-sdk, jules:c165-npm-sdk-source, jules:b10j-npm-cli.
Source revision [unknown] Not established for source revision in the named first-party source pass. Product access and scenario tests were not run.
Hosted parity [unknown] Not established for hosted parity in the named first-party source pass. Product access and scenario tests were not run.
The diff editor has download/copy controls for generated changes. REST changed-file outputs are Git patches. Jules runs only as a Google-hosted service in cloud VMs. A Google account, the Jules GitHub app and Google cloud VMs are required. Code, branches and PRs stay in GitHub; Jules configuration and history need a signed-in export before shutdown. The turndown export saves every session's prompt, plan, activity log and patches, but its script relies on undocumented endpoints.
Scope
Surfaces: Jules Tools remote-session CLI, Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: import, cancellation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
8 atomic answers
Self hosting [unsupported] Jules runs only as a Google-hosted service in cloud VMs. Sources: jules:b10j-faq.
Vendor dependencies [supported] A Google account, the Jules GitHub app and Google cloud VMs are required. Sources: jules:b10j-start, jules:b10j-faq.
Export [supported] The diff editor has download/copy controls for generated changes. Sources: jules:gap07-review.
Import [unknown] Not established for import in the named first-party source pass. Product access and scenario tests were not run.
Formats [supported] REST changed-file outputs are Git patches. Sources: jules:gap07-outputs.
Cancellation [unknown] Not established for cancellation in the named first-party source pass. Product access and scenario tests were not run.
Account independence [partial] Code, branches and PRs stay in GitHub; Jules configuration and history need a signed-in export before shutdown. Sources: jules:b10j-cl-2026-10-29.
History portability [partial] The turndown export saves every session's prompt, plan, activity log and patches, but its script relies on undocumented endpoints. Sources: jules:b10j-cl-2026-10-29.
Jules explicitly does not train models on private repository content. Integration API keys are stored encrypted and never shown in chat; the turndown export writes environment variable values in plaintext.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: code_data, prompts, logs, artifacts, retention, deletion, residency, subprocessors, telemetry_disclosure, telemetry_defaults, telemetry_controls, consent_prompt, provider_separation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
15 atomic answers
Code data [unknown] Not established for code data in the named first-party source pass. Product access and scenario tests were not run.
Prompts [unknown] Not established for prompts in the named first-party source pass. Product access and scenario tests were not run.
Credentials [partial] Integration API keys are stored encrypted and never shown in chat; the turndown export writes environment variable values in plaintext. Sources: jules:b10j-integrations, jules:b10j-cl-2026-10-29.
Logs [unknown] Not established for logs in the named first-party source pass. Product access and scenario tests were not run.
Artifacts [unknown] Not established for artifacts in the named first-party source pass. Product access and scenario tests were not run.
Retention [unknown] Not established for retention in the named first-party source pass. Product access and scenario tests were not run.
Deletion [unknown] Not established for deletion in the named first-party source pass. Product access and scenario tests were not run.
Training [supported] Jules explicitly does not train models on private repository content. Sources: jules:gap07-faq.
Residency [unknown] Not established for residency in the named first-party source pass. Product access and scenario tests were not run.
Subprocessors [unknown] Not established for subprocessors in the named first-party source pass. Product access and scenario tests were not run.
Telemetry disclosure [unknown] Not established for telemetry disclosure in the named first-party source pass. Product access and scenario tests were not run.
Telemetry defaults [unknown] Not established for telemetry defaults in the named first-party source pass. Product access and scenario tests were not run.
Telemetry controls [unknown] Not established for telemetry controls in the named first-party source pass. Product access and scenario tests were not run.
Consent prompt [unknown] Not established for consent prompt in the named first-party source pass. Product access and scenario tests were not run.
Provider separation [unknown] Not established for provider separation in the named first-party source pass. Product access and scenario tests were not run.
Price and included usage: Plans are per individual account; family plan members each get their own limits, and business users use an interest form. Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here. Not established: currency, interval, seat minimum, workspace fees, credits, trial, overages, taxes, model cost, compute cost.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: currency, interval, seat_minimum, workspace_fees, credits, trial, overages, taxes, model_cost, compute_cost. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
12 atomic answers
Currency [unknown] Not established for currency in the named first-party source pass. Product access and scenario tests were not run.
Interval [unknown] Not established for interval in the named first-party source pass. Product access and scenario tests were not run.
Seats [partial] Plans are per individual account; family plan members each get their own limits, and business users use an interest form. Sources: jules:b10j-limits.
Seat minimum [unknown] Not established for seat minimum in the named first-party source pass. Product access and scenario tests were not run.
Workspace fees [unknown] Not established for workspace fees in the named first-party source pass. Product access and scenario tests were not run.
Included usage [supported] Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here. Sources: jules:nov07-limits.
Credits [unknown] Not established for credits in the named first-party source pass. Product access and scenario tests were not run.
Trial [unknown] Not established for trial in the named first-party source pass. Product access and scenario tests were not run.
Overages [unknown] Not established for overages in the named first-party source pass. Product access and scenario tests were not run.
Taxes [unknown] Not established for taxes in the named first-party source pass. Product access and scenario tests were not run.
Model cost [unknown] Not established for model cost in the named first-party source pass. Product access and scenario tests were not run.
Compute cost [unknown] Not established for compute cost in the named first-party source pass. Product access and scenario tests were not run.
Jules documents a recurring plan available without cost; service turndown restricts the remaining availability window. Free allows 15 tasks per rolling 24 hours and three concurrent tasks. Not paid-only: a no-cost plan was offered; since 2026-11-11 the service is read-only for everyone.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: trial, credits_trial, self_host_cost, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
10 atomic answers
Ongoing free [supported] Jules documents a recurring plan available without cost; service turndown restricts the remaining availability window. Sources: jules:gap07-faq.
Trial [unknown] Not established for trial in the named first-party source pass. Product access and scenario tests were not run.
Credits trial [unknown] Not established for credits trial in the named first-party source pass. Product access and scenario tests were not run.
Self host cost [unknown] Not established for self host cost in the named first-party source pass. Product access and scenario tests were not run.
Paid only [unsupported] Not paid-only: a no-cost plan was offered; since 2026-11-11 the service is read-only for everyone. Sources: jules:b10j-faq, jules:b10j-cl-2026-10-29.
Early access [unknown] Not established for early access in the named first-party source pass. Product access and scenario tests were not run.
Free scenarios [unknown] Not established for free scenarios in the named first-party source pass. Product access and scenario tests were not run.
Card required [unknown] Not established for card required in the named first-party source pass. Product access and scenario tests were not run.
Usage caps [supported] Free allows 15 tasks per rolling 24 hours and three concurrent tasks. Sources: jules:gap07-limits.
Paid evaluation [unknown] Not established for paid evaluation in the named first-party source pass. Product access and scenario tests were not run.
Plan task allowances are 15/100/300 daily and 3/15/60 concurrent. Plans are measured in tasks per rolling 24 hours and concurrent tasks.
Scope
Surfaces: Jules web/cloud · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-22 inherited-lead additions: jules.google docs and changelog read 2026-11-22 (docs describe the service before it became read-only on 2026-11-11; wind-down 2026-12-31), npm packages @google/jules 0.1.42, @google/jules-sdk 0.2.0, @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35, and jules-action bff7875 (2025-12-13) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: overages, compute_markup, model_markup, minimum_commitment, cancellation, sales_only_unknowns, transparency_classification. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
9 atomic answers
Units [supported] Plans are measured in tasks per rolling 24 hours and concurrent tasks. Sources: jules:b10j-limits.
Included limits [supported] Plan task allowances are 15/100/300 daily and 3/15/60 concurrent. Sources: jules:gap07-limits.
Overages [unknown] Not established for overages in the named first-party source pass. Product access and scenario tests were not run.
Compute markup [unknown] Not established for compute markup in the named first-party source pass. Product access and scenario tests were not run.
Model markup [unknown] Not established for model markup in the named first-party source pass. Product access and scenario tests were not run.
Minimum commitment [unknown] Not established for minimum commitment in the named first-party source pass. Product access and scenario tests were not run.
Cancellation [unknown] Not established for cancellation in the named first-party source pass. Product access and scenario tests were not run.
Sales only unknowns [unknown] Not established for sales only unknowns in the named first-party source pass. Product access and scenario tests were not run.
Transparency classification [unknown] Not established for transparency classification in the named first-party source pass. Product access and scenario tests were not run.
Tasks start from a plain-language prompt in the web prompt box on a chosen repo and branch, with optional PNG/JPEG images (under 5 MB) that are never committed. An activity feed, mini diffs and a diff editor show progress; chat feedback mid-task makes Jules replan. Tasks can be paused. Adding the jules label to a GitHub issue starts a task; Jules comments on the issue and links the resulting pull request.
Kind
documented
Locator
Choose a repo and branch; Write a clear prompt; Attach visual context; Watching Jules work; Final summary; Giving feedback mid-task; Pausing Jules; Starting tasks from GitHub Issues
The repo view lists running tasks first, completed tasks with full logs and diffs, and clearly labelled failed or waiting tasks; any task can be reopened to review its plan or continue feedback.
A real-time activity feed logs steps, outputs, errors and requests for feedback; the diff editor shows all changed files with download and copy. Publish branch or Publish PR pushes to GitHub, after which users review and merge the PR themselves.
Jules presents a step-by-step plan for approval; feedback in chat makes it update the plan. If the user navigates away, the plan is auto-approved on a timer.
Jules Tools installs from npm, signs in with the Google account, lists repositories and remote sessions, starts sessions (optionally several in parallel) and pulls results; the TUI shows sessions and diffs.
Free, Pro and Ultra document daily limits of 15/100/300 and concurrent limits of 3/15/60. Paid Google AI plans require individual Gmail accounts; business/Workspace upgrade routes are not yet available.
Users sign in with a Google account, connect GitHub and choose repositories, pick a repo and branch, write a prompt and request a plan to approve. Jules reads AGENTS.md at the repository root. Browser notifications report completion or a need for input.
Kind
documented
Locator
Login; Connect GitHub; Starting your first task; Include AGENTS.md file; Enabling notifications
Plans allow 15/100/300 tasks per rolling 24 hours and 3/15/60 concurrent tasks (Jules, Pro, Ultra), all with Gemini models. Paid plans come with Google AI Pro/Ultra and are only for individual @gmail.com accounts; business users fill an interest form. Family plan members each get their own limits. Users must be 18 or older. At the daily limit new tasks are blocked while existing tasks remain accessible.
The alpha REST API uses Jules API keys (at most 3) in X-Goog-Api-Key. Sessions have stable IDs; automationMode AUTO_CREATE_PR is optional (default no PR); API sessions auto-approve plans unless requirePlanApproval is true.
Kind
documented
Locator
alpha note; Generate Your API Key; API concepts; Your first API call
REST API can start sessions without a repository and return changed-file outputs in Git patch format. Activities are immutable records with timestamp filters and can reconstruct a session.
Several tasks can run simultaneously, each in its own VM with its own logs, environment setup and code changes. Paused tasks can be resumed; deleted tasks are removed permanently. Jules can only access GitHub repositories the user explicitly allows; other version control systems are future work.
Kind
documented
Locator
Starting tasks; Pausing or deleting tasks; Managing repositories
Jules is in Public Beta and includes a no-cost plan. Each task runs in a fresh cloud VM with internet access where Jules clones the repo and installs dependencies. Users can leave the app after submitting a task. Failed tasks are retried automatically, then marked failed with a notification.
Kind
documented
Locator
What is Jules?; Is Jules available without cost?; How does Jules work under the hood?; security; Can I leave Jules while its working?; What happens if a task fails?; Does Jules train on private repos?
Each task runs in a secure, short-lived Ubuntu VM. Without a script Jules studies the repository and uses AGENTS.md or README.md for setup hints; setup scripts can be validated with Run and Snapshot, and the snapshot is reused by later tasks in that repository.
Kind
documented
Locator
intro; Add a setup script; Test your setup script; Environment Snapshots
Alpha REST API uses X-Goog-Api-Key, with up to three keys. Sessions and activities expose plans, messages and progress. Alpha specifications and keys may change.
The MCP server, run with a JULES_API_KEY, exposes tools to create, list and inspect sessions, send replies or approve plans, read review context and diffs, and query a local session cache. Licensed ISC.
Integrations are read-only by default, can trigger Jules from external events, and store API keys encrypted, never exposed in chat or shared between sessions.
Jules supports only hand-selected MCP servers (Linear, Stitch, Neon, Tinybird, Context7, Supabase), each added with an API key in the user Settings page; Google limits the list deliberately for security and vets each server's permissions.
The npm package is a Node.js installer that downloads a prebuilt platform binary (Go GOOS/GOARCH naming) from storage.googleapis.com/jules-cli and runs it as the jules command.
Kind
documented
Locator
package.json binURL; index.cjs and run.cjs platform mapping to Go GOOS; published package @google/jules@0.1.42 (tarball sha1 cc2a1be2ea6e6ca53b51bcccf903ccf457431fe1)
Jules creates a step plan after setup and revises it from chat feedback. Approve plan starts execution, but the documentation says a timer may auto-approve when the user leaves.
Session activities are immutable, follow an event-source pattern, can reconstruct a session and can be fetched with a createTime filter; completed sessions return the change set as a Git patch.
Jules saves preferences, nudges and corrections during a task and references them in later same-repository tasks. Memory can be toggled per repository under Knowledge in repo settings.
Jules saves preferences, nudges and corrections per repository and uses them in later tasks there; memory can be turned on or off per repository under Knowledge.
The documented primary API resources are sources, sessions and session activities. This establishes a session/run API, but not independent issue-backlog records, human workspace roles or a shared-human prompting model.
Sessions can be created, listed, read, deleted, messaged and have plans approved; states are QUEUED, PLANNING, AWAITING_PLAN_APPROVAL, AWAITING_USER_FEEDBACK, IN_PROGRESS, PAUSED, COMPLETED and FAILED.
Kind
documented
Locator
Create, List, Get, Delete a Session; Send a Message; Approve a Plan; Session States
Failed steps are retried where possible, including network/install faults. Persistent failures get a failed state and UI badge. Humans can change setup/prompt and rerun.
Errors appear in the activity feed and as a red notification badge; transient failures are retried, persistent ones mark the task failed; users can rerun from the task summary after editing the setup script or prompt.
Kind
documented
Locator
How errors are reported; Automatic retry behavior; Debugging environment setup
Recurring tasks run automatically at a set frequency and cadence; three templated scheduled tasks (performance, design, security) are offered. The page says editing a scheduled task is not supported.
Kind
documented
Locator
Creating a Scheduled Task; Managing Scheduled Tasks; Common Use Cases
Jules can work after the user leaves the app, notifies plan/task completion, retries failed steps and never trains on private repository content. A recurring no-cost plan is documented. Setup scripts do not support long-lived servers.
Kind
documented
Locator
Leave while working; Failure handling; Training; Free access
Jules Tools is a local npm CLI/TUI for Google-authenticated remote sessions. It controls the Google-hosted Jules worker rather than executing the coding agent on the client or a user server.
Jules winds down on 2026-12-31; sessions could continue until 2026-11-11, after which Jules is read-only. Jules Tools plus a CLI-agent prompt export settings, environment variables, scheduled tasks, repositories, memories, setup scripts and every session (prompt, plan, activity log, patches) to a local folder; environment variable values are written in plaintext. The export script uses undocumented internal endpoints. Code, branches and PRs stay in GitHub.
Repository setup scripts install dependencies and run discrete checks. Successful Run and Snapshot captures the environment for future tasks, including preinstalled runtimes and tools.
Jules reads and responds to pull request comments and pushes commits with requested changes; Reactive Mode limits this to comments that mention @Jules.
Jules receives failed GitHub Actions checks on its own PRs, fixes and resubmits. User-level settings choose Jules-only, coauthored or user-only commits.
An explicitly experimental prototype analyses goals, files GitHub issues, dispatches Jules sessions and sequentially merges the resulting PRs from GitHub Actions or the CLI.
Kind
documented
Locator
README.md (Status: Very Experimental); dist/init/templates/merge; published package @google/jules-fleet@0.0.1-experimental.35 (tarball sha1 1c8bdd2a4b871bb9fb7fe2cf7dda7e5c2ddbeadf)
The Jules homepage links Google Terms of Service for its hosted application. These are vendor-authored service/software terms retaining Google intellectual-property rights, not an open-source grant for the hosted coding agent. Public SDK or example repositories do not establish the core service license.
Kind
documented
Locator
Jules homepage Terms of Service link; Google service/software permissions and intellectual property
The jules-sdk source repository named by the npm packages returned HTTP 404 on 2026-11-22. This concerns repository availability only: the published SDK, MCP and fleet packages still contain readable code.
Kind
documented
Locator
repository URL and pinned tree 19fc117 (both HTTP 404 on 2026-11-22); GitHub API repos/google-labs-code/jules-sdk 404
Three public, unarchived repositories exist: jules-action (MIT), jules-skills (Apache-2.0) and jules-awesome-list (a prompt collection with no declared license, named as the repository of the @google/jules npm package). jules-sdk returns 404.
Kind
documented
Locator
GitHub API orgs/google-labs-code/repos filtered to names containing jules; repos/google-labs-code/jules-sdk
The published SDK package ships readable bundled JavaScript, type declarations and a source map that embeds its original TypeScript sources; the MCP and fleet packages also ship readable JavaScript. Their code stays inspectable from npm although the jules-sdk repository returns 404.
Kind
documented
Locator
dist/index.mjs (4,369 lines of unminified ES module JavaScript); dist/*.d.ts; dist/index.mjs.map sourcesContent for 28 files under ../src (errors.ts, api.ts, sources.ts, ...); @google/jules-mcp 0.2.0 and @google/jules-fleet 0.0.1-experimental.35 dist/*.mjs; published package @google/jules-sdk@0.2.0 (tarball sha1 0e5f226d6338b66637e647df0c9f07175272802c)