Agentic AI Coding with Google Jules
Picture by Writer# Introduction
When you have been writing code up to now couple of months, I’m fairly certain you have to have seen a shift. AI is now not one thing that simply suggests snippets; it has gone past that, it’s beginning to act. Builders are transferring from assistive instruments like Copilot to agentic methods that perceive a objective, plan a sequence of steps, and execute them on their very own.
Google Jules sits on the entrance of that curve. It’s not a chat assistant that lives in your IDE; it’s a totally asynchronous coding agent. You inform it what you need fastened, up to date, or examined, and it does the work remotely, from cloning your repo, modifying code in a safe cloud VM, working assessments, and opening a pull request for evaluate.
The distinction is refined however profound: Jules doesn’t wait so that you can sort. It acts independently, guided by your intent and the context of your codebase. It reads your documentation, runs builds, reveals its plan earlier than touching something, and even explains every change in a diff view. Whilst you give attention to structure or design, Jules quietly handles the upkeep duties that devour most of a developer’s day, corresponding to model bumps, flaky assessments, forgotten docstrings, and low-impact bugs.
# What Makes Jules Completely different?
Most AI coding instruments nonetheless reside inside your editor. They autocomplete features, counsel patches, or refactor small snippets when you supervise line by line. Jules doesn’t try this. It strikes all the workflow exterior your native setting and runs it asynchronously within the cloud.
Once you assign Jules a job, let’s say, “Improve the app to Subsequent.js 15 and migrate to the app listing,” it doesn’t simply predict. It pulls your repository from GitHub, units up a digital machine, installs dependencies, writes and assessments the adjustments, and presents a plan and diff earlier than making any adjustments to your major department.
That end-to-end workflow is what makes Jules completely different from suggestion-based assistants like Copilot or Cody. It’s not serving to you write code quicker; it’s serving to you end work you’d quite not do in any respect.
The platform is constructed round 4 core concepts:
- GitHub-Native Integration — Jules works via points, branches, and pull requests like a teammate. You’ll be able to even assign it duties immediately by including the
juleslabel to a difficulty. - Cloud Execution Atmosphere — Each job runs in a clear Ubuntu VM with Node.js, Python, Go, Rust, Java, and Docker preinstalled. No native setup, no dependency drift.
- Clear Reasoning — Jules reveals you its plan, explains every step, and generates diffs earlier than merging. You see precisely what it’s considering.
- Asynchronous Autonomy — As soon as began, Jules retains working even when you shut the browser. You get notified when it’s achieved.
# The Jules Structure
Jules is a workflow system wrapped round a big language mannequin, Gemini 2.5 Professional, and a cloud-based execution layer. It combines structured automation with agent reasoning, which means each step (plan, edit, take a look at, PR) is observable, traceable, and reversible.

Picture by Writer
Right here’s the way it truly works behind the scenes:
- Activity Initialization: Once you describe a job (“Add integration assessments for auth.js”), Jules creates a session linked to your GitHub repo and department. It fetches the repository metadata and setting hints from recordsdata like README.md or AGENTS.md.
- Atmosphere Setup: Jules spins up a short-lived Ubuntu digital machine within the cloud. It installs your dependencies robotically or runs your setup script —
npm set up,pytest,make construct, no matter you outline. All the pieces runs in isolation, so your repo stays protected. - Reasoning and Planning: Utilizing Gemini 2.5 Professional, Jules analyzes the codebase and your immediate to supply a plan: which recordsdata to switch, which features to the touch, and which assessments to create. It presents this plan for evaluate earlier than executing. You’ll be able to edit or approve it immediately within the interface.
- Code Technology and Testing: As soon as accredited, Jules executes every step contained in the VM. It writes or modifies code, runs the take a look at suite, validates the output, and logs each lead to an exercise feed. That is the place you may watch Jules “assume aloud” — explaining why it modified every file.
- Diff and Evaluate: Each edit comes with a Git diff. You’ll be able to broaden it, evaluate the patch, and obtain or copy snippets. Jules explains every change in pure language and sometimes hyperlinks it again to the plan step that prompted it.
- Commit and PR Creation: Lastly, Jules pushes the up to date department to GitHub and opens a pull request, the place you (or your CI pipeline) can evaluate and merge. You keep the proprietor of the repo — Jules solely commits as an assistant.
The whole system runs asynchronously. You’ll be able to shut your laptop computer, get espresso, or work on one other department whereas Jules finishes a construct or take a look at run. When it’s achieved, it sends a browser notification or updates the UI.
# Getting Began with Jules
Jules is designed to really feel easy from the primary click on. You don’t want to put in or configure something; it runs totally within the cloud, with GitHub because the entry level. Right here’s what the standard onboarding circulation appears to be like like.
// 1. Log in and Connect with GitHub
Go to jules.google and register along with your Google account. After accepting the privateness discover, you’ll be prompted to attach your GitHub account. Jules solely works with repositories you explicitly grant entry to, so you may select to attach all or only a few initiatives.
As soon as related, you’ll see your repositories listed in a selector. Select one, and Jules will robotically detect its branches, README, and construct context.

Picture by Writer
// 2. Write a Clear Activity Immediate
On the coronary heart of Jules is the immediate field, which is the place you describe what you need achieved. You’ll be able to sort plain English directions like:
Add a take a look at for parseQueryString() in utils.js
To assign a job immediately from GitHub, merely add the label ‘jules‘ to a difficulty. Jules will choose it up robotically, generate a plan, and begin making ready a VM.
You’ll be able to even connect photographs (corresponding to UI mockups or bug screenshots) to offer extra context. Jules makes use of these as visible hints, not as belongings to decide to your repo.
// 3. Evaluate the Plan
Earlier than any code is written, Jules reveals you its reasoning, a structured breakdown of the steps it intends to take. You’ll be able to broaden every step, depart feedback, or request changes immediately within the chat. When you approve the plan, Jules begins executing inside a recent digital machine.
Picture by Writer
// 4. Watch Jules Work
Within the exercise feed, you’ll see reside logs of what Jules is doing, putting in dependencies, modifying recordsdata, working assessments, or producing diffs. You’ll be able to step away; it’s asynchronous by design.
When it’s achieved, you’ll get a abstract exhibiting:
- Information modified
- Complete runtime
- Traces of code added or modified
- Department created with commit message

Picture by Writer
From there, you may click on Publish PR, and Jules will open a GitHub pull request with their adjustments already pushed. You’ll be able to then evaluate and merge the PR as soon as you’re happy with it.
# The Jules CLI
Whereas the online app offers you a visible dashboard, the Jules Instruments CLI brings the identical energy on to your terminal. It’s light-weight and integrates easily into your on a regular basis developer workflows. You should use it to start out duties, test progress, or pull outcomes with out ever leaving your editor or CI/CD pipeline.
// 1. Set up and Login
Jules Instruments is accessible via npm. Set up it globally with:
npm set up -g @google/jules
After set up, log in along with your Google account:
A browser window will open for authentication, and as soon as confirmed, you’ll have full entry to your Jules classes.
// 2. Checking Repositories and Classes
The CLI enables you to view all related GitHub repositories and lively classes.
# Listing related repos
jules distant checklist --repo
# Listing lively or previous classes
jules distant checklist --session
This mirrors what you’d see on the Jules dashboard, however in terminal type, helpful for automated checks or when engaged on a headless server.
// 3. Making a New Session
Beginning a brand new coding job is simply as easy:
jules distant new --repo . --session "Add TypeScript definitions to utils/"
This command tells Jules to fetch the present repository, spin up a safe cloud VM, and start planning. You’ll get a session ID in return, which you should use to observe or pull adjustments later.
// 4. Pulling Outcomes Again
As soon as Jules finishes a job and creates a pull request, you may convey the ensuing adjustments again to your native setting:
jules distant pull --session 123456
That is helpful for CI methods or groups that need to evaluate adjustments offline earlier than merging.
// 5. Launching the TUI
For those who choose visuals, you may merely sort:
This launches the Terminal Consumer Interface (TUI), a minimal dashboard that reveals reside classes, duties, and their progress, all inside your terminal. It’s the right mix of automation and visibility.
# Selecting Jules Plans that Match Your Workflow
Jules is constructed to scale along with your coding, from solo debugging to enterprise-level agile growth. It’s out there in three tiers, every tuned for various workloads, however all powered by the identical Gemini 2.5 Professional mannequin.
Paid plans are managed via Google AI Plans, at the moment out there just for particular person @gmail.com accounts. Google has confirmed that Workspace and enterprise paths are coming quickly.
| Plan | Greatest For | Day by day Duties | Concurrent Duties | Mannequin Entry | Notes |
|---|---|---|---|---|---|
| Jules | Attempting out real-world coding automation | 15 duties per day | 3 at a time | Gemini 2.5 Professional | Free to start out, good for interest or take a look at initiatives |
| Jules in Professional | Builders who ship day by day and need a fixed circulation | 100 duties per day | 15 at a time | Increased entry to the newest Gemini fashions | Included with Google AI Professional Plan |
| Jules in Extremely | Energy customers or large-scale agent workflows | 300 duties per day | 60 at a time | Precedence entry to the most recent Gemini releases | Included with Google AI Extremely Plan |
When you’ve used your day by day quota (measured over a rolling 24-hour interval), you may nonetheless view and handle current classes; nevertheless, you can not begin new ones till the restrict resets. Jules will show a tooltip or “Improve” immediate when that occurs.
Every plan enforces its personal concurrency restrict, which determines the utmost variety of VMs that may run concurrently. Exceeding it merely queues duties, guaranteeing protected parallel execution with out conflicts.
Each Jules session spins up a safe digital machine with actual compute price. Limits guarantee stability, isolate workloads, and defend repository information from overuse or abuse. In addition they assist Google benchmark efficiency for upcoming multi-agent upgrades.
# Privateness, Safety, and Knowledge Dealing with
When an AI system runs your code, belief isn’t non-obligatory; it’s all the things. Jules was designed from the bottom up with developer privateness in thoughts. Each repository, job, and setting is dealt with in isolation, and none of your non-public information is used for mannequin coaching.
Right here’s what which means in observe:
- Brief-Lived, Remoted Digital Machines: Every job Jules runs takes place in a brief cloud VM. As soon as the duty completes, whether or not it succeeds or fails, the setting is destroyed. No persistent containers, no shared volumes, and no long-lived processes. This sandbox mannequin protects your repository from leaks or cross-contamination between runs. Each new job begins clear.
- Specific Repository Entry: Jules can solely entry the repositories you authorize via GitHub. To cease a repository from working, merely revoke its entry via your GitHub software settings.
- No Coaching on Personal Code: Not like some assistants that silently gather context, Jules doesn’t practice on non-public repositories. Your prompts, diffs, and commits are used just for that session’s execution, by no means for bettering the mannequin. This level is central to Google’s method to agentic methods: the mannequin might enhance via mixture studying, however not out of your private or company code.
- Protected Execution and Dependency Dealing with: All builds occur in a totally sandboxed setting. You’ll be able to examine each command that runs through the exercise feed or logs. If one thing appears to be like dangerous, you may pause or delete the duty at any time.
- Clear Logs and Full Auditability: Each motion Jules takes, e.g. plan creation, diff era, testing, commit, or PR, is logged. You’ll be able to obtain or evaluate these logs later for compliance or auditing.
# Wrapping Up
Software program growth is coming into an agentic section, the place AI doesn’t simply help, however participates. Google Jules is among the clearest examples of that shift.
It integrates immediately with GitHub, runs duties safely in its personal VM, validates its output via assessments, and reveals its reasoning and diffs earlier than merging something. Whether or not you’re fixing a bug, refactoring a characteristic, or cleansing up dependencies, Jules offers you a strategy to transfer quicker with out slicing corners.
For groups exploring automation or builders uninterested in upkeep overhead, that is the place the following era of AI tooling begins. Discover it your self at jules.google and see what it feels wish to code alongside an agent that actually works with you.
Shittu Olumide is a software program engineer and technical author captivated with leveraging cutting-edge applied sciences to craft compelling narratives, with a eager eye for element and a knack for simplifying complicated ideas. You may also discover Shittu on Twitter.