Jules Shutdown: Export Your Data Before 11 November

Anyone with half-finished work in Google’s Jules has 12 days left to complete it: the Jules shutdown starts with a read-only switch after 11 November, and the coding agent closes for good on 31 December. Google announced the timetable in a Jules changelog notice titled “Jules Turndown” on 29 October, alongside a tool for exporting everything users have stored in the service.

The closure is less about Jules than about where Google wants its coding agents to live. The company calls the move “part of our work to unify our agentic coding efforts”, and the official Jules account on X said Google is bringing what it learned into Antigravity, its agent-first development platform. For users, the practical question is what to save, because nothing in Google’s notice says their Jules history will follow them there.

In brief

Jules runs normally until 11 November, then turns read-only and winds down on 31 December.
Code, branches and pull requests stay in GitHub; settings, memories, setup scripts and session history must be exported.
Google has not said when Jules-style background tasks will reach Antigravity, or what happens to data left in Jules.

The Jules shutdown runs in two stages

Until 11 November, Jules works as before and users can keep “finishing up sessions”, the changelog says. After that date Google will turn Jules “to read-only until the end of the year”, so past sessions stay visible but no new work can be started. The service winds down on 31 December. The notice gives no time of day or time zone for either date, so it is sensible to finish a day early.

Google launched Jules in December 2024, as The Verge noted when it reported the sunset. In its notice Google describes the tool as “an experiment to learn how asynchronous coding agents could help you tackle your backlog and ship faster”: you handed it a task against a GitHub repository and came back later to a plan, a diff or a pull request.

How to export with Jules Tools

Work that Jules has already pushed is safe. “Your code, branches, and pull requests already live in GitHub, so they stay where they are,” Google says. What lives only inside Jules is the configuration and history around that code: account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and every session with its prompt, plan, full activity log and code patches.

To save it, Google tells users to install Jules Tools, its command-line client, with npm install -g @google/jules, then sign in with jules login. The next step is unusual. Rather than a download button, the notice asks users to open a command-line coding agent, “such as Claude Code”, in their home directory and paste in a long export prompt, which runs a Python script. The output lands in a folder called ~/jules-export, with a readable summary.md and the diffs for each session.

Two warnings in the notice matter most. The file env-variables.json holds the actual values of users’ environment variables, so Google says to keep the export folder private and out of any repository. And GitHub must be connected to Jules first, or the export will contain no repository data. The prompt itself admits the script relies on internal endpoints that are “undocumented”, so it is worth running before the read-only switch rather than in the last week of December.

What Google Antigravity is meant to absorb

Google’s own phrasing is careful. “We’re working on bringing our learnings from Jules into @antigravity so you get the best of both worlds: autonomous remote background task execution and an agent-first development environment,” the Jules account posted. Neither the post nor the changelog gives a date for that feature, a migration path or any way to import a Jules export into Antigravity.

Antigravity itself is moving quickly. TSN covered its launch as an agentic IDE and DeepMind’s use of an Antigravity agent in drug discovery research. On the same day as the Jules notice, Google launched a Plugin Marketplace in Antigravity, a directory of Google-built and third-party plugins for its app and command-line tool.

A shutdown notice that points users to a rival’s agent

This is TSN’s analysis. Consolidation makes sense on paper. Google has been running overlapping coding products, and Jules’s main idea, an asynchronous coding agent you send off to work in the background, is exactly what Google now says it wants inside Antigravity. Folding the lessons into one platform is tidier than maintaining both, and the Plugin Marketplace launched the same day suggests where Google’s effort now goes.

The way Jules is being closed is more revealing. Google’s recommended route out is to hand the job to a command-line agent and name Anthropic’s Claude Code as the example, not Antigravity. That is pragmatic, since the export is a script that any capable agent can run, but it underlines that there is no in-product path from Jules to its successor. Memories and setup scripts, the context that makes an agent useful on a particular repository, leave as JSON files, and users will have to rebuild that context by hand wherever they go next.

There is also a lesson about where agent context should live. Code and pull requests survive because they were always in GitHub. Everything that existed only in Jules needs rescuing. Teams adopting any hosted coding agent can reduce the next migration’s cost by keeping setup scripts, test commands and standing instructions in the repository itself. TSN’s guide to choosing an AI assistant listed Jules among Google’s coding options only three weeks ago.

What to check before 11 November

The timetable is generous next to some recent closures. The Browser Company gave Arc users two months before its Arc browser shutdown on 22 December, and Deno gave six months’ notice when it said Deno Deploy would shut down. Jules users get about seven weeks of read-only access, but only 12 days of working time.

The open questions are the ones Google has not answered: whether data left in Jules is deleted after 31 December, and when Antigravity will run remote background tasks. Until Google dates that feature, the export folder is the only part of Jules users can be sure of keeping.