Jules Release Notes

Release notes

Jules now automatically detects and fixes CI failures on pull requests it creates. When a check fails in GitHub Actions, Jules receives the error, works through a fix, and resubmits the PR — all without manual intervention.

Previously, a failed CI check on a Jules PR would stall your workflow. Resolving it required setting up REST API calls or manually copy-pasting error logs back to Jules. CI Fixer closes that gap. Jules now operates in a loop — fixing, committing, and resubmitting — so your PRs keep moving forward.

Authorship modes

You can now control how commits from Jules are attributed on GitHub. Three authorship modes are available:

• Jules: Jules is the sole author of all commits (default, existing behavior).
• Co-authored (Jules + You or You + Jules): Commits are co-authored by both you and Jules, crediting both contributors.
• User only: You are the sole author. Jules applies its changes under your identity.

Previously, Jules authored every commit and PR, which meant your GitHub contribution graph didn’t reflect the work you initiated. Setting the commit authorship in to co-authored to you or you + Jules, makes it clear to contributors and PR reviewers who is driving each change.

It applies at the user level across all repositories and all task types — scheduled, suggested, and manually triggered tasks.

Setting commit authorship

1. Go to the Jules Settings page
2. Open the Commit Authoring section
3. Select your preferred authorship mode
4. All future sessions will use the selected attribution

Today we’re launching MCP Server support in Jules starting with: Linear, Stitch, Neon, Tinybird, Context7, and Supabase.
Add a service connection in the Settings page and will trigger the MCP server tools in a session when it detects the need for a tool call.

Getting started

Our MCP server integration uses API key authentication. To get started:

• Get the service’s API key (such as Linear or Stitch)
• Go to the Jules Settings page
• Click on the MCP section
• Plug in your API key for that specific service
• Kick off a new session
• Jules will trigger the MCP server tools when it detects the need for the call

Focus on Security

It might seem odd for us to limit which MCP servers Jules can connect to. However, we are wanted to start with a focus on security. Jules operates within a cloud development environment connected to your GitHub repositories, so we prioritize a security-first approach to third-party integrations.
By hand-selecting these initial servers, we can:

• Validate Data Flow: We ensure that each server adheres to strict data-handling standards, keeping your source code and API keys isolated.
• Audit Tool Permissions: We verify that each server only requests the specific permissions it needs to function, preventing “over-privileged” access to your environment.
• Ensure Stability: A vetted integration means fewer connection drops and a more predictable experience when Jules interacts with your external data.
  We plan to expand this list as we work with more partners.

Tell us what to add next

If you have an MCP server in mind, you can let us know in the settings panel what we should add next.

Release Notes

Repoless comes to the REST API and we think this has massive potential. A repoless session in a sense becomes serverless, because it creates an ephemeral cloud dev environment with Node, Python, Rust, Bun, and other runtimes preloaded on the image.

The massive potential is that this serverless environment comes with an AI coding agent.
With a single API call you can spawn a serverless dev environment with only the context in your prompt. When it’s done you can download the file outputs from the session.
We can’t wait to see what you all do with this one.

Speaking of file outputs, we just made that a lot easier. When a session completes a task, you can now get the entire change set.
This is stored in a git patch format for parsing changes such as additions, modifications, and deletions.

Each Jules Session has a collection of activities that represent the steps Jules took to complete the task. These activities are immutable and can be used to reconstruct the session.
Activities follow the event source pattern, meaning once they occur they never change. They are a record in time of the steps Jules took to complete the task. Since they never change, you can cache them aggressively.
We added a createTime filter that works like a range cursor and allows you to only fetch new activities over the network.
This may seem like a small optimization but stay tuned. We have some big news around this one.

Scheduled Tasks

You can now set recurring tasks for Jules. Whether it’s a weekly dependency check, a nightly lint fix, or a monthly cleanup, just define it once and Jules will handle the rest on your schedule.

To get started, navigate to the Scheduled tab on your repo page to configure your first task.

• Set it and forget it: Define your maintenance chores once. Jules will wake up, perform the task, and open a PR without you needing to lift a finger.

• Never miss a beat: No more manual prompts for the stuff that needs to happen every week. Ensure consistent code quality and dependency hygiene by automating your routine work.

This feature is available today for all Jules users.

Read more at: Scheduled Tasks.

Render integration

We’ve integrated with Render to handle the last mile of shipping code. Jules can now detect failed builds, analyze the logs, and push fixes to its PRs before you even know your build failed.

To enable this, go to your Render Dashboard, open the Help menu (top-right), and click Coding Agents to provision your API Key. Paste this key into Settings > Integrations in Jules.

• Instant Recovery: No more context switching to dig through console logs. Jules detects the failure immediately and identifies the root cause.
• Proactive Fixes: Instead of just alerting you to an error, Jules writes the code to fix it. Review the solution as a standard commit on your PR, merge it, and get back to green.

This integration is available now. Check out the docs for the full setup guide, including enabling PR previews.

Note: For now, Jules only fixes PRs it has created.

Proactive Suggestions: Suggested Tasks

Jules can now work proactively in the background to improve your code. With Suggested Tasks, Jules scans your repository for potential improvements and presents them on your repo page.

To get started, enable the proactive suggestions toggle on the repo page.

• Tackle the #TODOs: In this initial release, Jules focuses on identifying #TODO comments in your code. It reads the context, formulates a plan, and presents it for your approval—turning idle comments into active solutions. More use cases coming soon.

• Continuous Improvement: Once enabled, Jules continuously monitors your codebase. You don’t have to ask; just check your dashboard for new suggestions and approve the ones you want.

This experimental feature is available today for Google AI Pro and Ultra subscribers on up to five repositories.

Read more at: Suggested Tasks.