Google expands Jules: from web interface to developer toolchains
Google has announced a significant expansion of its Jules AI assistant with two new capabilities designed to embed the agent directly into developers’ workflows: Jules Tools’ command-line interface (CLI) and a public API. The update allows engineers to run Jules inside their terminal, CI/CD pipelines, and even Slack, removing the need to flip between the web interface and other tools. This move aims to make Jules a more transparent, integrated collaborator in the coding process.
What Jules Tools brings to developers
Before this rollout, Jules was primarily accessible via a web interface and GitHub workflows. The new CLI enables direct, scriptable interactions with the agent through simple commands, smoothing tasks like code analysis, task delegation, and automation of repetitive coding chores. The public API extends this reach beyond the CLI, opening the door for IDE plugins and integrations with other developer tools. As a result, developers can keep their hands on the keyboard and their minds on the code without constantly context-switching between separate surfaces.
CLI: command-driven interaction with a “specific tasks” mindset
The Jules Tools CLI is designed for task-oriented workflows. Engineers can issue targeted commands to the agent to perform concrete coding tasks, fetch insights, or automate steps in the build and test process. By leveraging the CLI, teams can embed Jules directly in their terminal sessions and CI pipelines, enabling automated guidance and assistance as part of the standard development cycle.
Public API: unlocking IDEs and broader tool ecosystems
The public API is a strategic expansion that Google says will enable Jules to plug into the most popular integrated development environments (IDEs) and other developer tools. The company plans to develop plugins for leading IDEs so teams can invoke Jules without leaving their familiar environments. This API-first approach supports more transparent collaboration, allowing Jules to operate in the context of pull requests, code reviews, and automated workflows.
Jules vs. Gemini CLI: different but complementary models
Google notes that Jules and Gemini CLI are both built on the Gemini 2.5 Pro foundation, yet they follow different interaction paradigms. Jules is oriented toward “specific tasks,” making it ideal for deterministic coding assistance, automation, and delegation. In contrast, the Gemini CLI emphasizes interactive collaboration, enabling a more exploratory dialogue with the agent. Together, they offer a spectrum of automation and guidance that can be tailored to diverse developer needs.
Why this matters for developer productivity
According to Katie Koreveck, product director at Google Labs, the overarching goal is to minimize context switching for developers and to make Jules more visible within daily workflows. By running Jules in the terminal, CI/CD, and Slack, teams can assign coding tasks, obtain real-time recommendations, and orchestrate multi-step processes without leaving their primary work environment. Early adopters are likely to see faster iteration cycles, tighter integration of AI-assisted insights, and reduced friction when moving from idea to implementation.
Looking ahead: IDE plugins and broader adoption
Beyond the current CLI and public API, Google plans to roll out plugins for the most widely used IDEs, creating a seamless bridge between Jules and developers’ favorite coding habitats. The vision is to embed Jules as a reliable automation partner that can draft, review, and optimize code in the context of ongoing projects, while still respecting security and governance considerations.
What developers can do now
Teams interested in Jules Tools should monitor Google’s updates for API access details, authentication methods, and documentation for the CLI commands. Early pilots are expected to demonstrate how Jules can manage routine coding tasks, triage issues, and propose refactor opportunities directly within familiar workflows, all without sacrificing control or transparency.
Conclusion
With Jules Tools, Google is turning a previously web-centric AI assistant into a practical, integrated helper for developers. The CLI and public API together lower barriers to adoption, supporting easier delegation of coding tasks, smoother CI/CD automation, and deeper integration into IDEs and Slack. As Jules moves from a standalone tool to a built-in companion in the developer toolbox, the future of AI-assisted software engineering looks more embedded—and more efficient.
