What to use after Google Jules shuts down

Jules goes read-only, then shuts down on December 31, 2026. Covers exporting tasks, memories, and schedules, and how the replacements compare.

Quick answer

Google Jules shuts down on December 31, 2026. Under Google's October 29 notice, sessions could be finished through November 11, 2026; after that Jules is read-only. Export your settings, memories and schedules now, then pick a replacement by where your team asks for work. Nori fits teams that want Slack requests, cron schedules, webhooks and shared memory on any harness, including Gemini CLI, paid with accounts they already hold.

What Google announced, and the dates that matter

The facts below come from the Jules changelog, read on November 11, 2026.

Google Jules shutdown timeline, as of November 2026.
Date	What happens
October 29, 2026	Google publishes the shutdown notice
Through November 11, 2026	Existing sessions can be finished
After November 11, 2026	Jules is read-only
December 31, 2026	Jules shuts down

The notice says the export includes settings, memories and schedules. Whether anything else is exported, and whether data can be retrieved after December 31, is not documented in the pages we read. Treat December 31 as the last day you can get anything out.

Jules' earlier task-quota pricing on its usage limits page is historical. It is not a basis for comparing replacements, so this page does not restate it.

What you need to replace

A team that relied on Jules loses three things, and a replacement should be judged on each one separately.

A cloud place to run tasks. Work that ran without a laptop needs a new sandbox.
Schedules. The notice does not say that scheduled jobs keep running once Jules is read-only, so assume they do not. These are the urgent ones.
Memories and settings. What the agent had learned about your repositories needs a new home that the whole team can read and correct.

If you also want the Gemini models to keep doing the work, check harness support. Nori runs Gemini CLI as a first-class harness, next to Claude Code and Codex, so a team can keep its Google model account and still change platform.

Replacement options compared

Replacement options for Google Jules, as of November 2026. Vendor facts were read from each vendor's own pages on November 11, 2026; follow the links for plan and rollout conditions.
Option	Cloud execution and ways in	Schedules and events	Inference and price
Nori	Isolated cloud sandbox per session, started from Slack, Discord, the web or the CLI. Runs Jiro, Gemini CLI, Claude Code, Codex or any ACP agent	Cron schedules, one-time reminders and webhooks, with run history and approval paths	Your own subscription, API keys or LLM gateway; Nori never charges for tokens. 30-day free trial, Developer $99/month, Team from $250/month
Google Antigravity	Remote Agents are Google-hosted and rolling out to personal Pro and Ultra accounts, not Workspace or Cloud business accounts. Remote Control depends on your own running machine	Not documented	See Antigravity pricing
OpenAI Codex Cloud	Cloud workspaces with published reusable environments and Slack delegation	Cloud Team Tasks support schedules and events; desktop tasks need a running host	Plus $20/month; Business $20/user annual-billed or $25 monthly, two-user minimum. API-key access does not include cloud features
GitHub Copilot cloud	Cloud execution with Slack and Teams	Native automations	Paid plans begin at Pro $10/month; Business $19/seat/month. Actions compute is separate
Claude Code cloud	Anthropic-hosted; customer-run environments are a public beta for Team and Enterprise	Cloud schedules, API and GitHub triggers are a research preview	Pro $20/month, Max $100, Ultra $200; Team standard $25/month or $20 annual-billed per seat
Cursor cloud agents	Cursor-hosted, or self-hosted workers that execute tools while Cursor keeps planning and inference	Native automations include schedules and app events	Premium $30/month, Super $100, Ultra $200; the Free and $8 Plus plans exclude cloud agents

None of these vendors documents an importer for a Jules export in the pages we read. Plan to move schedules and memories by hand; the steps below show how. For a wider field, see cloud coding agents compared.

When to choose Nori

Your Jules tasks came from a team, and you want requests and results in a Slack thread that anyone can pick up.
You had recurring Jules jobs and want them back as cron schedules with run history and an approval step.
You want what Jules remembered to become shared memories and an org skillset that every session and every teammate uses.
You want to keep using Gemini models through Gemini CLI, or mix in Claude Code and Codex, without a second migration later.
You want inference billed to accounts you already hold, with no token charge from the platform.
You need the control plane in your own cloud. Nori deploys the full stack, control plane included, into your AWS VPC or Azure VNet, or on-prem; hosted customers get a dedicated, single-tenant control plane.

Nori also ships Jiro, a ready-to-work AI engineering teammate, for teams that would rather not assemble their own agent setup after losing one.

When to choose a single-vendor agent

Google Antigravity if you are an individual on a personal Pro or Ultra account and want to stay with Google. As of November 2026 Remote Agents are not available to Workspace or Cloud business accounts.
OpenAI Codex Cloud if the team already pays for ChatGPT Business and is happy with one vendor's harness.
GitHub Copilot cloud if work starts and ends in GitHub and you accept that Actions compute is billed separately.
Claude Code cloud if you are standardizing on Anthropic and can build on features labelled research preview.
Cursor cloud agents if your engineers already live in Cursor on a Premium plan or higher.

Each of these is a reasonable choice for the right team. The risk Jules just demonstrated is the one to weigh: when the agent, the schedules and the memory all belong to one vendor's product, a product decision by that vendor becomes your migration.

How to migrate off Jules before December 31

Export today. Run the Jules export and store the result in a repository or shared drive the team controls. The notice says it includes settings, memories and schedules.
List every schedule. For each one write down the repository, the prompt, the cadence and who reads the output. Assume none of them runs while Jules is read-only, and sort by how soon someone will notice.
Sort the memories. Split them into rules (always run make lint before pushing), facts (the payments service owns the ledger tables) and stale entries. Delete the stale ones.
Load the context into the new platform. On Nori, rules go into the org skillset's AGENTS.md, facts become shared memories, and repeatable procedures become skills.
Recreate the schedules. One automation per Jules schedule, each with a destination channel. See the worked example below.
Run each job once by hand. Trigger it, read the pull request or summary, and fix the prompt before trusting the schedule.
Close out Jules. Before December 31, confirm the export is complete and readable, then remove any repository access you granted to Jules.

Worked example: one schedule moved to Nori

A Jules job that updated dependencies every Monday becomes a Nori automation with three fields.

Schedule:     0 9 * * 1          (Mondays 09:00, team time zone)
Repository:   web-app
Post to:      #eng-maintenance
Prompt:       Update minor and patch dependencies in web-app.
              Run the full test suite. Open one pull request per
              package group. If a test fails, do not open the PR;
              post the failing test name and the package instead.

The same request works ad hoc in Slack: @nori run the Monday dependency update for web-app now. Both runs appear in one history. More patterns are in scheduled coding agents.

Frequently asked questions

When does Google Jules shut down?

Google's October 29, 2026 notice sets the shutdown for December 31, 2026. Sessions could be finished through November 11, 2026, and Jules is read-only after that date. Export what you need well before the end of December.

What can I export from Jules?

The notice says the export includes settings, memories and schedules. Whether other data is included is not documented in the pages we read, so run the export early, open the result, and check that it holds what your team needs before the shutdown date.

Can I import a Jules export into another agent?

No vendor in this comparison documents an automatic importer in the pages we read. Plan a manual move: turn rules into instruction files, facts into shared memories, and each schedule into a new automation.

Can I keep using Gemini models after Jules?

Yes. Nori runs Gemini CLI as a harness in cloud sandboxes, using your own Google model account or API key, alongside Claude Code and Codex. Google Antigravity Remote Agents are another route for personal Pro and Ultra accounts, though not for Workspace or Cloud business accounts.

Is Google Antigravity the official replacement for Jules?

The sources we read do not establish that. They document Antigravity Remote Agents as Google-hosted and rolling out to personal Pro and Ultra accounts, not Workspace or Cloud business accounts. Teams on business accounts should check availability before planning around it.

What does Nori cost for a team moving from Jules?

Nori has a 30-day free trial with no card. Developer is $99 per month for one person and three machines. Team starts at $250 per month for five machines with unlimited members. Model usage is paid to your own provider; Nori never charges for tokens.

Sources

Vendor pages were read on November 11, 2026. Dates, prices and preview labels change; check the linked pages before you decide.