Google said on Oct. 29 that Google Jules changelog will stop active Jules sessions after Nov. 11, shift the service to read-only access through Dec. 31, and wind it down at year-end.
The practical issue for teams is that GitHub is not the full backup. Google published an export path for Jules-side data including settings, environment variables, scheduled tasks, connected repositories, memories, and session logs with patches. Code, branches, and pull requests already stored in GitHub remain there, but Jules-specific configuration and history need a separate export if you want to preserve them.
Google also warns that exported environment-variable values can be included in the archive, so that output should be treated as sensitive. The company says lessons from Jules are shaping other products, including Google Antigravity, but the notice does not describe automatic migration for sessions, schedules, or memories.
If Jules still sits in a workflow, the immediate job is to finish in-flight sessions before the Nov. 11 cutoff and export service-side data before access narrows to read-only.