Google Jules shutdown: read-only Nov 11, gone Dec 31

Google is shutting down Jules, its asynchronous coding agent. The Jules shutdown was posted on October 29: you can keep running sessions until November 11, 2026, the product goes read-only after that, and it winds down for good on December 31, 2026. If Jules runs scheduled tasks against your repos, you have less than two weeks of working time left.

What actually happened

The notice is a "Jules Turndown" entry on the official Jules changelog. Google says the move is part of its work "to unify our agentic coding efforts." The key dates:

• Until November 11, 2026: you can keep working and finish open sessions.
• After November 11: Jules is read-only through the end of the year.
• December 31, 2026: Jules winds down.

Google says lessons from Jules are shaping its other products, naming Antigravity, its agent-first platform. The notice does not name a direct migration path. It also says nothing about refunds or billing for paid plans, so check your account if you pay for one.

Your code is safe. Branches and pull requests already live in GitHub and stay there. What does not live in GitHub is everything Jules learned: account settings, environment variables, scheduled tasks, connected repos, memories, setup scripts, and full session history with plans, activity logs, and patches. Google gives an export path for that: install the CLI with npm install -g @google/jules, run jules login, then paste the export prompt from the changelog into a CLI coding agent. The output is a local folder.

This is Google's second coding-tool exit in a month. On October 9 it stopped selling Gemini Code Assist and pointed teams at Antigravity too.

Why the Jules shutdown matters for your business

Async agents collect context nobody writes down: the setup script that makes the tests pass, the env vars, the nightly dependency task. When the agent closes, that context goes with it unless you pull it out.

1. Export before November 11. Read-only might still let you export, but don't bet your setup scripts on it.
2. Move the useful parts into the repo. Setup scripts go in scripts/. Rules and memories go in AGENTS.md or CLAUDE.md. Any agent can read those.
3. List your scheduled tasks. Each one is a job that stops on November 11. Rebuild them in CI or in your next agent before then.
4. Run a real bake-off. Antigravity is Google's answer. Test it against Claude Code, Codex, and Copilot on your own repos before you commit.

Sources: Jules changelog: Jules Turndown, Google Cloud: Gemini Code Assist release notes.