Jules is read-only after November 11. What to do now, and where to go next

What Google announced

On October 29, 2026, Google posted a notice titled “Jules Turndown” in Jules’s changelog: “as part of our work to unify our agentic coding efforts, Jules will wind down on December 31, 2026. You have until November 11, 2026 to continue finishing up sessions. After November 11, 2026, we will be turning Jules to read-only until the end of the year.”

November 11 has passed, so under that notice Jules is now read-only. Google hasn’t added to it: on November 12, the notice was still the newest entry in the changelog, and Jules’s homepage, docs and usage page still don’t mention the shutdown.

Date	What Google said
October 29, 2026	Jules will wind down, and you can export your data
November 11, 2026	The last day to finish sessions
After November 11, until December 31	Jules is read-only
December 31, 2026	Jules winds down

Jules launched on May 19, 2025 and left beta that August, according to its changelog. It cloned your GitHub repository into a cloud VM, made a plan for you to approve, did the work and helped you open a pull request, and its docs said you were “free to leave Jules while it is running.”

Google’s notice says what Jules taught it is “shaping products across Google, including our agent-first platform, Google Antigravity.” The Jules account went further on X: “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.” Neither gave a date for that. Then on November 3, Antigravity’s changelog said “Remote agents are starting to roll out to Google AI Ultra and Pro subscribers,” and on November 9 it said they had finished.

Who it affects

Everyone who used Jules, on any plan. Its usage page still lists three: Jules, free, with 15 tasks a day; Jules in Pro, included with Google AI Pro, with 100; and Jules in Ultra, included with Google AI Ultra, with 300.

It also reaches the ways in that aren’t the website. The Jules homepage still offers a “jules” label for assigning a task from a GitHub issue, the Jules Tools CLI and the Jules API. The notice doesn’t treat any of them separately, and Google’s API page still says “The Jules API is in an alpha release,” with no shutdown notice. Google hasn’t said whether they went read-only with the website. Plan on all of them ending with Jules.

If you pay for Google AI Pro or Ultra, nothing in the notice changes your plan. Google’s plans page lists Antigravity for coding and doesn’t mention Jules, with Google AI Pro at $19.99 a month and Ultra at $99.99 or $199.99.

How to export your Jules data

Google’s notice gives the export no deadline, and Google hasn’t said whether it still works now that Jules is read-only. If you haven’t exported yet, try it now. If a call fails, the prompt asks your agent to tell you which one “rather than guessing at fixes.”

The export covers what lives inside Jules: account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and every session, “including its prompt, plan, full activity log, and code patches.” In Google’s words, “Your code, branches, and pull requests already live in GitHub, so they stay where they are.”

1. Connect GitHub first, if you used Jules with repositories. Google warns that otherwise “the export won’t include repository data.”
2. Install Jules Tools and sign in: npm install -g @google/jules, then jules login.
3. Open a CLI coding agent from your home directory, “such as Antigravity CLI,” and paste the export prompt from Google’s notice. The agent checks your setup, saves and runs a Python script, and tells you what it saved.
4. Check ~/jules-export. It holds sources.json, a folder per repository with its setup script, test command and memories, your settings, environment variables and scheduled tasks as JSON, and a folder per session with a summary.md, the activity log and its diffs.

Read the script before your agent runs it. It reads your Jules sign-in from the macOS Keychain or Linux’s secret store, and the prompt warns that the endpoints it calls “are undocumented.” Its output includes secrets: “env-variables.json contains your environment variable values, so keep the export folder private and out of your repositories.”

Where Jules’s work can go

Jules’s model, a repository in a cloud VM ending in a pull request, is what three other companies sell today. Google’s own pick, Antigravity, now offers something close: its remote agents run in an “isolated, Google-managed remote environment” where “no local machine needs to stay on,” and clone the GitHub repositories you attach. Antigravity’s changelog says that on November 9 they “finished rolling out to Google AI Ultra subscribers and to Google AI Pro subscribers on a paid plan,” though their page still says the feature “is rolling out gradually.” They aren’t available “on the free plan, on Google AI Plus, or for business accounts (Google Workspace or Google Cloud),” and the page doesn’t mention pull requests, issue labels or how they count against your quota.

Option	Where it runs	Plan it needs	Scheduled jobs
Google Antigravity	On your computer; in Google’s cloud on Ultra and paid Pro plans	Free weekly quota; Google AI Pro, $19.99 a month, for more and for remote agents	Automations, alongside the app
Codex Cloud	OpenAI’s cloud	ChatGPT Plus, $20 a month	ChatGPT scheduled tasks
Claude Code cloud sessions	Anthropic’s cloud	Claude Pro, $20 a month or $17 billed yearly	Cloud scheduled tasks
GitHub Copilot cloud agent	GitHub’s cloud sandboxes	Copilot Pro, $10 a month; sandbox time billed once your GitHub plan’s included compute runs out	Copilot Automations, private and internal repositories only

Google Antigravity is the successor Google names. Its models page gives a paid Google AI Pro plan Gemini 4 Argon, and Ultra also Gemini 4 Carbon, which arrived on November 10. Every plan gets “Access to all product features,” and accounts without Pro or Ultra get “A meaningful quota, refreshed weekly,” says its plans page. Remote Control lets you “drive your Antigravity desktop sessions and CLI instances running across your machines from any web browser,” but the machine has to stay online and “not asleep or suspended.” Its Automations, “formerly called Scheduled Tasks,” are sidecars, “background processes that run alongside Antigravity.” On a free account, from November 18 its only model is Gemini 3.8 Flash (our memo).

Codex Cloud is on ChatGPT Plus and up, at $20 a month on ChatGPT’s pricing page: Codex pricing lists Codex on the web and its cloud-based features from Plus, and for Free and Go only GPT-6 Luna in the desktop app. Codex can check out repositories from your connected GitHub or GitLab account, and each task “has its own workspace and can keep working while your computer is asleep.” OpenAI warns that “Cloud tasks may use more of your allowance than local messages.” ChatGPT’s scheduled tasks on the web “can’t work directly in a folder on your computer.”

Claude Code’s cloud sessions come with Claude Pro, Max, Ultra and Team, and Enterprise with premium seats or Chat + Claude Code seats. Anthropic says a session “keeps running after you close your laptop,” counts toward your plan’s limits, and has “no separate charge for the cloud VM.” Its cloud scheduled tasks run hourly at most and “draw down subscription usage the same way interactive sessions do.”

GitHub Copilot’s cloud agent takes work the way Jules’s GitHub label did: the plans page says you “Assign work to Copilot to research, plan, and write code — with or without a pull request,” and lists it as “Not included” on Free. Each session runs in a cloud sandbox, “an isolated Linux environment that GitHub creates for a Copilot session.” GitHub said “Billing for cloud sandbox usage begins in November 2026”: sandbox time draws first on the compute your GitHub plan includes, and after that it’s billed by usage (our Universe memo has the rates). Automations “are available in private and internal repositories only.”

Keeping more than one agent

You don’t have to choose one. Enjoy runs Antigravity on your Google account beside Claude Code on your Claude plan and Codex on your ChatGPT plan, and lets you switch agents in the middle of a conversation. Its scheduled workflows can give any of them a recurring job, but they run while your computer is awake with Enjoy open, so they don’t replace a cloud VM that works with your laptop shut. Enjoy is a monthly subscription, with the first seven days free (pricing), and each agent runs on the plan you already have.

What to do now

• Try the export, if you haven’t. Google hasn’t said whether it still works while Jules is read-only, the script depends on endpoints Google calls undocumented, and Jules winds down on December 31.
• Save what’s left of your open work. Under the notice, sessions can’t be finished now. Copy any plan you still need into a file in the repository, and merge or close the pull requests Jules opened, which stay in GitHub.
• Move your scheduled tasks. Google hasn’t said whether they still run. Open scheduled-tasks.json and set each one up again where you’re going.
• Update what calls Jules. Scripts on the Jules API or Jules Tools, and issues that use the “jules” label, need a new home.
• Remove Jules from GitHub once the export is done and you’re finished with it. GitHub’s guide to installed apps shows where.

What Google hasn’t said

• Whether the export still works while Jules is read-only, and until when.
• Whether scheduled tasks and label-assigned tasks stopped on November 11.
• Whether the API and Jules Tools went read-only with the website, and what happens to your data after December 31.
• How Antigravity’s remote agents count against a plan’s quota, or what “a paid plan” leaves out for Google AI Pro.
• Anything about prices or refunds for Google AI Pro and Ultra.

We’ll update this memo when Google answers any of them.