If you use Google’s Jules coding agent, finish your open sessions and export your data before November 11, 2026. After that date Jules turns read-only, and on December 31, 2026 it shuts down for good. Your code, branches and pull requests are already in GitHub and stay there. What disappears is everything that lives only inside Jules: your settings, environment variables, scheduled tasks, per-repo memories, setup scripts and the full history of every session. Google published an official export prompt that you paste into an AI coding agent such as Claude Code; the agent installs the Jules command-line tool, checks your login and saves everything to a folder in your home directory. This guide walks through that process in plain language, lists the snags people hit, and covers where to take your work next.

Everything below was checked on November 4, 2026 against Google’s Jules Turndown notice (October 29, 2026), the Jules changelog, Google’s Antigravity Remote Agents docs and the Antigravity changelog entry for v2.29.0 (November 3, 2026). The Verge reported the shutdown the same day it was announced.

Key facts:

• November 11, 2026: last day to keep working in Jules sessions. After that, Jules is read-only until the end of the year. (Jules Turndown)
• December 31, 2026: Jules winds down completely. (Jules Turndown)
• Your GitHub code is safe: “Your code, branches, and pull requests already live in GitHub, so they stay where they are.” (Jules Turndown)
• What the export saves: account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and every session with its prompt, plan, full activity log and code patches. (Jules Turndown)
• Where Google points you: Google says the lessons from Jules are going into its agent-first platform, Google Antigravity. Antigravity’s cloud-based Remote Agents began rolling out on November 3, 2026 to Google AI Pro and Ultra subscribers. (Antigravity changelog)

Who needs to do this

You need to act if any of these are true:

• You have Jules sessions that are still running or that you planned to come back to. You can only continue them until November 11.
• You set up scheduled tasks in Jules (Google added them in December 2025, for jobs like a weekly dependency check or a nightly lint fix). Those schedules live inside Jules, not in GitHub, so they stop when Jules does.
• You added environment variables or setup scripts to a repository in Jules so it could build and test your project. You will want those again in whatever tool you use next.
• Jules saved memories for your repositories (the preferences and corrections it learned from you, a feature Google added in September 2025). They are your best record of how you like an agent to work on that code.
• You want a record of what Jules did: the prompts you gave it, its plans and the patches it produced.

If you only ever used Jules to open pull requests and you merged or closed all of them, you lose very little. Your code history is in GitHub. Even so, the export takes a few minutes and costs nothing, so it is worth doing before the deadline.

What you need before you start

The export runs on your own computer, not in the Jules website. You need:

1. A Mac or a Linux machine. Google’s export prompt checks for your Jules login in the macOS Keychain or with the Linux secret-tool command, and it also looks for a saved login file in your home folder. It does not mention Windows. If you are on Windows, the Jules command-line tool has had credential fixes for WSL (Windows Subsystem for Linux) since version 0.1.40, according to the Jules changelog, so running the export inside WSL is the closest match to what Google tested.
2. Node.js with npm installed. The Jules command-line tool, called Jules Tools, is installed through npm. If npm is missing, Google’s prompt tells the agent to stop and tell you, so you will know.
3. A command-line AI coding agent. Google’s notice says to use “a CLI coding agent, such as Claude Code”. Codex CLI or the Antigravity CLI should work the same way, since all the prompt asks for is an agent that can run commands and save files. If you have never used one, our guide to Claude Code in the cloud explains what these agents are, though for this job you need the version that runs on your own computer.
4. The Google account you use for Jules, and access to the GitHub account you connected to it.

Step 1: Sign in to Jules from your computer

Google’s notice asks you to install Jules Tools and sign in first. If you are comfortable typing two lines into the Terminal app, those lines are on the Jules Turndown page: one installs the tool and the other, jules login, opens a browser window where you sign in with your Google account.

If you would rather not type anything, skip ahead. The export prompt tells the agent to check whether Jules Tools is installed and to install it if it is missing. What the agent will not do is sign in for you. The prompt explicitly says sign-in is an interactive browser step, so the agent will pause and ask you to run jules login yourself. In Claude Code you do that by typing ! jules login in the chat box; the ! tells Claude Code to run the command directly. A browser tab opens, you pick your Google account, and then you tell the agent you are done.

Step 2: Open your agent in your home folder

Start your agent from your home directory (the folder with your user name, for example /Users/yourname on a Mac). Google’s prompt saves everything to a folder called jules-export inside the folder where it runs, so starting in your home folder puts the result at ~/jules-export, which is where Google’s instructions expect it.

Do not start the agent inside one of your code projects. The export contains your environment variable values, and you do not want that folder landing inside a Git repository where it could be committed and pushed by accident.

Step 3: Copy Google’s export prompt and paste it in

On the Jules Turndown page, click Show the export prompt. Copy the whole block, from “I want to export all my data from Google Jules” through the end of the script, and paste it into your agent as one message.

Use Google’s prompt exactly as published rather than a version you found elsewhere. It has three parts:

• Setup checks. The agent checks that Jules Tools is installed, checks that you are signed in, and lists your connected repositories to confirm GitHub access works.
• The export script. A short Python program that downloads your data and writes it to jules-export. The script uses only Python’s built-in libraries, so beyond Python 3 itself there is nothing extra to install; if Python is missing, your agent will tell you.
• Known problems. A list of errors earlier users hit, so the agent knows how to react instead of guessing.

The prompt also tells the agent not to print your access token or the values in your environment variables file, and to finish by telling you what it exported and the full path of the folder.

Your agent may ask permission before it runs commands or writes the script to a file. That is normal. Read what it wants to run; it should be the Jules setup commands and the Python script from Google’s page. If you use Claude Code and want to understand those permission prompts, our guide to Claude Code permissions and auto mode explains each option.

Step 4: Check what was exported

When the script finishes, it prints a short summary with counts: the number of repositories, how many repositories had memories, the number of sessions, the number of patches, how many repositories had a setup script or test command, and any errors. Ask your agent to show you that summary if it does not.

According to Google’s notice, the folder contains:

What	Where in ~/jules-export
Connected repositories	sources.json
Per-repository setup script, test command and memories	a folder per repository under repos/ (setup.sh, test-command.txt, memories.md and memories.json)
Account settings	user-settings.json
Environment variables, with their values	env-variables.json
Scheduled tasks	scheduled-tasks.json
Every session	a folder per session under sessions/, with a readable summary.md, the full activity log in activities.json, and code changes as patch-1.diff, patch-2.diff and so on

The quickest way to sanity-check the result is to open a few summary.md files. Each one lists the session’s title, repository, status, dates, your original prompt, Jules’s latest plan, any code outputs with their branch names and the activity counts. If those look right for sessions you remember, the export worked.

Troubleshooting

Google built the most common failures into the prompt itself. Here is what they mean in plain terms.

Every call fails with a 401 error. Your Jules login has expired. Google’s notes say the access token lasts about an hour after you sign in. Run ! jules login again (or any jules command) and ask the agent to retry.

Only the repository list fails with a 401 “missing required authentication credential” error. Your GitHub account is not connected to Jules. Google’s prompt sends you to the Google Labs Jules GitHub app page, github.com/apps/google-labs-jules/installations/select_target, to connect it. Approve access there, tell the agent, and it will continue. If you never used Jules with GitHub repositories, you can skip this; the export just will not include repository data.

A call returns 404 or 400. The export uses internal Jules endpoints that are not officially documented. Google’s prompt tells the agent to report which one failed rather than guess at a fix. If this happens, note the error and try again later; do not let the agent invent workarounds.

memories.json is empty or a repository has no memories folder. Google’s notes say an empty response simply means there were no memories for that repository.

There are more sessions in the export than you see in Jules. Expected. Google says the export can include a few older sessions that the command-line list does not show.

Setup scripts are missing for a repository. The repository list in Jules does not include setup scripts or test commands, so the script recovers them from the code output of your past sessions. If a repository never had a session that produced code, there may be nothing to recover. Check the repository’s settings page in Jules while you still can and copy anything you need by hand.

The agent says npm is not installed. Install Node.js from its official site, or ask the agent how to install it on your system, then paste the prompt again.

Step 5: Protect the export folder

env-variables.json contains the actual values of your environment variables, which often include API keys and database passwords. Google’s notice says to “keep the export folder private and out of your repositories”. A few habits help:

• Leave the folder in your home directory, not in a project folder or a synced shared drive.
• Once you have re-entered those variables in your new tool, consider deleting env-variables.json, or move it into your password manager.
• If you ever shared or committed the file by mistake, rotate those keys with each service.

Step 6: Decide where your work goes next

Jules’s main appeal was that it worked in the cloud: you gave it a task, closed your laptop, and came back to a pull request. If that is what you will miss, here are the realistic options.

Google Antigravity Remote Agents (Google’s suggested path)

Google’s notice says the lessons from Jules are shaping Antigravity, and on November 3, 2026 Antigravity v2.29.0 started rolling out Remote Agents, which run conversations in a Google-managed cloud environment “instead of on your computer”. The Remote Agents docs say they keep working when you close your browser or put your laptop to sleep, and you can pick them up from the Antigravity app, the Antigravity CLI or the web at antigravity.google.com.

The catches matter:

• Plan: Remote Agents are for Google AI Pro and Google AI Ultra subscribers on a personal Google account. They are not on the free plan, on Google AI Plus, or for Google Workspace and Google Cloud business accounts.
• Rollout: they are “rolling out gradually”, so you may not see the option yet.

To start one in the Antigravity app, the docs say to click + next to Projects in the left sidebar (or open the project selector in the message box), choose New Remote Project, optionally click Add Resource to attach GitHub repositories, Google Drive files or uploaded files, name the project and click Create. You can also pick Remote > GitHub Repositories from the project selector in the message box; if GitHub is not connected yet, click Connect GitHub. On the web, sign in at antigravity.google.com with an eligible account and either type a prompt or click Create Project next to Projects.

Two Antigravity details worth knowing before you move:

• Permissions default to “always proceed”. In the Antigravity CLI, the docs say the remote agent permission preset is always-proceed (turbo) unless you change it, so remote agents run commands without asking. If you are used to approving Jules’s plans, change the preset to default (asks before sensitive operations) or request review (asks before every command) in the CLI’s /config Remote Agent tab, and set Plan Review Policy to always ask.
• Private repositories from different owners need separate projects. All private repositories in one remote project must belong to the same GitHub user or organization.

For scheduled jobs, the Antigravity changelog says v2.29.0 also redesigned the Automations page into Scheduled, Always on and Paused lists. Open scheduled-tasks.json from your export (or ask your agent to summarize it in plain English) and recreate each one there. Google has not said these schedules move over automatically, so plan to recreate them yourself.

If you were already burned by Google’s last forced move, the Gemini CLI shutdown in June, it is reasonable to check that Remote Agents actually appear in your account and fit your plan before you commit to them.

Claude Code on the web

If you pay for Claude rather than Google AI Pro, Claude Code’s cloud sessions do the same kind of job: they connect to your GitHub repository, work on a task in the cloud and hand back changes for you to review. Our step-by-step Claude Code in the cloud guide covers who can use it, how to connect GitHub and how to review and merge.

Any other agent you already use

Whatever you pick, your Jules export is useful there. The practical moves:

1. Memories. Open each repos/<name>/memories.md. These are the preferences Jules learned. Paste them into your new agent’s instructions for that repository, or simply tell the agent: “Read this file and add the useful rules to the instruction file you use for this project.”
2. Setup scripts and test commands. Give setup.sh and test-command.txt to your new agent when it first sets up the project, so it installs and tests the same way Jules did.
3. Environment variables. Re-enter them in the new tool’s settings by hand. Do not paste the whole JSON file into a chat.
4. Unfinished work. For any session that never became a pull request, the patch-*.diff files hold the code changes. You can ask your agent to “apply this patch to my repository on a new branch and summarize what it changes”.

A short checklist

• Finish or wrap up any active Jules sessions before November 11, 2026.
• Publish any work-in-progress you want as a branch or pull request from the Jules interface while you still can.
• Run Google’s official export prompt with an AI agent from your home folder.
• Open a few summary.md files to confirm the export is complete.
• Keep env-variables.json private and out of every repository.
• Recreate scheduled tasks and environment variables in your next tool.
• Move repository memories into your new agent’s instructions.

FAQ

Will my code disappear when Jules shuts down? No. Google says your code, branches and pull requests already live in GitHub and stay there. The shutdown affects only what is stored inside Jules.

Can I still export after November 11? Google’s notice says Jules becomes read-only after November 11 and winds down on December 31, but it does not say how long the export will keep working during the read-only period. Export before November 11 to be safe.

Do I need to know how to code to export? No. You paste Google’s prompt into an AI coding agent, sign in once in the browser when asked, and the agent does the rest. You do need Node.js and npm on your computer, and you should read and approve the commands the agent asks to run.

Does the export include my GitHub repositories’ code? No. It includes the list of connected repositories and each session’s code patches. The repository code itself stays in GitHub.

Can I use Antigravity Remote Agents on a free plan? Antigravity Remote Agents, the closest match to how Jules worked, are only for Google AI Pro and Ultra subscribers on personal accounts, according to Google’s docs. They are not available on the free plan or on Google AI Plus.

Why is Google shutting Jules down? Google’s notice says it is “part of our work to unify our agentic coding efforts”, with Jules’s lessons going into Antigravity. The notice gives no other reason.