AgentComparison
Google · product · coding agent (Google)

Jules

Google's background coding agent that turns GitHub tasks into pull requests.

Group: Coding agents

Jules is Google's asynchronous GitHub coding agent. In its web workflow, you select a repository and branch, describe a task, approve a plan, then review the changes and publish a pull request. Code runs in a cloud VM. The API also supports automated workflows, but its approval defaults differ from the web app.

Documentation researched, not testedChecked 22 October 2026Vendor documentation, not a test

The decision in plain English

Best for scoped repository maintenance, tests and documentation that you can review as a pull request. Start with a non-sensitive repository, limit the GitHub app to selected repos, and provide a working setup script. Web plans can be reviewed before code changes; API sessions automatically approve plans unless requirePlanApproval is true. Automatic PR creation is a separate API setting, not automatic merging.

Best fit

GitHub developers with a working project setup who want bounded bug fixes, dependency maintenance, documentation or tests returned for review while they work on something else.

Poor fit

Teams needing a confirmed Workspace paid upgrade path, repositories with embedded secrets, or workflows that cannot tolerate an internet-connected cloud VM. Not a substitute for testing and reviewing generated changes.

Documented capabilities

Vendor statements, not verified task outcomes.

  • Web plan approval, cloud VM changes and reviewed pull request workflow Source · checked 2026-10-22
  • Assign a task through a GitHub issue with a 'jules' label Source · checked 2026-10-22
  • API sessions with explicit plan-approval and automatic-PR settings Source · checked 2026-10-22
  • No-cost tier and Google AI Pro / Ultra task allowances Source · checked 2026-10-22

Permissions and human control

  • Connect the Google Labs Jules GitHub app to all or selected repositories. The FAQ explains changing this scope through GitHub Settings > Applications > Google Labs Jules > Configure. Refresh Jules after changing repository access.
  • The getting-started web workflow shows a plan to review and approve before code changes. Review the diff and tests before publishing or merging the resulting pull request.
  • API sessions automatically approve plans unless requirePlanApproval is true. automationMode=AUTO_CREATE_PR can create a pull request when changes are ready; the default does not automatically create one. These API controls do not authorize merging.

Documented controls do not prove that an agent always follows them.

Limits and open questions

  • Requires a Google sign-in and GitHub repository access; select only the repositories needed
  • Tasks are capped in a rolling 24-hour window: 15 / 100 / 300, with 3 / 15 / 60 concurrent tasks
  • Paid upgrades currently documented for individual @gmail.com accounts, not Workspace accounts; age 18+
  • API plans are automatically approved by default; set requirePlanApproval=true when approval is required
  • Cloud VM has internet access; setup scripts, dependencies and non-code files need security review
  • Vendor documentation only; AgentComparison has not tested task quality or reliability

Privacy and security

Re-verified 22 October 2026: Google's Jules FAQ states verbatim 'Jules does not train on private repository content... we do not use your private repositories to train models.' Each task runs in a fresh cloud VM that clones your repo with internet access; Google advises treating it like any shared compute surface - do not commit secrets to repos you connect, and review non-code files too. Repository access is manageable through the GitHub app connection. A linked page describes separate data use 'to improve Jules'; the training exclusion applies to private repo content. Vendor statements, not independently audited.

Feature-by-feature: what is documented and what is not

Official sources checked 22 October 2026. A documented feature is a vendor statement, not proof of success.

FeatureEvidence statusDetail and limit
Account and repositoryTwo connectionsSign in with Google, then connect the Jules GitHub app to selected repositories. Paid benefits currently require an individual @gmail.com account; users must be 18+. Source
Web plan reviewDocumented workflowGetting started shows Give me a plan, review and approve before code changes. This is not proof that every integration uses that gate. Source
API approvalAutomatic by defaultAPI plans are automatically approved unless requirePlanApproval is true. Explicit approval must be configured, not assumed from the web workflow. Source
Pull request automationSeparate choiceAUTO_CREATE_PR can create a PR when changes are ready. The default creates no PR automatically; neither setting is permission to merge. Source
Environment setupDiscrete commandsCloud VMs clone the repository and run setup. Long-lived dev servers/watch scripts are not supported in setup; root AGENTS.md supplies project context. Source
Network and dependenciesSecurity review neededVM has internet access. Review dependencies, shell commands and non-code files, and do not keep secrets in the repository. Source
Training scopePrivate-repo statementFAQ says private repository content is not used for training. It does not establish all prompt, feedback, public-repository or retention terms. Source
Task allowancesRolling limitsNo-cost/Pro/Ultra list 15/100/300 tasks per rolling 24 hours and 3/15/60 concurrent tasks. Paid local Google AI subscription prices remain unverified. Source

How to start with Jules narrowly

  1. Connect one non-sensitive GitHub repository using a Google account.
  2. Use a working discrete install/test setup and one clearly bounded task.
  3. Review the web plan; for API work explicitly set requirePlanApproval=true if required.
  4. Review the diff and test results before publishing or merging; check the task allowance separately.

Official product/setup source. These are documentation-based steps, not a hands-on setup test.

Common questions about Jules

What is Jules for?

GitHub developers with a working project setup who want bounded bug fixes, dependency maintenance, documentation or tests returned for review while they work on something else. The vendor describes it as: Jules is Google's asynchronous GitHub coding agent. In its web workflow, you select a repository and branch, describe a task, approve a plan, then review the changes and publish a pull request. Code runs in a cloud VM. The API also supports automated workflows, but its approval defaults differ from the web app.

Who should look elsewhere?

Teams needing a confirmed Workspace paid upgrade path, repositories with embedded secrets, or workflows that cannot tolerate an internet-connected cloud VM. Not a substitute for testing and reviewing generated changes.

How much does Jules cost?

Jules in Pro and Ultra are included in corresponding Google AI plans. No standalone Jules subscription price is listed in these docs; paid benefits currently require individual @gmail.com accounts. Exact local subscription price remains unknown.

What can it access and what needs my approval?

Connect the Google Labs Jules GitHub app to all or selected repositories. The FAQ explains changing this scope through GitHub Settings > Applications > Google Labs Jules > Configure. Refresh Jules after changing repository access. The getting-started web workflow shows a plan to review and approve before code changes. Review the diff and tests before publishing or merging the resulting pull request. API sessions automatically approve plans unless requirePlanApproval is true. automationMode=AUTO_CREATE_PR can create a pull request when changes are ready; the default does not automatically create one. These API controls do not authorize merging.

What happens to my data?

Re-verified 22 October 2026: Google's Jules FAQ states verbatim 'Jules does not train on private repository content... we do not use your private repositories to train models.' Each task runs in a fresh cloud VM that clones your repo with internet access; Google advises treating it like any shared compute surface - do not commit secrets to repos you connect, and review non-code files too. Repository access is manageable through the GitHub app connection. A linked page describes separate data use 'to improve Jules'; the training exclusion applies to private repo content. Vendor statements, not independently audited.

Has AgentComparison tested it?

No. This record is built from the vendor's own documentation, checked 2026-10-22. Vendor claims are attributed, not confirmed.

How to evaluate Jules yourself

  1. Pick one low-risk task that matches its documented capabilities: web plan approval, cloud vm changes and reviewed pull request workflow.
  2. Write the expected output and what counts as failure before you start.
  3. Connect the minimum access needed, and check approval settings first.
  4. Run it twice and compare, then review every action it took.
  5. Check cost after any free allowance. Unknown price is not free.

Related

Documented use cases: Software development and repository work.

Sources and history

Change history

Documentation overview expanded with current pricing/access sources. No hands-on results claimed.

Report a correction