Google Jules shutdown: key dates and how to export data

Google is shutting down Jules, its asynchronous coding agent. You have until November 11, 2026 to finish any open sessions. After that Jules goes read-only, and it closes for good on December 31, 2026. Your code, branches and pull requests already live in GitHub, so they aren't affected. What you do need to export is everything stored inside Jules: settings, environment variables, scheduled tasks, repo memories and session history.

The news came Thursday afternoon from the official @julesagent account. The post calls Jules an experiment that taught the team "where agentic development is headed," and says its lessons are going into Google Antigravity. The key line: "As we focus on this unified experience, Jules will be winding down." Within a few hours it had roughly 80,000 views and over 100 quote posts.

What Google is replacing Jules with

The official notice is a changelog entry titled "Jules Turndown". It says the move is "part of our work to unify our agentic coding efforts," and names Antigravity as the agent-first platform that gets Jules' ideas. The X post puts the goal plainly: background tasks that run remotely, inside an environment built around agents.

Antigravity's site currently lists four pieces: a desktop app for running several local agents in parallel, a CLI with background subagents, a full IDE, and an SDK. There's a $0 individual tier with "basic weekly rate limits." Google AI Pro and Ultra subscribers get higher limits, and business seats through Google Cloud start at $30 a month. Ultra was also the only plan that got Gemini 4 Argon inside Antigravity when it launched, as we covered in is Gemini 4 Argon free.

Google hasn't said anything about migration tooling, refunds, or how long the Jules API keeps working. The changelog doesn't mention any of them.

How to export your Jules data

Google's export method is unusual: it gives you a prompt and expects your own coding agent to do the work. Here's the process from the changelog:

1. Install Jules Tools and sign in: npm install -g @google/jules, then jules login. Login opens a browser window, so run it yourself.
2. From your home directory, open a CLI coding agent. Google names Claude Code as an example.
3. Copy the full export prompt from the changelog page and paste it in. The agent checks that the CLI is installed and logged in, saves Google's Python script, runs it, and reports the counts.
4. If the repo step fails with a 401 and asks about GitHub, connect your GitHub account to the Google Labs Jules app (the prompt includes the link), then run it again. If you never connected repos, you can skip that step.

The script saves everything to a jules-export folder:

Two warnings from Google's own notes. First, env-variables.json holds real secret values, so keep that folder private and out of any repository. Second, the script calls endpoints that Google calls undocumented. If one starts returning 404s, the export breaks, so do it this week, not in late December. The access token also expires about an hour after login. If every call comes back 401, sign in again.

Where to run those tasks now

Memories and setup scripts are the useful part of the export. They record what the agent learned about each repo, and you can move them into whatever comes next. Antigravity is Google's answer. Outside Google, Anthropic's Claude Code Projects keeps cloud agents running after you log off, and Cursor now lets you build and deploy your own agents.

Our read

No benchmark tells you whether a tool will still be around next year. Back in November 2025, @GergelyOrosz said that with dev tools, Google "keeps abandoning them / seems to have no coherent strategy," and listed Jules as one that already felt abandoned. Eleven months later, it's closing.

For a business, the lesson is to keep the valuable pieces somewhere you control. Prompts, repo instructions, setup scripts and task history should live in your own files and your own Git history, not only inside a vendor's dashboard. Then switching agents takes an afternoon instead of becoming a rebuild. If you're unsure which of your workflows depend on a single AI tool, New Face Design's free process audit maps that out and shows you what to move first.