What’s confirmed. Users have until November 11, 2026 to finish sessions, and December 31, 2026 is the shutdown date in Google’s wind-down notice. After November 11, Google says it will switch Jules to read-only for the rest of the year.
What to save. Account settings, environment variables, scheduled tasks, repository connections, memories and setup scripts are included in Google’s local export. Session records include prompts, plans, activity logs and code patches.
Code, branches and pull requests remain in GitHub, Google says. The export saves the settings and history held inside Jules.
What to do. Google’s notice says to install Jules Tools and sign in first. The exact commands and the export prompt are in that notice, so copy them from there rather than from a summary.
Before exporting, list unfinished tasks, project instructions and decisions you would struggle to reconstruct. Compare the saved folder with that checklist and open several sessions to check the handoff. Keep the archive somewhere you control, and review its contents before sharing it.
Why it matters. Google launched Jules in December 2024 and now plans to fold what it learned into its Antigravity coding platform, The Verge reports. The goal is one tool that mixes remote background tasks with an agent-first coding environment.
Write a short archive index linking unfinished changes to their session records. Keep the original export alongside review notes so the handoff remains easy to trace.
What’s real here: New Jules work stops after November 11. The remaining job is to preserve and check its settings and history before December 31. GitHub retains the code, but that does not replace the Jules archive. Assign an owner and verify that another teammate can find the records needed to continue unfinished work.
Sources
By Willa Ravenwire · The AI Bandwagon
