# Jules

Podium publishes this catalog and sells an agent development environment. Podium chooses the products, criteria, sources and wording, so treat these pages as vendor-authored research. Check important claims against the linked primary sources. The same evidence rules apply to Podium and its competitors, but they do not remove this conflict of interest.

Page: https://adecomparison.com/ade/jules/
Website: https://jules.google/
Research: covered

## Published lifecycle notice

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.

Scope: Google-hosted Jules coding service and sessions
Announcement date: 2026-10-29
Service end date: 2026-12-31
Continuation: The notice points to Google Antigravity as a product informed by Jules learnings; it does not promise automatic migration or continued Jules execution. GitHub code and PRs remain with their repositories.
Checked: 2026-11-07

Source: https://jules.google/docs/changelog/2026-10-29
Locator: 29 October 2026 notice; export description
Finding: Google announces read-only after November 11 and wind-down December 31, 2026; configuration and full session history can be exported locally.
Retrieved: 2026-11-07

Method: https://adecomparison.com/method/

Rank by must-haves met, then preferences, then name. Read each finding's checked date. Findings stay published after their scheduled recheck. Checks over six months old may be outdated.

## jules:ACC-01

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-11
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules Tools remote-session CLI; Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/
Locator: Login; Connect GitHub; first task; notifications
Finding: Jules uses Google identity, authorized GitHub repositories, a cloud VM and AGENTS.md. Shutdown dates supersede the generic onboarding guide.
Retrieved: 2026-11-07

Source: https://jules.google/docs/cli/reference.md
Locator: Remote commands; interactive dashboard
Finding: Jules Tools logs into Google, lists/creates remote sessions and pulls results; it does not run the coding worker locally.
Retrieved: 2026-11-07

## jules:ACC-02

Finding: Jules documents Gemini model access across its plans; separate external coding harness support is not established.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-14
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Jules web/cloud; Jules Tools remote-session CLI
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/usage-limits.md
Locator: Plan comparison; Availability
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.
Retrieved: 2026-11-07

## jules:ACC-03

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-14
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Jules web/cloud; Jules Tools remote-session CLI
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/usage-limits.md
Locator: Plan comparison; Availability
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.
Retrieved: 2026-11-07

## jules:ACC-04

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/
Locator: Login; Connect GitHub; first task; notifications
Finding: Jules uses Google identity, authorized GitHub repositories, a cloud VM and AGENTS.md. Shutdown dates supersede the generic onboarding guide.
Retrieved: 2026-11-07

Source: https://jules.google/docs/changelog/2026-01-26-4.md
Locator: Repoless; File outputs; Immutable activities
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.
Retrieved: 2026-11-07

## jules:ACC-05

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules Tools remote-session CLI; Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/api/reference.md
Locator: Alpha note; authentication; resources
Finding: The alpha REST API exposes sources, sessions and activities using API keys; stability is explicitly experimental.
Retrieved: 2026-11-07

Source: https://jules.google/docs/cli/reference.md
Locator: Remote commands; interactive dashboard
Finding: Jules Tools logs into Google, lists/creates remote sessions and pulls results; it does not run the coding worker locally.
Retrieved: 2026-11-07

Source: https://jules.google/docs/api/reference.md
Locator: Authentication; API concepts
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.
Retrieved: 2026-11-07

## jules:PLAN-01

Finding: Applying the jules label to a GitHub issue starts work and returns a PR link; GitHub remains the issue system.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-11
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/running-tasks.md
Locator: Visual context; feedback; pause; issue label
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
Retrieved: 2026-11-07

## jules:PLAN-02

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/review-plan.md
Locator: Reviewing the plan; feedback
Finding: Jules presents a step plan that can be revised, but the guide says it eventually auto-approves after navigation away.
Retrieved: 2026-11-07

Source: https://jules.google/docs/review-plan.md
Locator: Review and feedback
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.
Retrieved: 2026-11-07

## jules:PLAN-04

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/
Locator: Login; Connect GitHub; first task; notifications
Finding: Jules uses Google identity, authorized GitHub repositories, a cloud VM and AGENTS.md. Shutdown dates supersede the generic onboarding guide.
Retrieved: 2026-11-07

Source: https://jules.google/docs/changelog/2025-09-30.md
Locator: Memory
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.
Retrieved: 2026-11-07

## jules:PLAN-05

Finding: Task creation accepts PNG/JPEG images totaling under 5 MB; this guide excludes follow-up image attachments.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-11
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/running-tasks.md
Locator: Visual context; feedback; pause; issue label
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
Retrieved: 2026-11-07

## jules:PLAN-08

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Jules web/cloud; Jules Tools remote-session CLI
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/review-plan.md
Locator: Review and feedback
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.
Retrieved: 2026-11-07

## jules:COORD-01

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-11
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/usage-limits/
Locator: Plan comparison; FAQ
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Retrieved: 2026-11-07

## jules:COORD-04

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/faq.md
Locator: Leaving while working; training; setup scripts
Finding: Cloud tasks continue after leaving the app; private repository content is excluded from model training according to the FAQ.
Retrieved: 2026-11-07

Source: https://jules.google/docs/scheduled-tasks.md
Locator: Creating and managing scheduled tasks
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.
Retrieved: 2026-11-07

Source: https://jules.google/docs/changelog/2026-01-26-5.md
Locator: Edit, Pause and Resume
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.
Retrieved: 2026-11-07

## jules:COORD-05

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/running-tasks.md
Locator: Visual context; feedback; pause; issue label
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
Retrieved: 2026-11-07

Source: https://jules.google/docs/errors.md
Locator: Error reporting; Retry; Rerun
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.
Retrieved: 2026-11-07

## jules:RUN-01

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-14
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: 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

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.

Source: https://jules.google/docs/faq.md
Locator: Leaving while working; training; setup scripts
Finding: Cloud tasks continue after leaving the app; private repository content is excluded from model training according to the FAQ.
Retrieved: 2026-11-07

Source: https://jules.google/docs/faq.md
Locator: Leave while working; Failure handling; Training; Free 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.
Retrieved: 2026-11-07

Source: https://jules.google/docs/cli/reference.md
Locator: Introduction; authentication; remote commands
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.
Retrieved: 2026-11-13

## jules:RUN-02

Finding: Each task runs in its own short-lived VM; no adversarial isolation test was run.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-11
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/environment.md
Locator: Short-lived VM; setup validation; snapshots
Finding: Every task uses an Ubuntu VM with developer tools; successful setup scripts can be snapshotted for later tasks.
Retrieved: 2026-11-07

## jules:RUN-03

Finding: Immutable API activities can be used to reconstruct the session’s history; this does not prove process recovery.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Jules web/cloud; Jules Tools remote-session CLI
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/changelog/2026-01-26-4.md
Locator: Repoless; File outputs; Immutable activities
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.
Retrieved: 2026-11-07

## jules:RUN-04

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/environment.md
Locator: Short-lived VM; setup validation; snapshots
Finding: Every task uses an Ubuntu VM with developer tools; successful setup scripts can be snapshotted for later tasks.
Retrieved: 2026-11-07

Source: https://jules.google/docs/faq.md
Locator: Leaving while working; training; setup scripts
Finding: Cloud tasks continue after leaving the app; private repository content is excluded from model training according to the FAQ.
Retrieved: 2026-11-07

Source: https://jules.google/docs/faq.md
Locator: Leave while working; Failure handling; Training; Free 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.
Retrieved: 2026-11-07

Source: https://jules.google/docs/environment.md
Locator: Setup; Run and Snapshot; Tools
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.
Retrieved: 2026-11-07

## jules:RUN-05

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/usage-limits/
Locator: Plan comparison; FAQ
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Retrieved: 2026-11-07

Source: https://jules.google/docs/usage-limits.md
Locator: Plan comparison; Availability
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.
Retrieved: 2026-11-07

Source: https://jules.google/docs/errors.md
Locator: Error reporting; Retry; Rerun
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.
Retrieved: 2026-11-07

## jules:RUN-06

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/running-tasks.md
Locator: Visual context; feedback; pause; issue label
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
Retrieved: 2026-11-07

Source: https://jules.google/docs/code.md
Locator: Activity; Diffs; Feedback; Summary; Publishing
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.
Retrieved: 2026-11-07

Source: https://jules.google/docs/errors.md
Locator: Error reporting; Retry; Rerun
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.
Retrieved: 2026-11-07

## jules:RUN-08

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Jules web/cloud; Jules Tools remote-session CLI
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/usage-limits.md
Locator: Plan comparison; Availability
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.
Retrieved: 2026-11-07

## jules:TEAM-03

Finding: The guide says an unattended plan eventually auto-approves on a timer; plan review is not an indefinite authorization gate.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-11
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/review-plan.md
Locator: Reviewing the plan; feedback
Finding: Jules presents a step plan that can be revised, but the guide says it eventually auto-approves after navigation away.
Retrieved: 2026-11-07

## jules:TEAM-04

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Jules web/cloud; Jules Tools remote-session CLI
Version: Public sources checked 2026-11-07; no installed release 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.

Source: https://jules.google/docs/changelog/2026-01-26-4.md
Locator: Repoless; File outputs; Immutable activities
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.
Retrieved: 2026-11-07

## jules:TEAM-05

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/code.md
Locator: Activity feed; diffs; pushing to GitHub
Finding: Jules shows changed-file diffs, accepts feedback and can publish a branch or PR after the user action.
Retrieved: 2026-11-07

Source: https://jules.google/docs/code.md
Locator: Activity; Diffs; Feedback; Summary; Publishing
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.
Retrieved: 2026-11-07

## jules:SHIP-01

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/code.md
Locator: Activity feed; diffs; pushing to GitHub
Finding: Jules shows changed-file diffs, accepts feedback and can publish a branch or PR after the user action.
Retrieved: 2026-11-07

Source: https://jules.google/docs/changelog/2025-08-07.md
Locator: Screenshots; Playwright
Finding: Jules can render and verify a frontend, returning a screenshot with the code changes. The base image includes Playwright.
Retrieved: 2026-11-07

## jules:SHIP-02

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/environment.md
Locator: Short-lived VM; setup validation; snapshots
Finding: Every task uses an Ubuntu VM with developer tools; successful setup scripts can be snapshotted for later tasks.
Retrieved: 2026-11-07

Source: https://jules.google/docs/environment.md
Locator: Setup; Run and Snapshot; Tools
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.
Retrieved: 2026-11-07

Source: https://jules.google/docs/changelog/2026-02-19.md
Locator: CI Fixer; Commit Authoring
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.
Retrieved: 2026-11-07

## jules:SHIP-03

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/code.md
Locator: Activity feed; diffs; pushing to GitHub
Finding: Jules shows changed-file diffs, accepts feedback and can publish a branch or PR after the user action.
Retrieved: 2026-11-07

Source: https://jules.google/docs/changelog/2026-02-19.md
Locator: CI Fixer; Commit Authoring
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.
Retrieved: 2026-11-07

## jules:SHIP-05

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/running-tasks.md
Locator: Visual context; feedback; pause; issue label
Finding: Tasks accept initial images, in-run feedback and pause controls. A jules issue label starts work through the GitHub integration.
Retrieved: 2026-11-07

Source: https://jules.google/docs/code.md
Locator: Activity; Diffs; Feedback; Summary; Publishing
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.
Retrieved: 2026-11-07

## jules:OWN-01

Finding: 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.

Verification: sourced
Checked: 2026-11-13
Scheduled recheck: 2027-05-12
Plan: Not specified
Surface: Jules web/cloud; Jules Tools remote-session CLI
Version: 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

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.

Source: https://policies.google.com/terms
Locator: Jules homepage Terms of Service link; Google service/software permissions and intellectual property
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.
Retrieved: 2026-11-13

## jules:OWN-02

Finding: The diff editor has download/copy controls for generated changes. REST changed-file outputs are Git patches.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules Tools remote-session CLI; Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/changelog/2026-10-29
Locator: 29 October 2026 notice; export description
Finding: Google announces read-only after November 11 and wind-down December 31, 2026; configuration and full session history can be exported locally.
Retrieved: 2026-11-07

Source: https://jules.google/docs/code.md
Locator: Activity; Diffs; Feedback; Summary; Publishing
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.
Retrieved: 2026-11-07

Source: https://jules.google/docs/changelog/2026-01-26-4.md
Locator: Repoless; File outputs; Immutable activities
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.
Retrieved: 2026-11-07

## jules:OWN-03

Finding: Jules explicitly does not train models on private repository content.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/faq.md
Locator: Leaving while working; training; setup scripts
Finding: Cloud tasks continue after leaving the app; private repository content is excluded from model training according to the FAQ.
Retrieved: 2026-11-07

Source: https://jules.google/docs/faq.md
Locator: Leave while working; Failure handling; Training; Free 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.
Retrieved: 2026-11-07

## jules:OWN-04

Finding: Paid quotas are accessed through Google AI Pro or Ultra; currency and regional subscription prices were not established here.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-14
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/usage-limits/
Locator: Plan comparison; FAQ
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Retrieved: 2026-11-07

## jules:OWN-06

Finding: Google's 29 October notice says sessions can continue until November 11, then Jules becomes read-only until wind-down December 31, 2026.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-11
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules Tools remote-session CLI; Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/changelog/2026-10-29
Locator: 29 October 2026 notice; export description
Finding: Google announces read-only after November 11 and wind-down December 31, 2026; configuration and full session history can be exported locally.
Retrieved: 2026-11-07

## jules:OWN-08

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/usage-limits/
Locator: Plan comparison; FAQ
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Retrieved: 2026-11-07

Source: https://jules.google/docs/faq.md
Locator: Leave while working; Failure handling; Training; Free 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.
Retrieved: 2026-11-07

Source: https://jules.google/docs/usage-limits.md
Locator: Plan comparison; Availability
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.
Retrieved: 2026-11-07

## jules:OWN-09

Finding: Plan task allowances are 15/100/300 daily and 3/15/60 concurrent.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-10
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Jules web/cloud
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://jules.google/docs/usage-limits/
Locator: Plan comparison; FAQ
Finding: The published tiers list daily and concurrent task quotas; wind-down dates limit future evaluation access.
Retrieved: 2026-11-07

Source: https://jules.google/docs/usage-limits.md
Locator: Plan comparison; Availability
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.
Retrieved: 2026-11-07