Catch up with DevCon Fall conference talks in our YouTube Playlist
Logo
Back to articlesGoogle wants to make Jules a more ‘proactive’ coding colleague

12 Jan 20265 minute read

Paul Sawers

Freelance tech writer at Tessl, former TechCrunch senior writer covering startups and open source

AI coding assistants have largely been reactive tools: developers ask, assistants respond, and the interaction ends. Google’s latest update to Jules signals a shift away from that pattern, nudging coding agents closer to background infrastructure that can surface work and act without being explicitly prompted.

Jules, for the uninitiated, is Google’s AI coding agent, which launched out of beta back in August through Google Labs. It connects directly to GitHub repositories, runs in a managed cloud environment, and can analyze codebases before proposing changes via pull requests. While Jules already operated asynchronously, it generally acted in response to explicit developer requests, rather than surfacing work on its own.

Now, Google has expanded where and when that agent is allowed to operate.

Enabling proactive suggestions
Enabling proactive suggestions

Suggested tasks put Jules on the front foot

The most notable addition is proactive task suggestions. Jules scans connected repositories for signals such as #TODO comments and proposes relevant follow-on work without a developer explicitly asking for help. Those suggestions appear as recommendations that developers can review and approve.

Jules being proactive
Jules being proactive

Google frames this as a way to surface work that often gets deferred or overlooked. It allows Jules to initiate activity based on code context alone, marking a shift from “invoke the agent” to “the agent flags something worth attention.”

“Every codebase collects a trail of small tasks, drift and maintenance work,” Google Labs’ AI product manager Anirudh Kulkarni wrote in a blog post last month. “It’s the work you intend to get to eventually, or the work you don’t notice until it slows you down. Imagine if your agent helped you carry that load without being asked to, every time. We are betting on proactive agents, ones that can carry that load for you.”

Alongside that, Google has added scheduled tasks, allowing developers to define recurring jobs — such as routine maintenance or dependency checks — that Jules will run on a set cadence. This gives the agent a standing mandate to operate over time, rather than being tied to one-off requests.

Both features are currently available to users on Google’s AI Pro and AI Ultra plans, which bundle higher usage limits and access to more advanced models.

Event-driven fixes, with humans in the loop

As part of the announcement, Google also revealed that it was expanding Jules’ reach through integrations. A new connection with Render, a cloud platform for building and running web apps, allows Jules to respond when deployments fail. When Render surfaces an error, Jules can inspect logs, diagnose the issue, and propose a fix via a pull request.

Developers remain in the approval loop, reviewing and merging proposed fixes. But the agent now has clearer triggers — scheduled, contextual, or event-based — that let it act without being summoned.

Agent enablement amid growing tool sprawl

While much of the big headline news is often dominated by powerful new models or benchmark gains, the latest Jules update is centered around enablement: granting the agent permission to notice, schedule, and respond to events inside a development lifecycle. As coding agents move deeper into production environments, questions of authority, timing, and integration increasingly shape their usefulness as much as raw model capability.

That focus arrives as Google’s developer-facing AI tools continue to multiply. The company introduced Project IDX back in 2023 as an AI-assisted development environment, and in 2025 alone added Firebase Studio, Jules, Antigravity, and the Gemini command-line interface, each applying agentic assistance at different layers of the developer stack.

While these tools target distinct use cases, their functional boundaries can appear blurred. This hasn’t been lost on the developer community, with many questioning whether Google is spreading similar capabilities across too many products rather than consolidating them. One Reddit commenter, reacting to the growing list of Google-built coding agents, summed up the concern bluntly:

“Too many products, Gemini CLI, Antigravity, Jules, Google Code Assist?,” they wrote. “Unify all that under a single product.”

Join Our Newsletter

Be the first to hear about events, news and product updates from AI Native Dev.