Jules review

Jules is a GitHub-focused AI coding assistant for work you can hand off, rather than a tool described here as an inline autocomplete. You give it a coding task tied to a repository and branch. It works in a cloud VM, makes code changes, and can return a plan and diff for review before creating a pull request.

The listed work includes bug fixes, dependency version updates such as a Next.js bump, tests, and feature building. That makes Jules a possible fit for discrete changes a developer can review, not a reason to stop reviewing code. The key switching question is whether you want another service in your GitHub workflow and whether its task limits suit your volume. Its pricing is hard to compare: the available plan information lists task and concurrency caps, but no monthly or annual dollar amounts.

Jules covers a useful range of delegated repository work without limiting its stated role to one narrow task type. The product information lists bug fixing, dependency updates, test work, and feature building. For teams—or individual developers—who already track changes through GitHub, the plan-and-diff step gives you something concrete to inspect before accepting the work.

Its workflow is also clear: assign a task against a repository and branch, let Jules work in a cloud VM, review the resulting diff, and have it create a pull request. That is a more reviewable handoff than accepting an unexplained code change. It does not remove the need for a developer to check the result, but the stated process keeps the change visible.

A user in one Reddit discussion said Jules handled substantial work with little intervention, while also noting that the model could be part of the reason. That is one user's impression, not evidence of consistent results. Still, it points to the appeal: offload a bounded coding task, then review what comes back.

The biggest gap for a buying decision is price. The available pricing information lists no monthly or annual dollar amount for Jules, Jules in Pro, or Jules in Ultra. It says Pro and Ultra are included with their respective Google AI plans, but without those subscription prices here, we cannot calculate Jules's cost or compare it cleanly with another coding assistant. Treat the price details as unconfirmed, not as a free upgrade.

The listed usage limits are specific: Jules has 15 tasks per rolling 24 hours and 3 concurrent tasks; Jules in Pro has 100 tasks and 15 concurrent tasks; Jules in Ultra has 300 tasks and 60 concurrent tasks. All three are listed for individual Google Accounts only. That rules out assuming these plans cover a team or organizational account. The free tier may be enough to assess a small amount of work, but the caps could constrain heavier use. Before switching, check the current Google AI plan price and confirm account eligibility; neither a higher cap nor an included plan tells you whether Jules fits your budget.

Jules has a free plan, but the available pricing data does not publish a monthly or annual price for any tier. The free Jules plan lists 15 tasks per rolling 24 hours, three concurrent tasks and Gemini 2.5 Pro access. Jules in Pro raises that to 100 tasks and 15 concurrent tasks; it is included with Google AI Pro. Jules in Ultra lists 300 tasks and 60 concurrent tasks, and is included with Google AI Ultra. The prices of those Google AI plans are not provided here, so we can’t calculate the cost of moving up or compare it with a standalone coding assistant.

The practical jump is capacity: Pro offers about 6.7 times the free plan’s daily task allowance, and Ultra triples Pro’s. Those are not price comparisons. The plans are for individual Google Accounts only, which rules out treating them as a published team offering. No add-ons are listed. Check the applicable Google AI plan price before committing; the Jules figures alone don’t tell you what you’ll pay.

Jules takes a task from a GitHub repository and branch, works in a cloud VM, then provides a plan and diff and can create a pull request. That makes the reviewable code change the clearest handoff described; the available details don’t specify a migration tool, bulk import, or data-export process. If you’re switching from another assistant, expect to provide tasks through GitHub rather than assume its history or settings transfer.

The product details don’t explain what happens to task history or other data if you leave, so treat portability beyond the code changes as unconfirmed. We also don’t have Reddit posts or comments in the published material to substantiate why users leave Jules. Before switching, check whether your Google account is eligible: the listed Jules plans are for individual Google Accounts only. For a team or a buyer who needs clear standalone pricing and support terms, the published details leave important questions unanswered.