What should you do after Google shuts down Jules? Remember two dates first: from 11 November 2026, Jules becomes read-only — you can view things but cannot create new tasks or continue work; on 31 December 2026, the service shuts down completely. Google announced this plan on 29 October 2026, because it is concentrating its agent coding capabilities in the Antigravity platform. Sessions that are not finished need to be wrapped up before 11 November.
Step 1: Wrap up and export
First, finish your in-progress sessions: merge changes already produced into the code repository or save them as a branch, because code and pull requests already live on GitHub and will not disappear when Jules closes. Then export settings, session history, scheduled tasks, and repository connections — Google provides an export route; exported files may contain environment variables and secrets, so keep them somewhere you control and do not casually send them to group chats or public repositories. In the read-only period you can still view old content, but you cannot have it do more work, so do not leave the export until December.
Step 2: Rebuild in Antigravity
There is no automatic migration in Antigravity: Jules sessions and settings do not move over by themselves. Open the same repository, rebuild the previous configuration and instructions, run a small task first and confirm the output matches expectations, then move scheduled tasks across. Google says it is bringing the lessons of Jules background execution into Antigravity, but has published no timetable for when the full capabilities will arrive, so do not assume Antigravity already fully covers the “close the laptop and the task keeps running in the background” workflow — verify it with small tasks before relying on it.
When you need a different tool
If you depend on tasks running in the cloud to completion with the computer switched off, evaluate other cloud agent tools before Antigravity is verified, rather than betting scheduled work on a feature whose date has not been announced. If you only fix small problems occasionally, Antigravity's local development environment plus small-task verification is enough; the migration then comes down to three steps: export, rebuild, verify.
