Google sets Jules wind-down dates and publishes export guide
Google will wind down Jules on December 31, 2026. The earlier working-session deadline is November 11, followed by read-only access. Its October 29 announcement provides a local export guide. Neither cutoff includes a stated time zone or hour.
For developers, the immediate question is not just which coding agent to try next. It is whether unfinished work and useful context are recoverable outside the service. A repository backup and an agent-history backup solve different problems.
Two dates to plan around
| Date in 2026 | Service change | Planning implication |
|---|---|---|
| November 11 | Last stated date to finish sessions | Review unfinished work first |
| After November 11 | Read-only period | Do not plan further agent execution |
| December 31 | Jules wind-down | Complete preservation beforehand |
Preserve context separately from code
Google says GitHub code, branches and pull requests remain in GitHub. Jules export includes settings, environment variables, schedules, repositories, memories and session prompts, plans, activity logs and patches. Keep the export private: environment-variable values are included. The notice does not specify post-shutdown deletion or retention.
A practical review should answer three questions: which tasks remain unfinished, which changes have been reviewed, and which decisions exist only in a conversation? For example, a patch can show the final code without explaining why an alternative was rejected. Preserve that reasoning before relying on a replacement agent to continue the job.
Check the inventory before exporting
The Jules Tools reference documents jules remote list --session for listing sessions and jules remote list --repo for connected repositories. Its terminal dashboard also offers a side-by-side diff view. These are useful inspection surfaces before deciding what needs attention.
The CLI uses Google authentication through a browser. The documented remote pull command retrieves results from a completed session, but should not be confused with a complete account archive. Follow the linked export guide for the broader preservation workflow rather than treating a code download as proof that everything was saved.
After an export, inspect its reported errors and sample the saved material before calling the migration complete. A useful acceptance check is whether someone can identify the unfinished task, locate its relevant changes and understand its next step without reopening the old service. ByteForward has not performed a Jules export or tested restoration.
Antigravity is the suggested destination, not a proven import
Google points users toward Antigravity. Its App documentation describes parallel agents, scheduled tasks, project grouping and workspace customization. Those features may cover parts of a Jules workflow, but a list of capabilities does not establish that existing schedules, memories or sessions transfer automatically.
Treat replacement setup as a separate project: map recurring jobs to their triggers, identify required repository access and review each automation before enabling it. Start with one representative task rather than moving every recurring job at once. This is a planning suggestion, not a tested migration procedure.
