Skip to content
,

Google Jules Is Shutting Down: How to Export Your Data and Best Alternatives (2026)

7–10 minutes
Surprised woman holding a Jules card in a server room with the text Jules is shutting down, for a Google Jules export guide

Google is shutting down Jules, its asynchronous AI coding agent. If you used Jules to fix bugs, write tests or open pull requests on GitHub, you need to save your data and move to another tool before the end of 2026.

Google announced the “Jules Turndown” on 29 October 2026. Jules became read-only after 11 November 2026 and will wind down completely on 31 December 2026.

This guide explains exactly what is changing, what happens to your code and pull requests, how to export everything with the official Jules Tools CLI, and which coding agents to switch to. All details come from the Jules changelog and docs, checked on 16 November 2026.

TL;DR

  • Timeline: announced 29 Oct 2026; sessions could be finished until 11 Nov 2026; now read-only; Jules shuts down 31 Dec 2026.
  • Your code is safe: branches and pull requests already live in GitHub and stay there.
  • Export the rest: npm install -g @google/jules, then jules login, then run Google’s export prompt in a CLI coding agent. Data lands in ~/jules-export.
  • What’s exported: settings, environment variables, scheduled tasks, connected repos, memories, setup scripts and every session (prompt, plan, activity log, code patches).
  • Careful: env-variables.json holds your secret values. Keep the folder private and never commit it.
  • Google’s replacement: Google Antigravity and the Antigravity CLI.
  • Other options: Claude Code, Codex, Gemini CLI, Cursor.

What Was Jules?

Jules was Google’s experimental coding agent. You connected GitHub, picked a repo and branch, described a task, and Jules cloned your code into a cloud virtual machine, wrote a plan for you to approve, made the changes and pushed a branch for a pull request.

Feature What it did
Plans Showed a step-by-step plan before writing code (“Give me a plan”)
Async work Ran in the background while you did other things
GitHub issues Label an issue “jules” and it opened a PR
AGENTS.md Read repo instructions from an AGENTS.md file
CI Fixer (Feb 2026) Auto-fixed failing CI checks on its own PRs
MCP (Feb 2026) Connected to six services via MCP with API keys
Planning Critic (Jan 2026) A second agent reviewed plans that ran without human approval
Limits Free 15 tasks/day (3 at once); Pro 100 (15); Ultra 300 (60)

Shutdown Timeline

Date What happens
29 Oct 2026 Google announces the Jules Turndown and releases the export tool
Until 11 Nov 2026 You could keep finishing existing sessions
11 Nov to 31 Dec 2026 Jules is read-only: view and export, but no new work
31 Dec 2026 Jules winds down completely

Google says Jules was always an experiment and that it is unifying its agentic coding work around Google Antigravity, its agent-first platform. As of 16 November 2026 you are in the read-only window, so export now rather than in late December.

What Happens to Your Code, PRs and Data

Item What happens Action needed?
Branches and pull requests Already in GitHub; they stay where they are No
Merged code Part of your repo No
Session history (prompts, plans, logs, patches) Lost after shutdown unless exported Yes, export
Unpushed code patches Only in Jules Yes, export and apply
Setup scripts and env variables Lost unless exported Yes, export
Scheduled tasks and memories Stop and disappear Export and recreate elsewhere
Jules GitHub app Not stated by Google Remove it from GitHub when you’re done
Subscription Jules came with Google AI Pro/Ultra; Google has not announced a Jules-specific refund Your Google AI plan continues for its other features

The export only includes repository data if your GitHub account is connected to Jules, so check the connection first.

How to Export Your Jules Data

Google’s export works through the Jules Tools CLI plus a CLI coding agent, which runs Google’s export prompt for you.

  1. Install Node.js (LTS) if you do not have it, so you have npm.
  2. Install Jules Tools: npm install -g @google/jules
  3. Sign in: jules login. A browser window opens for your Google account. Use the same account you used for Jules.
  4. Check the CLI works: jules remote list --session should list your sessions, and jules remote list --repo your connected repos.
  5. Open a CLI coding agent from your home directory, for example the Antigravity CLI. Google’s instructions name Antigravity CLI as an example; any agent that can run terminal commands can follow the prompt.
  6. Paste the export prompt from the “Jules Turndown” entry in the Jules changelog. The agent checks your setup, runs the export and reports what it saved.
  7. Find your files in ~/jules-export (on Windows, C:\Users\YourName\jules-export).

What the export contains

  • Account settings
  • Environment variables (with values) in env-variables.json
  • Scheduled tasks
  • Connected repositories
  • Memories
  • Setup scripts
  • Every session: the prompt, plan, full activity log and code patches

If you only need the code from one finished session, you can also pull it directly: jules remote pull --session SESSION_ID.

After the Export: Checklist

  1. Protect secrets: move env-variables.json somewhere private or into a password manager, and never put the export folder inside a git repo.
  2. Rotate keys: if any API keys or tokens were stored in Jules, consider rotating them once you have moved.
  3. Apply unfinished patches: review exported code patches and apply the ones you still want with git apply on a new branch.
  4. Save your setup scripts into your repo (for example a scripts/setup.sh) so any agent can use them.
  5. Keep AGENTS.md: if you wrote one for Jules, keep it; many agents read AGENTS.md or similar files.
  6. Recreate scheduled tasks in your new tool or as GitHub Actions.
  7. Remove the Jules GitHub app from your GitHub account or organisation settings when you no longer need it.

Best Jules Alternatives

Tool Type Closest to Jules because Watch out for
Google Antigravity / Antigravity CLI Agent-first IDE and CLI Google’s official direction; Gemini models; remote agents Different workflow from Jules’ web UI
Claude Code Terminal and IDE agent, plus cloud sessions Strong autonomous coding, GitHub PRs, AGENTS-style instruction files Needs a Claude plan or API
OpenAI Codex CLI, IDE and cloud agent Cloud tasks that open PRs, much like Jules Needs ChatGPT plan or API
Gemini CLI Terminal agent Free tier, Gemini models, open source Runs locally, not async in the cloud
Cursor AI code editor with background agents Agents that work while you code Editor-centred, paid plans for heavy use

Learn more in our guides: Antigravity remote agents, install Claude Code, Gemini CLI free limits and Antigravity CLI, and Claude Code vs Gemini CLI.

How to Move Your Jules Workflow

In Jules you used Do this instead
“Give me a plan” then approve Use plan mode in Claude Code, Codex or Antigravity before letting the agent edit
Labelling GitHub issues “jules” Use your new agent’s GitHub integration or a GitHub Action that triggers it
Setup scripts Commit them to the repo; point the new agent at them in its instruction file
AGENTS.md Keep it; copy key rules into the new tool’s instruction file if it uses a different name
Memories Paste the important ones into your repo instruction file
Scheduled tasks Recreate as GitHub Actions on a schedule, or your agent’s scheduler
CI Fixer Ask your new agent to read CI logs and fix failures on its PRs

Troubleshooting the Export

Problem Fix
npm not found Install Node.js LTS, then open a new terminal
jules not found after install Open a new terminal; check npm’s global bin folder is on your PATH
Login opens wrong Google account Run jules logout, sign out in the browser, then jules login again
No sessions listed You are signed in with a different account than the one you used for Jules
Repo data missing from export Your GitHub account was not connected to Jules; connect it via the Jules GitHub app first
Export folder not where expected Run the agent from your home directory; look for ~/jules-export
Accidentally committed env-variables.json Remove it from git history and rotate every secret in it

My Take

Your code is not at risk because it already lives in GitHub, but your session history, setup scripts and environment variables are. Spend ten minutes now on the export rather than finding out on 1 January that they are gone.

If you liked Jules’ “hand it a task and come back to a PR” style, Codex cloud tasks and Claude Code are the closest feel. If you want to stay with Google and Gemini, follow Google’s own pointer to Antigravity.

FAQ

Is Google Jules shutting down?

Yes. Google announced on 29 October 2026 that Jules will wind down on 31 December 2026. It has been read-only since 11 November 2026.

Will I lose my pull requests?

No. Branches and pull requests are already in GitHub and stay there.

How do I export my Jules data?

Install Jules Tools with npm install -g @google/jules, run jules login, then paste Google’s export prompt into a CLI coding agent. Files are saved to ~/jules-export.

Can I still start new Jules tasks?

No. After 11 November 2026 Jules is read-only until it closes.

What is replacing Jules?

Google points to Google Antigravity, its agent-first platform, and the Antigravity CLI.

Will I get a refund?

Google’s announcement does not mention refunds. Jules was included in Google AI plans, which keep their other features.

Is my exported data safe?

It is saved on your own computer, but env-variables.json contains secret values, so keep the folder private and out of any repository.

Sources

Free weekly email

Get new AI guides every week

One short weekly email with our newest local AI, ComfyUI and AI tool guides. No spam, no pop-ups, just the good stuff.

Free. Unsubscribe anytime in one click. We only use your email to send this newsletter. See our privacy policy.

Surprised woman holding a Jules card in a server room with the text Jules is shutting down, for a Google Jules export guide