---
title: Fixing a bug using AI with Google Jules
url: https://calvin.my/posts/fixing-a-bug-using-ai-with-google-jules
published: 2025-05-22
updated: 2026-09-17
category: AI
tags:
- Google
- Jules
- Web
- vibe coding
summary: The post demonstrates using Google Jules, a cloud-based GitHub coding agent, to repair a nonfunctional Delete button. After granting repository access, users describe requirements, review Jules’s proposed plan, and let it implement changes in a dedicated bug-fix branch. The example requires disabling deletion for content older than two hours and producing a clear commit message. Jules also generated tests without being asked and supported concurrent tasks, while users retained review, publishing, and pull-request control.
---

# Fixing a bug using AI with Google Jules

**Jules** is a coding agent created by Google. It integrates with Github and runs on the Cloud. This article demonstrates how to use Google Jules to fix a bug.

* * *

## Pre-requisites

1. Sign up Jules [here](https://jules.google/).
2. Jules is given access to your GitHub repository.

   ![](https://camy-pub.s3.ap-southeast-1.amazonaws.com/38eb60ff-1240-46e0-9fb3-55d4177e43ec.png)

* * *

## The Plan

1. The task:

   ```md
   In this demo, Jules should fix the nonfunctional Delete button. 
   Jules is also informed that the requirements are the same as those for the Delete button in another module.
   ```

2. The expectations:

   - A functional delete button.
   - A delete button will be disabled if the content was created more than 2 hours ago.
   - A meaningful commit message that explains the change.
   - All changes are placed in a bug fix branch.

* * *

## The Steps

1. Select the repo, branch, and tell Jules your request.

   ![](https://camy-pub.s3.ap-southeast-1.amazonaws.com/6a84bee8-70df-49be-a5c7-e3dde58f2940.png)

2. Jules provides you with a plan. If agreed, it launches an instance, clones the repository, and starts working on the code.

   ![](https://camy-pub.s3.ap-southeast-1.amazonaws.com/3e31e559-fc6c-4f66-a7e7-b8e129f0f7a3.png)

3. Once the task is completed, it presents you with the code changes.

   ![](https://camy-pub.s3.ap-southeast-1.amazonaws.com/9c9692d7-ae98-40b2-aee8-b17a62845239.png)

4. You can then review and push the changes into a bug fix branch.

   ![](https://camy-pub.s3.ap-southeast-1.amazonaws.com/a1b75857-03b6-42d1-9209-a22499b08d3d.png)

5. Once published, the branch appears in your GitHub repository.

   ![](https://camy-pub.s3.ap-southeast-1.amazonaws.com/065c9366-591c-47d0-b98f-e6ae4c1e9210.png)

6. You can then check if the GitHub Actions are successful or make a Pull Request.

* * *

## Other Observations

1. Although not specifically requested, it prepares test cases for the changes.

   ![](https://camy-pub.s3.ap-southeast-1.amazonaws.com/29e941e4-5c30-4d0d-95f3-e5e3c02d8dab.png)

2. You can perform multiple tasks at the same time. For example, a task to explain the repo and a task to perform bug fixing are running concurrently.

   ![](https://camy-pub.s3.ap-southeast-1.amazonaws.com/b3d81441-4873-4e7e-a6df-de2fb7302667.png)