Overview: Jules Tools goes local for developers
Google announced a major expansion of Jules Tools by releasing a dedicated command line interface and a public API to embed the Jules AI coding assistant directly into developer environments. This means you can run Jules from a terminal, inside CI/CD pipelines, or in Slack without bouncing between the web UI and your code base. Previously Jules was accessible mainly through its web interface and GitHub workflows. Google’s product director for Google Labs described the move as a way to minimize context switching and make Jules more transparent in daily workflows.
What is new: CLI and public API
The new Jules Tools CLI exposes a set of commands to interact with the agent, run coding tasks, fetch code, generate changes, and delegate work directly from the terminal. The public API enables IDE plugins and integrations with other tools in the dev stack. In practice, developers can stay in the editor or in a chat tool and still harness the AI assistant for concrete tasks such as code generation, debugging prompts, or documentation generation. Jules and Gemini 2.5 Pro share the same model lineage, but Jules is tuned for task oriented interactions while Gemini CLI aims for more interactive collaboration.
CLI features and usage
With the CLI, teams can script common workflows and incorporate Jules into their existing automation. Typical commands might include jules task run, jules fetch dependencies, or jules summarize code changes. The goal is to let engineers keep their hands on the keyboard and let Jules handle repetitive or context heavy coding chores.
Public API and IDE plugin roadmap
Google also opened a public API that enables IDE integrations and potential plugins for popular development environments. The company plans to roll out plugins for leading IDEs, allowing actions such as invoking Jules from within the editor, passing code snippets for analysis, and receiving AI generated improvements in place. This API-first approach is meant to accelerate adoption across teams and toolchains.
Jules vs Gemini CLI: two paths to AI assisted coding
Both Jules and Gemini CLI are built on Gemini 2.5 Pro, but they target different interaction styles. Jules concentrates on concrete tasks and direct automation, whereas Gemini CLI emphasizes a more fluid, chatlike collaboration with the agent. The dual approach gives developers options depending on whether they want scripted automation or ongoing, conversational guidance during development.
Impact on developer workflows
By enabling CLI and API access, Google aims to reduce the friction of using AI assistants in real work. Engineers can stay inside their preferred tools while delegating coding tasks to Jules, potentially speeding up code generation, review, and documentation. At the same time, teams should consider security and governance when exposing coding tasks to an external AI, and adopt best practices for data handling and guardrails in automated workflows.
Future directions and considerations
Beyond the current release, Google plans to expand with IDE plugins for the most popular editors and deeper integrations into the build and deployment pipeline. As AI assistants mature, the company will likely introduce more fine grained controls, auditing, and privacy protections to balance productivity with safety in professional coding environments.
Conclusion
The Jules Tools CLI and public API mark a significant shift in how AI coding assistants fit into developer workflows. By moving from a web interface to the terminal, IDEs, and CI/CD, Google is pushing Jules toward being a first class partner in the day to day work of engineers, not a stand alone web tool. The coming plugins and integrations could redefine how teams approach automation, collaboration, and code quality in a world where AI is increasingly embedded in programming practice.
