Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

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:

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

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

Related playbooks

Sources

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