Disclosure: GearPicked is reader-supported. Some links on this page are affiliate links; if you buy through them we may earn a commission at no extra cost to you. This never changes what we recommend. As an Amazon Associate, GearPicked earns from qualifying purchases. Read our affiliate disclosure.

How to Export Google Jules Data Before It Goes Read-Only (11 Nov 2026)

By Balwant Singh Rawat · Published 5 November 2026 · Updated 8 November 2026· Research-based (not yet hands-on tested)

If you still use Google Jules, the clock matters. After 11 November 2026 Jules turns read-only; it winds down on 31 December 2026 (Jules changelog). As of 8 November 2026 that is about three days of normal use. This page is the export checklist. For Antigravity cloud setup after you export, see Google Antigravity Remote Agents setup. For other replacements, see Best Google Jules alternatives.

When do I need to export by?

Google has not said whether the export CLI keeps working after read-only starts. The safe move is to export before 11 November, especially if you rely on scheduled tasks.

What gets exported, and what stays on GitHub?

Google: you can export account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and every session, including its prompt, plan, full activity log, and code patches. Separately: Your code, branches, and pull requests already live in GitHub, so they stay where they are.

Before you export, merge or close open Jules pull requests you still care about, and finish any session you still need to run.

How do I install Jules Tools and sign in?

From Google’s notice:

npm install -g @google/jules
jules login

jules login opens a browser sign-in — run it yourself in a terminal. If you used Jules with GitHub, confirm the connection:

jules remote list --repo

If that fails with a 401 about GitHub, connect the account at the Google Labs Jules GitHub app URL that Google’s export prompt lists (github.com/apps/google-labs-jules/...), then retry. If you never pointed Jules at a repo, you can skip that step; the export will simply have no repository data.

How do I run the official export?

1. Open Google’s Jules Turndown changelog and expand Show the export prompt.
2. From your home directory, open a CLI coding agent (Google names Claude Code as an example).
3. Paste the entire prompt. It tells the agent to check the CLI, confirm login, save Google’s export script, run it, report counts, and not print your access token or env-var values.
4. Wait for the counts and the folder path.

Google says the data lands in ~/jules-export (connected repos in sources.json, per-repo memories and setup scripts, settings / env vars / scheduled tasks as JSON, and per-session summary.md, activity logs and diffs).

Practical warnings from Google’s own prompt

• The access token expires about an hour after login; 401s on every call mean run jules login again.
• The script uses undocumented endpoints; if a call returns 404/400, note which one rather than guessing.
• Seeing a few more sessions than jules remote list --session shows is expected.

We are not republishing Google’s full Python script here — use the live copy on the changelog so you get any updates.

What does the export folder look like?

Google describes this layout (names from the changelog):

~/jules-export/
  user-settings.json
  env-variables.json      # treat as a secret
  scheduled-tasks.json
  sources.json            # connected repositories
  sessions.json
  repos/<id>/             # memories, setup.sh, test-command.txt when present
  sessions/<id>/          # summary.md, activities.json, patch-*.diff

An empty repos/ subfolder is not automatically a failed export — memories and setup scripts only appear when Jules had them.

How should I secure env-variables.json?

Google: env-variables.json contains your environment variable values, so keep the export folder private and out of your repositories.

Suggested hygiene (ours, not Google’s):

1. Add jules-export/ to your global gitignore.
2. Move needed secrets into your new tool’s secret store or a local .env that is ignored.
3. Rotate anything that is a real credential — those values sat with a third party and now sit on disk in plain text.
4. Delete env-variables.json once you have migrated what you need.

What should I do after exporting?

1. Rebuild scheduled tasks and memories in your next agent — if you stay in Google’s stack, follow Antigravity Remote Agents setup (exports do not auto-import); other options in Jules alternatives (Codex Cloud, Claude Code cloud sessions, Copilot cloud agent).
2. Copy useful setup.sh / test commands into your repo’s agent notes (CLAUDE.md, AGENTS.md, or equivalent) and into CI — keep them short and current.
3. Between 11 Nov and 31 Dec 2026, spot-check a few sessions in the read-only Jules UI against their summary.md files while you still can.
4. Related academic shutdown guide: OpenAI Prism → LaTeX alternatives.

Export checklist

• Merge or close open Jules PRs; finish sessions you still need
• npm install -g @google/jules and jules login
• Confirm GitHub connection if you used repos
• Run Google’s live export prompt from your home directory
• Keep ~/jules-export out of git; rotate credentials in env-variables.json
• Map setup / memories / schedules into your next tool
• Spot-check against Jules before 31 Dec

How we’ll verify

Related: Google Antigravity Remote Agents setup · Best Google Jules alternatives · OpenAI Prism shutting down: LaTeX alternatives · All AI tools