Jules review

Jules is a hosted AI coding agent, not a library, local CLI or self-hosted server. You select a GitHub repository and branch, write a task prompt, and Jules fetches and clones the repository to a cloud VM. It develops a plan, makes code changes, presents a diff, and can create a pull request for you to review and merge.

That puts Jules alongside your repository workflow rather than inside your application at runtime. It targets delegated engineering work such as bug fixes, version bumps, tests and feature building. You can also assign a task directly from GitHub by adding the “jules” label to an issue. The output is a proposed code change in the repository, not a running service or an API response for your product. The practical boundary is review: Jules prepares changes, while a developer approves edits and merges the resulting PR.

The homepage describes a GitHub-centered workflow: choose a repository and branch, enter a detailed prompt, or assign an issue with the “jules” label. Jules clones the repository to a cloud VM, plans the work, shows a diff, and can open a pull request. That is the documented integration surface for developers working from the published product details.

The homepage does not present a REST API, webhooks, SDKs, supported programming languages or a CLI workflow. This matters if you want to trigger coding tasks from CI, an internal developer portal or another agent orchestrator rather than through GitHub. Confirm API and SDK support, authentication, event handling and language-specific setup in the vendor’s docs before designing that integration. The GitHub issue-label route is the clearest stated path for assigning work from an existing codebase; Jules still expects a human to review and merge the proposed change.

Jules has a free tier. The listed allowance is 15 tasks per rolling 24 hours and three concurrent tasks, with Gemini 2.5 Pro access. The homepage describes that allowance as 15 tasks per day. The account restriction is Individual Google Accounts only.

Jules in Pro lists 100 tasks per rolling 24 hours and 15 concurrent tasks, with access to newer models starting with Gemini 3 Pro. Jules in Ultra lists 300 tasks per rolling 24 hours and 60 concurrent tasks, plus priority access to newer models starting with Gemini 3 Pro. Both are also limited to Individual Google Accounts. Monthly and annual prices are not published; the pricing information says Pro and Ultra are included with their respective Google AI plans. No add-on or overage prices are listed, so exceeding a plan’s task allowance is a capacity question rather than a calculable usage bill from the published figures. Ask Google to confirm current plan prices, reset timing and what happens at the task cap before budgeting for a production team.

The published Jules materials do not publish a source-code license or describe an open-source distribution. They also do not describe a self-hosted deployment; the workflow runs repository work on a cloud VM. Treat Jules as a hosted service unless Google confirms otherwise, and ask about data handling, retention and any available export options before sending proprietary code.

The repository itself remains on GitHub, and Jules presents changes as a diff and pull request that can be reviewed and merged there. That keeps the code change in a familiar Git workflow, but does not establish that task history, plans or other Jules data can be exported. If you later move to another agent, the repository and merged code remain usable; portability of Jules-specific records and workflows is not published. Confirm those details, along with the applicable source license, before making Jules a dependency in internal tooling.

Plan around the published task and concurrency caps: the free tier lists 15 tasks per rolling 24 hours and three concurrent tasks; Pro lists 100 and 15; Ultra lists 300 and 60. The homepage frames these as daily task allowances. Confirm how tasks are counted, when limits reset and what happens when a cap is reached before using Jules for time-sensitive release work.

Jules works with a cloud VM and GitHub repository, so review repository permissions and the handling of source code before assigning sensitive work. The published materials do not state service-level commitments, security certifications, data-retention terms or an incident process; ask Google for those before making it part of a production workflow. Reddit reactions are positive but anecdotal: one r/LocalLLaMA poster said Jules handled substantial work autonomously, while a Jules community post said a new version was in development. Neither is evidence of reliability at scale. Keep human review and pull-request approval in the release path.