Google Jitro Vs Jules: What's Actually Different

Google Jitro is the next version of Jules, and the differences between the two are bigger than a typical version bump would suggest. If you've been using Jules, this post tells you what's coming, what stays the same, what's new, and what it all means for your workflow.

The Quick Answer

Jules is task-based, async, and repository-connected. Jitro is goal-based, async, repository-connected, and adds a persistent workspace.

The biggest shift is from tasks to goals. Everything else is layered on top of that core architectural change.

What Jules Is Today

Jules is Google's existing AI coding agent. It connects to your repos and handles tasks like bug fixes, test writing, dependency updates, and refactors.

The execution model is async — you hand it a task, it works in the background, and it returns results when done. It's available on free and paid tiers (Google AI Pro, Ultra).

It's solid, but you're still telling it what to do, step by step.

What Jitro Adds

Three big upgrades that change the operational model.

1 — Goal-based workflow

Instead of "fix this bug", you say "reduce error rates in the checkout flow". Jitro figures out which files to change, what tests to add, and how to validate.

You set the destination. Jitro plans the route.

2 — Persistent workspace

Jules works task-by-task with limited memory. Jitro has a dedicated workspace that sees your project over time, tracks progress against goals, and maintains context across sessions.

This is closer to having an embedded engineer than a contract worker.

3 — Tool integration

Jitro connects to your existing tools through MCP remote servers and API integrations. That means it can pull data from monitoring tools, hit your CI/CD pipeline, and use external APIs as part of the work.

🔥 Want to be ahead on Jitro? Inside the AI Profit Boardroom, I share my Jitro prep workflows, async coding agent comparison, and weekly live coaching. 2,800+ members. → Get the prep playbook

What Stays The Same

A few things carry over cleanly from Jules.

Async execution stays — fire and forget. Repository integration stays — it works with your code. Transparency stays — you can see what it's doing before it acts. Free and paid tiers are likely to remain.

If you've already adapted to Jules' workflow, Jitro will feel familiar at the edges.

How To Adapt Your Workflow

Three changes worth making before Jitro lands.

1 — Stop writing task lists

For Jules, you'd write "fix bug X, add test Y, update dependency Z". For Jitro, you'd write "improve test coverage in the auth module".

Higher-level framing wins.

2 — Start tracking metrics

If you can't measure your goal, Jitro can't pursue it. Set up test coverage tracking, bug rate monitoring, and performance baselines now so you've got the signal Jitro will need.

3 — Plan for review checkpoints

Jitro will work toward goals over time. Plan to review at meaningful milestones rather than after every commit, because the unit of work is now the goal, not the change.

Trust And Control

Jules is currently easy to trust because each task is small. Jitro is harder to trust because it works on bigger objectives.

Google's design seems to handle this with approve-direction-before-execution steps, visible reasoning at the goal level, and human-in-the-loop checkpoints.

Even so, you should still test on low-stakes goals first, set narrow scope before broadening, and review thoroughly. Don't trust new tools with critical paths until you've earned the confidence.

Pricing Predictions

Pricing isn't announced, but the Jules pricing model suggests a free tier with limited goals per month, a paid tier through Google AI Pro and Ultra, and possibly an enterprise tier for teams.

If Jitro is dramatically more powerful, expect a higher price point.

When To Switch From Jules To Jitro

When Jitro launches (expected Google IO 2026, May 19), don't switch immediately.

Spend three weeks testing on side projects, comparing output quality, and validating cost ratios. Then migrate workflow by workflow rather than wholesale.

What Jitro Doesn't Replace

Be honest about the limits.

It doesn't replace senior engineers. It doesn't replace product judgement. It doesn't replace architectural decisions. It doesn't fully replace Jules for some workflows — small task work might still be faster on Jules.

Goal-based is more powerful but it adds overhead for trivial tasks.

Comparison To Other Agents

How Jitro lines up against other goal-pursuing agents.

Versus Z AI GLM 5.1, which can run 1,700 autonomous steps for 8 hours, is open source, and is available now — Jitro is more polished but less radical.

Versus Claude Code, which is async and agent-style but task-based — Jitro adds the goal layer.

Versus OpenAI Codex, which is more interactive and less goal-driven — Jitro is more autonomous.

For Google ecosystem users, Jitro is likely the natural choice. For others, alternatives exist.

I cover similar agent patterns in Hermes Agent Swarm — different ecosystem, similar idea.

What This Means For Solo Devs

If Jitro delivers what it promises, side projects ship faster, maintenance work happens hands-off, and you spend more time on creative work and less on routine engineering.

For independent developers, this is real leverage.

What This Means For Teams

For dev teams, the implications are bigger.

Junior devs use Jitro for routine work. Senior devs focus on goals and architecture. Code quality consistency improves because the same agent handles routine work across the codebase. Headcount-to-output ratios improve.

You don't fire engineers — you give existing engineers more leverage.

Daily Reality (Speculation)

What a day with Jitro might look like, based on the announced design.

In the morning you set 2-3 goals for the codebase. Throughout the day Jitro works on those goals in the background. In the afternoon you review progress on each goal and approve direction shifts as needed. Overnight Jitro continues if the goals aren't done.

You're orchestrating goals. Jitro handles execution.

🚀 Want full async agent automation? The AI Profit Boardroom has my agent stack, OpenClaw 6-hour course, 2-hour Hermes course, daily training, and weekly live coaching. 2,800+ members. → Join here

FAQ — Google Jitro vs Jules

Will my Jules workflows work in Jitro?

Likely yes — Jitro is the next version, not a replacement.

Should I migrate everything to Jitro on launch?

No. Test for 2-3 weeks first.

Will Jules be deprecated?

Not announced. But Jitro will likely be the recommended path going forward.

How do I prepare for Jitro?

Use Jules now. Practice describing work in terms of goals.

Can teams share Jitro workspaces?

Likely yes, based on the persistent workspace design.

What's the biggest risk with Jitro?

Trusting it with big goals before you've validated quality.

Is Jitro better than Cursor or Cline?

Different model — Jitro is goal-based, Cursor and Cline are interactive. They're built for different workflows.