Playbooks · Coding tasks
Google Jules ends Nov 11: export your work
Written November 7, 2026
Jules goes read-only Nov 11 and shuts down Dec 31. Finish your sessions, export everything, and don't wait for Antigravity — there's no import path yet.
The dates
Google's Jules turndown notice, dated October 29, 2026, gives three dates. You can run sessions until November 11, 2026. After November 11, Jules turns read-only until the end of the year. On December 31, 2026, it winds down. Google gives no time of day for either cutoff, so treat November 10 as the real deadline: finish work and run the export while sessions can still run and while you can still fix a gap the export reveals.
Your code is not the thing at risk. Code, branches, and pull requests already live in GitHub, and they stay there. What lives only in Jules is the configuration and history around the code: settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and sessions. That is the part with no other copy, and the export is the only way to get it out.
Export first
Google's export route is Jules Tools plus a supplied export prompt. Install and sign in:
npm install -g @google/jules # then sign in: jules login
Connect GitHub first if you use Jules with GitHub, or the export will not include repository data. Then, from your home directory, open a command-line coding agent and paste in the export prompt from the notice. The prompt tells the agent to check the setup, run the export, and report what it saved: the counts it prints, and the full path of the folder. The export lands in ~/jules-export and covers settings, environment variables, schedules, repository connections, memories, setup scripts, session prompts, plans, logs, and patches.
Keep the export folder private and out of your repositories. The environment variables file contains your environment variable values. Treat the whole folder the way you would treat a file of secrets: no commits, no pastes into chat logs, no shared drives.
Check the export before you trust it
A folder that exists is not a folder that is complete. Open it and match what is inside against the list in the notice:
- Account-level files: settings, environment variables, and scheduled tasks, each saved as JSON.
- One folder per connected repository holding its setup script, its test command, and its memories, with a readable memories file alongside the JSON.
- One folder per session holding a readable summary, the full activity log, and the session's diffs.
- The counts the agent printed when the export ran: numbers of repositories, sessions, and patches. Compare those counts with the folders on disk. A count that says twelve sessions and a folder holding eleven means one session did not export.
Open two or three session folders all the way through: summary, activity log, and at least one diff. A summary with no diff behind it, for a session you know produced code, is a gap to chase while Jules can still run. Also open the scheduled tasks file and read each task's prompt and schedule. That file is the raw material for rebuilding each recurring task wherever it runs next. If a task is missing from it, it will not be rebuilt from memory later.
One more caution, from a reading of the published exporter: its session count measures the sessions listed, even when fetching a session's details fails. It reports errors separately. A completion message proves less than a folder whose contents you have opened and matched. If an important record is missing, recover it while you still have access.
What has no answer yet
- No automatic import into Antigravity. Google says what it learned from Jules is shaping products across Google, including Antigravity, and its announcement says it is working to combine remote autonomous background execution with Antigravity's development environment. It supplies no delivery date for that combination, and no step in the notice loads an export into another product.
- No date for Jules-style background tasks in Antigravity. Antigravity already runs scheduled tasks, under the Automations tab, but the notice gives no date for remote background execution of the Jules kind there. Build on what Antigravity offers now, and re-check its changelog if the feature you need arrives later.
- No cutoff hour, time zone, or refund statement. The notice specifies no cutoff hour, no time zone, no separate API deadline, and no billing or refund date. Treat those as unanswered questions, not dates to infer from the table above.
- Session history is a record, not a state. The summaries, activity logs, and diffs are a record to read, not something another tool can resume. A session that was mid-work on November 11 needs its remaining work restated as a new task, with the exported diff as the starting point.
Where the work goes next
There is no automatic move, so choose the runtime before choosing the agent. The options are covered in the Jules alternatives guide: Antigravity's remote agents for staying with Google, GitHub Copilot's cloud agent for work that already lives in GitHub, Claude Code on the web or Codex Cloud for a hosted task queue, or your own Claude Code or Codex on a machine you operate. For each Jules scheduled task, rebuild it by hand from the prompt and schedule in the export, run the replacement once, and read what it did before trusting it to run on its own. Waiting past November 11 for a feature with no date leaves you with a read-only Jules and no export left to fix.
Limits
- This page follows the export path in Google's turndown notice. If that path errors, the notice's own advice is to report the error as-is. This page does not offer a second export path.
- No Jules account was available to this site, so no export was run here. The steps above are the notice's steps, not a report of an export performed for this page.
- November 11 is the read-only date, not the shutdown. December 31 is the shutdown. This page does not present November 11 as the end of the service.
Related playbooks
- Export Jules work and rebuild scheduled tasks before the shutdown
- Agent Builder shuts down Nov 30: export now
- Antigravity removes free Claude models Nov 18
- Claude Code hardens its sandbox ahead of Nov 10
Sources
- Changelog, including the Jules Turndown notice — Jules
- Google Jules alternatives — Prized
- Google Jules Shutdown: Export and Migration Guide — Omid Saffari
Back to: Coding playbooks hub · Also: Agent change deadlines: retirements and shutdowns · Export Jules work and rebuild scheduled tasks before the shutdown · November shutdowns: Runloop, Conductor, Moondream