Jules — the async coding agent that exited beta last year — gets a structural upgrade at I/O 2026, and Google also reveals the internal name of a much more ambitious direction: Project Jitro.
The paradigm shift
Until now, development agents worked on a task-driven model: you describe a task ("write this test", "refactor that function"), the agent executes. Jitro proposes a different, goal-driven model: you define an outcome ("raise test coverage to 80%", "drop p95 latency by 30 ms", "fix all accessibility violations") and the agent autonomously figures out which changes are needed to move that metric.
What landed at I/O
The intermediate step is already concrete: Jules V2 introduces a CI fixer, native integrations with Stitch and Linear, and new APIs that let agents trigger design workflows or propagate design feedback down to code. The next leap — Jitro as a persistent agentic workspace, with goals, insight tracking and integration configuration — is positioned as the natural evolution, arriving behind a waitlist.
Why it matters
According to DevOps.com and ByteIota, the shift from prompts to goals is the key point: it changes who is in control of "how" the work gets done. For senior teams, it means being able to focus on architecture while the agent works through a maintenance backlog. For junior teams, it means having a tool that, in principle, makes scoping decisions for them — with all the risks that involves. Worth watching closely, but also with skepticism: the bar to measure success is no longer "did it write the right code", but "did it understand which part of the system actually needed to be touched".