Shutdown notice
Shuts down 31 Dec 2026
Google announced Jules will become read-only after November 11, 2026 and wind down December 31, 2026. The notice offers an export of configuration and session history; code, branches and PRs remain on GitHub.
Dates, scope and sources
-
Finding: Google announces read-only after November 11 and wind-down December 31, 2026; configuration and full session history can be exported locally.
Jules
Browser app. Agents run in the vendor's cloud.
Product websitejules.google Compare with others Missing or wrong data?
- Desktop app
- Not listed
- Browser
- Yes
- Phone
- Not listed
- Command line
- Yes
- Agents
- No
- Your subscription
- No
- Agents run
- In the vendor's cloud
- Laptop closed
- Keeps going
- Isolation
- VM
- Parallel agents
- Yes
- Scheduled runs
- Yes
- Coordinator agent
- Not listed
- Built-in issues
- Not listed
- Pull requests
- Yes
- Review screen
- Yes
- Team
- Not listed
- Self-hosting
- Not listed
- Licence
- Custom terms
- Price from
- Free
- How it charges
- Free plan and subscription
- Paid plans from
- Not listed
Receipts
- Checked
- · oldest answer 2026-11-07
- Findings
- 34 published · 27 cross-checked by a second agent · read them all
- Sources
- 25 public pages on 2 sites: jules.google, policies.google.com
- Screenshot
- jules.google, retrieved · first party docs · shows appearance, not capability
- Data
- /products/jules.json · .md
- Method
- Same rules for all 103 researched ADEs. How we check · Report wrong data
What it does
Where you use it
Jules has a browser client; mobile action parity was not established. Jules Tools is an npm-installed remote-session CLI with a TUI dashboard. Further scoped facts are recorded in the atomic answers.
Source and scope for Where you use itAgents it runs
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
Source and scope for Agents it runsAccounts and subscriptions
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. Google account eligibility controls Jules access and paid upgrades. Paid plan upgrades require an individual Gmail account; Workspace/business upgrades are not established.
Source and scope for Accounts and subscriptionsWhere agents run
Tasks run in cloud-based VMs, separate from the browser client. 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. 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.
Source and scope for Where agents runHow work is kept apart
Each task runs in its own short-lived VM; no adversarial isolation test was run.
Source and scope for How work is kept apartParallel work
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.
Source and scope for Parallel workScheduled runs
The dashboard supports scheduled recurring tasks with frequency and cadence. Recurring tasks can be edited, paused and resumed from their menu, according to the January 26 release. The scheduled task runs in the Jules cloud service; wind-down limits apply.
Source and scope for Scheduled runsGit and pull requests
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.
Source and scope for Git and pull requestsLicence and source
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.
Source and scope for Licence and sourcePrice
Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
Source and scope for PriceTyped filters
Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.
| Filter | Value |
|---|---|
| Desktop OS: macOS | Unknown |
| Desktop OS: Windows | Unknown |
| Desktop OS: Linux | Unknown |
| Web client | Yes cross-checked |
| Phone access: Native iOS | Unknown |
| Phone access: Native Android | Unknown |
| Phone access: Phone browser | Unknown |
| CLI | Yes cross-checked |
| Coding agents: Claude Code | No |
| Coding agents: Codex | No |
| Coding agents: Cursor Agent | No |
| Coding agents: Gemini CLI | No |
| Coding agents: OpenCode | No |
| Coding agents: Pi | No |
| Coding agents: Grok | No |
| Coding agents: Aider | No |
| Coding agents: Antigravity | No |
| Use my subscription | No |
| Where agents run: On your computer | No |
| Where agents run: On your own server | No |
| Where agents run: In the vendor's cloud | Yes |
| Workspace isolation: Git worktree | Unknown |
| Workspace isolation: Container | Unknown |
| Workspace isolation: VM or microVM | Yes cross-checked |
| Parallel runs | Yes cross-checked |
| Coordinator | Unknown |
| Native issue tracking | Unknown |
| Unattended triggers | Yes cross-checked |
| Shared prompting | Unknown |
| Team roles | Unknown |
| SSO | Unknown |
| Pull request workflow | Yes cross-checked |
| Review interface | Yes cross-checked |
| Product license: Apache-2.0 | No. Custom terms |
| Product license: MIT | No. Custom terms |
| Product license: GPL-3.0 | No. Custom terms |
| Product license: GPL-3.0-or-later | No. Custom terms |
| Product license: AGPL-3.0 | No. Custom terms |
| Product license: AGPL-3.0-or-later | No. Custom terms |
| Product license: Elastic License 2.0 | No. Custom terms |
| Product license: Custom terms | Yes. Custom terms |
| Product license: Proprietary | No. Custom terms |
| Self-hosting | Unknown |
| Telemetry opt-out | Unknown |
| Free access | Yes cross-checked |
| Starting price: Free | Yes. Free cross-checked |
| Starting price: Up to $20/month | No. Free cross-checked |
| Starting price: $21–40/month | No. Free cross-checked |
| Starting price: $41–100/month | No. Free cross-checked |
| Starting price: Over $100/month | No. Free cross-checked |
| Starting price: Contact for pricing | No. Free cross-checked |
| Pricing model: Free, no paid plan | No |
| Pricing model: Free plan | Yes cross-checked |
| Pricing model: Subscription | Yes |
| Pricing model: Per seat | No |
| Pricing model: Usage-based | No |
| Pricing model: Per machine or compute | No |
| Pricing model: Bring your own key | No |
| Pricing model: One-time purchase | No |
| Paid plans from: No paid plan | Unknown |
| Paid plans from: $10 or less/month | Unknown |
| Paid plans from: $11–20/month | Unknown |
| Paid plans from: $21–40/month | Unknown |
| Paid plans from: $41–100/month | Unknown |
| Paid plans from: Over $100/month | Unknown |
| Paid plans from: Contact sales | Unknown |
| Lifecycle status: Active | No. Sunsetting cross-checked |
| Lifecycle status: Sunsetting | Yes. Sunsetting cross-checked |
| Keeps going with laptop closed | Yes |
| Open-source license | No. Custom terms |
| Any desktop app | Unknown |
| Paid plan up to $20/month | Unknown |
| Paid plan up to $40/month | Unknown |
| Any phone client | Unknown |
Filter receipts
Web client: Yes cross-checked
Web client
Typed value: Yes.
Jules has a browser client; mobile action parity was not established. Jules Tools is an npm-installed remote-session CLI with a TUI dashboard. Further scoped facts are recorded in the atomic answers.
- Browser: Jules has a browser client; mobile action parity was not established.
- Notifications: Browser notifications can signal completion or need for input.
- Client access: first-party sources in this pass did not establish desktop_os, mobile_apps, mobile_browser, editor_extensions, task_actions, cross_device_continuity. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: Jules uses Google identity, authorized GitHub repositories, a cloud VM and AGENTS.md. Shutdown dates supersede the generic onboarding guide.
CLI: Yes cross-checked
CLI
Typed value: Yes.
Jules has a browser client; mobile action parity was not established. Jules Tools is an npm-installed remote-session CLI with a TUI dashboard. Further scoped facts are recorded in the atomic answers.
- Cli: Jules Tools is an npm-installed remote-session CLI with a TUI dashboard.
- Client access: first-party sources in this pass did not establish desktop_os, mobile_apps, mobile_browser, editor_extensions, task_actions, cross_device_continuity. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: Jules Tools logs into Google, lists/creates remote sessions and pulls results; it does not run the coding worker locally.
Coding agents: Claude Code: No
Coding agents: Claude Code
Typed value: No.
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Model providers: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Coding agents: Codex: No
Coding agents: Codex
Typed value: No.
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Model providers: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Coding agents: Cursor Agent: No
Coding agents: Cursor Agent
Typed value: No.
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Model providers: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Coding agents: Gemini CLI: No
Coding agents: Gemini CLI
Typed value: No.
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Model providers: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Coding agents: OpenCode: No
Coding agents: OpenCode
Typed value: No.
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Model providers: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Coding agents: Pi: No
Coding agents: Pi
Typed value: No.
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Model providers: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Coding agents: Grok: No
Coding agents: Grok
Typed value: No.
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Model providers: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Coding agents: Aider: No
Coding agents: Aider
Typed value: No.
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Model providers: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Coding agents: Antigravity: No
Coding agents: Antigravity
Typed value: No.
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Model providers: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Use my subscription: No
Use my subscription
Typed value: No.
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. Google account eligibility controls Jules access and paid upgrades. Paid plan upgrades require an individual Gmail account; Workspace/business upgrades are not established.
- Agent subscriptions: 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.
- Vendor account requirement: Google account eligibility controls Jules access and paid upgrades.
- Provider restrictions: Paid plan upgrades require an individual Gmail account; Workspace/business upgrades are not established.
- Unknown after the targeted first-party documentation, release and repository pass: api_accounts, vendor_credits, local_models, account_switching. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Where agents run: On your computer: No
Where agents run: On your computer
Typed value: No.
Tasks run in cloud-based VMs, separate from the browser client. 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. 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.
- Local: Jules Tools is a remote-session client; the coding worker executes in Google cloud VMs.
- Byo remote: The published worker architecture is Google-hosted cloud VMs, not user-operated execution servers.
- 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.
-
Jules Tools remote-session architecture
Finding: 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.
Where agents run: On your own server: No
Where agents run: On your own server
Typed value: No.
Tasks run in cloud-based VMs, separate from the browser client. 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. 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.
- Local: Jules Tools is a remote-session client; the coding worker executes in Google cloud VMs.
- Byo remote: The published worker architecture is Google-hosted cloud VMs, not user-operated execution servers.
- 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.
-
Jules Tools remote-session architecture
Finding: 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.
Where agents run: In the vendor's cloud: Yes
Where agents run: In the vendor's cloud
Typed value: Yes.
Tasks run in cloud-based VMs, separate from the browser client. 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. 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.
- Managed cloud: Tasks run in cloud-based VMs, separate from the browser client.
- 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.
-
Finding: Cloud tasks continue after leaving the app; private repository content is excluded from model training according to the FAQ.
Workspace isolation: VM or microVM: Yes cross-checked
Workspace isolation: VM or microVM
Typed value: Yes.
Each task runs in its own short-lived VM; no adversarial isolation test was run.
- Vm: Each task runs in its own short-lived VM; no adversarial isolation test was run.
- Workspace and process isolation: first-party sources in this pass did not establish checkout, branch, worktree, container, os_sandbox, filesystem, process, network, secrets, code_separation, security_boundary. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: Every task uses an Ubuntu VM with developer tools; successful setup scripts can be snapshotted for later tasks.
Parallel runs: Yes cross-checked
Parallel runs
Typed value: Yes.
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.
- Quotas: 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.
- Parallel work: first-party sources in this pass did not establish concurrent_sessions, concurrent_tasks, observed_concurrency, status_visibility. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Unattended triggers: Yes cross-checked
Unattended triggers
Typed value: Yes.
The dashboard supports scheduled recurring tasks with frequency and cadence. Recurring tasks can be edited, paused and resumed from their menu, according to the January 26 release. The scheduled task runs in the Jules cloud service; wind-down limits apply.
- Schedules: The dashboard supports scheduled recurring tasks with frequency and cadence.
- Scheduler location: The scheduled task runs in the Jules cloud service; wind-down limits apply.
- Unknown after the targeted first-party documentation, release and repository pass: events, completion_conditions, overlaps, retries, client_independence. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Jules has cloud recurring tasks configured with frequency and cadence; edit behavior has later changelog updates and is not inferred from this older guide.
Pull request workflow: Yes cross-checked
Pull request workflow
Typed value: Yes.
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.
- Pull requests: Publish branch and Publish PR push results to GitHub; PR creation is separate from merging.
- Unknown after the targeted first-party documentation, release and repository pass: branches, worktrees, comments, rebase, conflicts, product_state. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Jules shows changed-file diffs, accepts feedback and can publish a branch or PR after the user action.
Review interface: Yes cross-checked
Review interface
Typed value: Yes.
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.
- Diffs: The feed includes mini diffs and a full changed-file diff editor.
- Unknown after the targeted first-party documentation, release and repository pass: documents, recordings, previews, reviewer_outputs, gallery, task_links, revision_links, persistence, child_findings, prompt_leakage. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Jules shows changed-file diffs, accepts feedback and can publish a branch or PR after the user action.
Product license: Apache-2.0: No. Custom terms
Product license: Apache-2.0
Typed value: No. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
Product license: MIT: No. Custom terms
Product license: MIT
Typed value: No. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
Product license: GPL-3.0: No. Custom terms
Product license: GPL-3.0
Typed value: No. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
Product license: GPL-3.0-or-later: No. Custom terms
Product license: GPL-3.0-or-later
Typed value: No. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
Product license: AGPL-3.0: No. Custom terms
Product license: AGPL-3.0
Typed value: No. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
Product license: AGPL-3.0-or-later: No. Custom terms
Product license: AGPL-3.0-or-later
Typed value: No. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
Product license: Elastic License 2.0: No. Custom terms
Product license: Elastic License 2.0
Typed value: No. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
Product license: Custom terms: Yes. Custom terms
Product license: Custom terms
Typed value: Yes. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
Product license: Proprietary: No. Custom terms
Product license: Proprietary
Typed value: No. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
Free access: Yes cross-checked
Free access
Typed value: Yes.
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.
- Ongoing free: Jules documents a recurring plan available without cost; service turndown restricts the remaining availability window.
- Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Starting price: Free: Yes. Free cross-checked
Starting price: Free
Typed value: Yes. Free.
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.
- Ongoing free: Jules documents a recurring plan available without cost; service turndown restricts the remaining availability window.
- Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Starting price: Up to $20/month: No. Free cross-checked
Starting price: Up to $20/month
Typed value: No. Free.
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.
- Ongoing free: Jules documents a recurring plan available without cost; service turndown restricts the remaining availability window.
- Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Starting price: $21–40/month: No. Free cross-checked
Starting price: $21–40/month
Typed value: No. Free.
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.
- Ongoing free: Jules documents a recurring plan available without cost; service turndown restricts the remaining availability window.
- Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Starting price: $41–100/month: No. Free cross-checked
Starting price: $41–100/month
Typed value: No. Free.
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.
- Ongoing free: Jules documents a recurring plan available without cost; service turndown restricts the remaining availability window.
- Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Starting price: Over $100/month: No. Free cross-checked
Starting price: Over $100/month
Typed value: No. Free.
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.
- Ongoing free: Jules documents a recurring plan available without cost; service turndown restricts the remaining availability window.
- Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Starting price: Contact for pricing: No. Free cross-checked
Starting price: Contact for pricing
Typed value: No. Free.
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.
- Ongoing free: Jules documents a recurring plan available without cost; service turndown restricts the remaining availability window.
- Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Pricing model: Free, no paid plan: No
Pricing model: Free, no paid plan
Typed value: No.
Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Included usage: Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Price and included usage: first-party sources in this pass did not establish currency, interval, seats, seat_minimum, workspace_fees, credits, trial, overages, taxes, model_cost, compute_cost. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Pricing model: Free plan: Yes cross-checked
Pricing model: Free plan
Typed value: Yes.
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.
- Usage caps: Free allows 15 tasks per rolling 24 hours and three concurrent tasks.
- Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
Pricing model: Subscription: Yes
Pricing model: Subscription
Typed value: Yes.
Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Included usage: Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Price and included usage: first-party sources in this pass did not establish currency, interval, seats, seat_minimum, workspace_fees, credits, trial, overages, taxes, model_cost, compute_cost. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Pricing model: Per seat: No
Pricing model: Per seat
Typed value: No.
Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Included usage: Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Price and included usage: first-party sources in this pass did not establish currency, interval, seats, seat_minimum, workspace_fees, credits, trial, overages, taxes, model_cost, compute_cost. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Pricing model: Usage-based: No
Pricing model: Usage-based
Typed value: No.
Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Included usage: Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Price and included usage: first-party sources in this pass did not establish currency, interval, seats, seat_minimum, workspace_fees, credits, trial, overages, taxes, model_cost, compute_cost. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Pricing model: Per machine or compute: No
Pricing model: Per machine or compute
Typed value: No.
Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Included usage: Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Price and included usage: first-party sources in this pass did not establish currency, interval, seats, seat_minimum, workspace_fees, credits, trial, overages, taxes, model_cost, compute_cost. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Pricing model: Bring your own key: No
Pricing model: Bring your own key
Typed value: No.
Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Included usage: Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Price and included usage: first-party sources in this pass did not establish currency, interval, seats, seat_minimum, workspace_fees, credits, trial, overages, taxes, model_cost, compute_cost. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Pricing model: One-time purchase: No
Pricing model: One-time purchase
Typed value: No.
Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Included usage: Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Price and included usage: first-party sources in this pass did not establish currency, interval, seats, seat_minimum, workspace_fees, credits, trial, overages, taxes, model_cost, compute_cost. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Lifecycle status: Active: No. Sunsetting cross-checked
Lifecycle status: Active
Typed value: No. Sunsetting.
-
Finding: Google announces read-only after November 11 and wind-down December 31, 2026; configuration and full session history can be exported locally.
Plan not specified. Surface and scope: Google-hosted Jules coding service and sessions. Google announced Jules will become read-only after November 11, 2026 and wind down December 31, 2026. The notice offers an export of configuration and session history; code, branches and PRs remain on GitHub.
Lifecycle status: Sunsetting: Yes. Sunsetting cross-checked
Lifecycle status: Sunsetting
Typed value: Yes. Sunsetting.
-
Finding: Google announces read-only after November 11 and wind-down December 31, 2026; configuration and full session history can be exported locally.
Plan not specified. Surface and scope: Google-hosted Jules coding service and sessions. Google announced Jules will become read-only after November 11, 2026 and wind down December 31, 2026. The notice offers an export of configuration and session history; code, branches and PRs remain on GitHub.
Keeps going with laptop closed: Yes
Keeps going with laptop closed
Typed value: Yes.
Tasks run in cloud-based VMs, separate from the browser client. 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. 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.
- Client disconnect: Jules explicitly lets users leave the app after submitting a task; it continues autonomously.
- Other device continuation: Notifications report completion or plan readiness; cross-device task takeover was not established.
- 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.
-
Finding: 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.
Open-source license: No. Custom terms
Open-source license
Typed value: No. Custom terms.
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.
- Server license: The hosted Jules application is offered under the vendor-authored Google Terms linked from its homepage.
- 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.
-
Google Terms linked from Jules
Finding: 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.
All public findings
Findings may summarize a source. They are not presented as verbatim statements.
jules:ACC-01: Jules has a browser client; mobile action parity was not established. Jules Tools is an npm-installed remote-session CLI with a TUI dashboard. Further scoped facts are recorded in the atomic answers. cross-checked
jules:ACC-01
Jules has a browser client; mobile action parity was not established. Jules Tools is an npm-installed remote-session CLI with a TUI dashboard. Further scoped facts are recorded in the atomic answers.
- Client access: first-party sources in this pass did not establish desktop_os, mobile_apps, mobile_browser, editor_extensions, task_actions, cross_device_continuity. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: Jules uses Google identity, authorized GitHub repositories, a cloud VM and AGENTS.md. Shutdown dates supersede the generic onboarding guide.
-
Finding: Jules Tools logs into Google, lists/creates remote sessions and pulls results; it does not run the coding worker locally.
jules:ACC-02: Jules documents Gemini model access across its plans; separate external coding harness support is not established.
jules:ACC-02
Jules documents Gemini model access across its plans; separate external coding harness support is not established.
- Unknown after the targeted first-party documentation, release and repository pass: harnesses, custom_adapters, session_integration, mixed_harness_operation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
jules:ACC-03: 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. Google account eligibility controls Jules access and paid upgrades. Paid plan upgrades require an individual Gmail account; Workspace/business upgrades are not established.
jules:ACC-03
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. Google account eligibility controls Jules access and paid upgrades. Paid plan upgrades require an individual Gmail account; Workspace/business upgrades are not established.
- Unknown after the targeted first-party documentation, release and repository pass: api_accounts, vendor_credits, local_models, account_switching. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: 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.
jules:ACC-04: 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. cross-checked
jules:ACC-04
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.
- Unknown after the targeted first-party documentation, release and repository pass: first_task_setup, local_git_without_remote, prerequisite_guidance, byo_vps_onboarding. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Jules uses Google identity, authorized GitHub repositories, a cloud VM and AGENTS.md. Shutdown dates supersede the generic onboarding guide.
-
Repoless, outputs and activity filters
Finding: 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.
jules:ACC-05: 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. cross-checked
jules:ACC-05
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.
- Unknown after the targeted first-party documentation, release and repository pass: sdk, mcp_server, webhooks. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: The alpha REST API exposes sources, sessions and activities using API keys; stability is explicitly experimental.
-
Finding: Jules Tools logs into Google, lists/creates remote sessions and pulls results; it does not run the coding worker locally.
-
Finding: 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.
jules:PLAN-01: Applying the jules label to a GitHub issue starts work and returns a PR link; GitHub remains the issue system. cross-checked
jules:PLAN-01
Applying the jules label to a GitHub issue starts work and returns a PR link; GitHub remains the issue system.
- Intake and external tracker relationship: first-party sources in this pass did not establish local_creation, prompt_intake, external_import, authoritative_tracker, stable_ids, sync, supported_edits, external_roundtrips. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
jules:PLAN-02: 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. cross-checked
jules:PLAN-02
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.
- Unknown after the targeted first-party documentation, release and repository pass: acceptance_criteria, revisions, restart_persistence. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Reviewing plans & giving feedback
Finding: Jules presents a step plan that can be revised, but the guide says it eventually auto-approves after navigation away.
-
Finding: 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.
jules:PLAN-04: 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.
jules:PLAN-04
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.
- Unknown after the targeted first-party documentation, release and repository pass: skills, project_docs, scope, provenance, correction, deletion, freshness, takeover_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Jules uses Google identity, authorized GitHub repositories, a cloud VM and AGENTS.md. Shutdown dates supersede the generic onboarding guide.
-
Finding: 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:PLAN-05: Task creation accepts PNG/JPEG images totaling under 5 MB; this guide excludes follow-up image attachments. cross-checked
jules:PLAN-05
Task creation accepts PNG/JPEG images totaling under 5 MB; this guide excludes follow-up image attachments.
- Architecture and API awareness: first-party sources in this pass did not establish code_search, indexing, external_knowledge, freshness, access_scope, api_retrieval, citations, conflict_detection, review_enforcement. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
jules:PLAN-08: 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. cross-checked
jules:PLAN-08
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.
- 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.
-
Finding: 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.
jules:COORD-01: 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. cross-checked
jules:COORD-01
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.
- Parallel work: first-party sources in this pass did not establish concurrent_sessions, concurrent_tasks, observed_concurrency, status_visibility. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
jules:COORD-04: The dashboard supports scheduled recurring tasks with frequency and cadence. Recurring tasks can be edited, paused and resumed from their menu, according to the January 26 release. The scheduled task runs in the Jules cloud service; wind-down limits apply. cross-checked
jules:COORD-04
The dashboard supports scheduled recurring tasks with frequency and cadence. Recurring tasks can be edited, paused and resumed from their menu, according to the January 26 release. The scheduled task runs in the Jules cloud service; wind-down limits apply.
- Unknown after the targeted first-party documentation, release and repository pass: events, completion_conditions, overlaps, retries, client_independence. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Cloud tasks continue after leaving the app; private repository content is excluded from model training according to the FAQ.
-
Finding: Jules has cloud recurring tasks configured with frequency and cadence; edit behavior has later changelog updates and is not inferred from this older guide.
-
Finding: The dated release adds schedule editing, pause and resume without deleting and recreating the task; the undated schedule guide still says editing is unavailable.
jules:COORD-05: 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. cross-checked
jules:COORD-05
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.
- Unknown after the targeted first-party documentation, release and repository pass: stop, resume, notifications, pending_decisions, escalation, chat_terminal_parity, retained_history. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
-
Finding: 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.
jules:RUN-01: Tasks run in cloud-based VMs, separate from the browser client. 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. 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:RUN-01
Tasks run in cloud-based VMs, separate from the browser client. 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. 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.
- 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.
-
Finding: Cloud tasks continue after leaving the app; private repository content is excluded from model training according to the FAQ.
-
Finding: 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.
-
Jules Tools remote-session architecture
Finding: 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:RUN-02: Each task runs in its own short-lived VM; no adversarial isolation test was run. cross-checked
jules:RUN-02
Each task runs in its own short-lived VM; no adversarial isolation test was run.
- Workspace and process isolation: first-party sources in this pass did not establish checkout, branch, worktree, container, os_sandbox, filesystem, process, network, secrets, code_separation, security_boundary. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: Every task uses an Ubuntu VM with developer tools; successful setup scripts can be snapshotted for later tasks.
jules:RUN-03: Immutable API activities can be used to reconstruct the session’s history; this does not prove process recovery. cross-checked
jules:RUN-03
Immutable API activities can be used to reconstruct the session’s history; this does not prove process recovery.
- Unknown after the targeted first-party documentation, release and repository pass: client_disconnect, worker_crash, service_restart, expiry, transcript_reload, process_reconnect, task_resume, context_loss, duplicate_actions, manual_repair, multi_day_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Repoless, outputs and activity filters
Finding: 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.
jules:RUN-04: 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. Future tasks can reuse a successful prepared environment snapshot; exact invalidation behavior is not established.
jules:RUN-04
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. Future tasks can reuse a successful prepared environment snapshot; exact invalidation behavior is not established.
- Unknown after the targeted first-party documentation, release and repository pass: ports, secrets, collisions, remote_setup, automatic_repair. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Every task uses an Ubuntu VM with developer tools; successful setup scripts can be snapshotted for later tasks.
-
Finding: Cloud tasks continue after leaving the app; private repository content is excluded from model training according to the FAQ.
-
Finding: 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.
-
Finding: 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:RUN-05: 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. cross-checked
jules:RUN-05
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.
- Unknown after the targeted first-party documentation, release and repository pass: time_limits, turn_limits, token_limits, spend_limits, timeouts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
-
Finding: 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.
-
Finding: 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.
jules:RUN-06: 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. cross-checked
jules:RUN-06
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.
- 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.
-
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
-
Finding: Jules exposes activity/errors, per-file and expanded diffs, real-time feedback, downloadable changes and a completion summary with runtime, files, lines and branch/commit details. Publish branch/PR controls export changes.
-
Finding: 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.
jules:RUN-08: 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. cross-checked
jules:RUN-08
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.
- 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.
-
Finding: 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.
jules:TEAM-03: The guide says an unattended plan eventually auto-approves on a timer; plan review is not an indefinite authorization gate. cross-checked
jules:TEAM-03
The guide says an unattended plan eventually auto-approves on a timer; plan review is not an indefinite authorization gate.
- Approvals and temporary access: first-party sources in this pass did not establish command, tool, network, secret, delivery, approver_identity, lifetime, allow, deny, revoke, tunnels, safer_modes, enforcement. No two-account permission, simultaneous steering, revocation or colleague-takeover fixture was run. Sharing and presence do not establish co-prompting.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Reviewing plans & giving feedback
Finding: Jules presents a step plan that can be revised, but the guide says it eventually auto-approves after navigation away.
jules:TEAM-04: 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. cross-checked
jules:TEAM-04
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.
- Unknown after the targeted first-party documentation, release and repository pass: approvals, edits, discussion, decisions, cross_user_persistence, cross_session_persistence, retention. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Repoless, outputs and activity filters
Finding: 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.
jules:TEAM-05: 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. cross-checked
jules:TEAM-05
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.
- 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.
-
Finding: Jules shows changed-file diffs, accepts feedback and can publish a branch or PR after the user action.
-
Finding: Jules exposes activity/errors, per-file and expanded diffs, real-time feedback, downloadable changes and a completion summary with runtime, files, lines and branch/commit details. Publish branch/PR controls export changes.
jules:SHIP-01: 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. cross-checked
jules:SHIP-01
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.
- Unknown after the targeted first-party documentation, release and repository pass: documents, recordings, previews, reviewer_outputs, gallery, task_links, revision_links, persistence, child_findings, prompt_leakage. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Jules shows changed-file diffs, accepts feedback and can publish a branch or PR after the user action.
-
Finding: Jules can render and verify a frontend, returning a screenshot with the code changes. The base image includes Playwright.
jules:SHIP-02: Setup scripts can run tests before snapshotting. Setup scripts can include linters. CI Fixer responds to GitHub Actions failures on Jules-created PRs. 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. cross-checked
jules:SHIP-02
Setup scripts can run tests before snapshotting. Setup scripts can include linters. CI Fixer responds to GitHub Actions failures on Jules-created PRs. 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.
- Unknown after the targeted first-party documentation, release and repository pass: types, independent_review, spec_checks, required_checks, requirement_conflicts, enforced_policy. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Every task uses an Ubuntu VM with developer tools; successful setup scripts can be snapshotted for later tasks.
-
Finding: Repository setup scripts install dependencies and run discrete checks. Successful Run and Snapshot captures the environment for future tasks, including preinstalled runtimes and tools.
-
Finding: Jules receives failed GitHub Actions checks on its own PRs, fixes and resubmits. User-level settings choose Jules-only, coauthored or user-only commits.
jules:SHIP-03: 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. cross-checked
jules:SHIP-03
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.
- Unknown after the targeted first-party documentation, release and repository pass: branches, worktrees, comments, rebase, conflicts, product_state. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Jules shows changed-file diffs, accepts feedback and can publish a branch or PR after the user action.
-
Finding: Jules receives failed GitHub Actions checks on its own PRs, fixes and resubmits. User-level settings choose Jules-only, coauthored or user-only commits.
jules:SHIP-05: 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. cross-checked
jules:SHIP-05
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.
- 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.
-
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
-
Finding: Jules exposes activity/errors, per-file and expanded diffs, real-time feedback, downloadable changes and a completion summary with runtime, files, lines and branch/commit details. Publish branch/PR controls export changes.
jules:OWN-01: 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.
jules:OWN-01
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 scoped first-party source pass does not establish client_license, hosted_extensions, source_visibility, source_revision, hosted_parity. No hands-on scenario was run.
-
Google Terms linked from Jules
Finding: 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.
jules:OWN-02: The diff editor has download/copy controls for generated changes. REST changed-file outputs are Git patches. cross-checked
jules:OWN-02
The diff editor has download/copy controls for generated changes. REST changed-file outputs are Git patches.
- Unknown after the targeted first-party documentation, release and repository pass: self_hosting, vendor_dependencies, import, cancellation, account_independence, history_portability. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: Google announces read-only after November 11 and wind-down December 31, 2026; configuration and full session history can be exported locally.
-
Finding: Jules exposes activity/errors, per-file and expanded diffs, real-time feedback, downloadable changes and a completion summary with runtime, files, lines and branch/commit details. Publish branch/PR controls export changes.
-
Repoless, outputs and activity filters
Finding: 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.
jules:OWN-03: Jules explicitly does not train models on private repository content. cross-checked
jules:OWN-03
Jules explicitly does not train models on private repository content.
- Unknown after the targeted first-party documentation, release and repository pass: code_data, prompts, credentials, 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.
-
Finding: Cloud tasks continue after leaving the app; private repository content is excluded from model training according to the FAQ.
-
Finding: 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.
jules:OWN-04: Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
jules:OWN-04
Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.
- Price and included usage: first-party sources in this pass did not establish currency, interval, seats, seat_minimum, workspace_fees, credits, trial, overages, taxes, model_cost, compute_cost. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
jules:OWN-06: Google's 29 October notice says sessions can continue until November 11, then Jules becomes read-only until wind-down December 31, 2026. cross-checked
jules:OWN-06
Google's 29 October notice says sessions can continue until November 11, then Jules becomes read-only until wind-down December 31, 2026.
- Availability and support: first-party sources in this pass did not establish release_stage, access_restrictions, support, response_commitments, release_activity, status_history, export_options. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
- Jules becomes read-only after November 11 and winds down December 31, 2026; generic guides do not override this notice.
-
Finding: Google announces read-only after November 11 and wind-down December 31, 2026; configuration and full session history can be exported locally.
jules:OWN-08: 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. cross-checked
jules:OWN-08
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.
- Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
-
Finding: 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.
-
Finding: 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.
jules:OWN-09: Plan task allowances are 15/100/300 daily and 3/15/60 concurrent. cross-checked
jules:OWN-09
Plan task allowances are 15/100/300 daily and 3/15/60 concurrent.
- Unknown after the targeted first-party documentation, release and repository pass: units, 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.
-
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
-
Finding: 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.