Plan around the work cutoff first
Google's October 29 notice gives Jules users two deadlines: finish sessions by November 11, then use a read-only period before the service winds down December 31, 2026. The company links the closure to consolidation of its coding-agent work and mentions Antigravity, but does not describe an automatic migration.
The announcement does not specify a cutoff hour, timezone, country exception or refund policy. Teams should avoid treating the final calendar day as a guaranteed working window.
Preserve the service record as well as the code
Google says GitHub retains code, branches and pull requests. Its export procedure separately saves Jules settings, environment variables, scheduled tasks, repository connections, memories and session records. The notice warns that exported environment-variable values require private storage.
The CLI reference documents repository and session listing, browser-based Google sign-in and retrieval of completed session results. Those commands can help users inventory outstanding work, but a list of sessions is not the same as a checked archive.
Check what a replacement must actually support
CGH perspective: assign an owner to each unfinished session and compare its output with the corresponding GitHub branch or pull request. Review exported files locally, record missing items and keep sensitive configuration away from public repositories. A completed download should be followed by a small restoration check.
Before moving recurring work, inventory its triggers, repository access and required secrets. Recreate only the permissions the replacement needs, and test one representative task before expanding it. The reviewed notice supplies neither a migration compatibility promise nor replacement pricing. CGH has not run the export or tested a transfer to another coding agent.