How to Migrate from Google Jules Before December 31, 2026

Google announced on October 29, 2026 that it is winding down Jules, its async coding agent, and that date gives every Jules user a short migration window. To migrate from Google Jules safely, finish open sessions before November 11, 2026, export your settings, scheduled tasks, repositories, memories, and sessions before December 31, 2026, and rebuild the tasks you still need in Google Antigravity or another async agent. Jules becomes read-only after November 11, so work left open past that date can be viewed but not finished in Jules. The full shutdown follows on December 31, 2026.

Why the Google Jules Shutdown Matters Now

The November 11 date matters more than the December 31 date, because November 11 ends new Jules work. Google said it will bring its learnings from Jules into Antigravity, its agent-first development platform, so the move is a consolidation into one platform rather than a one-to-one transfer of Jules sessions. A developer who waits until December to act will find Jules read-only, with no way to rerun a failed session or finish a scheduled task in place.

For example, a weekly dependency update that Jules ran on a schedule needs a new home before November 11, or that week simply has no run. Treat the next two weeks as the working window, and December as the deadline for keeping a copy of what Jules knew.

What to Save Before November 11

Save four kinds of material before the read-only date, because each one is harder to rebuild from memory later:

• Open sessions and pull requests: Save the list of active sessions with the state of each one: merged, waiting for review, or still running.
• Scheduled recurring tasks: Record the exact trigger schedule, the target repository, and the precise task prompt used.
• Environment settings and variables: Note down setup steps, test harness commands, and secrets each repository needed before Jules could build and test it.
• Memories and session history: Retain notes that explain architectural decisions, such as why a refactor stopped at a certain file or why a flaky test was skipped.

A session that only says "fix the failing test" is easy to recreate. A session that holds the reason a test was skipped, or the workaround for a flaky build, is the material worth keeping.

How to Finish Open Jules Work

Work through open sessions in order of risk, starting with the ones that touch production code or shared branches:

1. List active sessions: Open Jules and catalog every active session across all connected GitHub repositories.
2. Triage open work: For each session, decide whether to merge, close, or rewrite the pull request by hand.
3. Review and merge: Merge finished pull requests in GitHub after reviewing the diff, and run the repository test suite on the merged result.
4. Close stale work: Close sessions that are no longer needed, and note the reason in the pull request or issue, so the decision is visible later.
5. Let long runs complete: For sessions still running, let them finish before November 11 where possible, and avoid launching long tasks in the final days before cutoff.
6. Capture unfinished tasks: For any task that cannot finish in time, copy its prompt, repository, and last session summary into a migration note, so it can be restarted elsewhere without rework.

A pull request that Jules opened but nobody reviewed is the most common leftover. Review it the same way you would review a colleague's pull request, because merging without review trades a deadline problem for a code problem.

How to Export Your Jules Work

Google published an export path for Jules data, and reports of the October 29 announcement describe it as a CLI export. Use the export prompt given in the current Jules changelog, because that prompt is the part of this process most likely to change.

1. Install the Jules CLI package named in the current Jules changelog. Reports of the announcement give this command:

   npm install -g @google/jules

2. Sign in with jules login using the Google account that owns the Jules data.
3. Paste the official export prompt from the Jules changelog into a CLI coding agent, following the changelog wording exactly.
4. Confirm the export folder, reported as ~/jules-export, contains settings, environment variables, scheduled tasks, repositories, memories, and every session.
5. Open the export and check that scheduled tasks and environment variables are present, rather than assuming the run copied everything.
6. Move the export to a private backup location, and keep it out of any Git repository.

How to Migrate from Google Jules to Antigravity

Antigravity is the platform Google named as the destination for what it learned from Jules, and it fits the Jules pattern because its Agent Manager runs several agents on separate tasks while you review their work. Rebuild one Jules task at a time, starting with the smallest recurring task, so an issue is easy to spot.

1. Download Antigravity from antigravity.google and sign in with your Google account.
2. Open the repository you used with Jules, and confirm the project builds and tests pass cleanly before any agent runs.
3. In Agent Manager, create a task from one saved Jules prompt, keeping the repository, the scope, and the test you will run after the change.
4. Let the agent draft a plan, write the change, and produce artifacts you can review, such as a plan, a diff, and test output.
5. Review the diff and run the tests yourself before merging, using the same review habit you used for Jules pull requests.
6. Repeat the process for the next task, and only then recreate scheduled or recurring tasks, so a broken schedule does not repeat a broken change.

A Jules prompt that worked well usually transfers with little editing, because both tools take a scoped task, a repository, and a check at the end. A prompt that says "clean up the codebase" will fail in Antigravity the same way it would have failed in Jules, so tighten the scope to one folder or one behavior before you run it. When a task needs a browser check, use the agent's browser verification step and inspect the visual output yourself.

How to Pick a Replacement If Antigravity Does Not Fit

Antigravity is the natural first try for a Jules user, but it is not the only async pattern, and the right replacement depends on where your team already works. Use the picker below to narrow the choice, then test one task in the new tool before moving the rest:

Test the replacement with a task you have already completed in Jules, because a known result makes a weak replacement obvious. If the new tool cannot reproduce that result, or if its pull request needs heavy cleanup, test the next option before migrating scheduled tasks. Check current pricing pages before committing a team to a new subscription.

What to Do If It Fails

If you encounter blockers during the migration process, use these targeted recovery steps:

• Jules is already read-only: Skip finishing steps and go straight to exporting data, since no new session can execute.
• Missing scheduled tasks in export: Cross-check your Jules session list against the local export folder, and rerun the export prompt while Jules remains accessible.
• Secrets exposed in export: Move the export folder to private storage immediately, and rotate any credentials that touched a shared drive or git tree.
• Antigravity cannot build your repo: Fix build dependencies locally first. An autonomous agent cannot reliably debug an environment that fails basic compilation.
• Rebuilt task produces poor PR diffs: Narrow the scope of your prompt to a single file or function, provide an explicit unit test target, and rerun.

Frequently Asked Questions

Conclusion

To migrate from Google Jules, finish open work before November 11, 2026, export your sessions, schedules, settings, and memories before December 31, 2026, and rebuild each task in Antigravity or another async agent that returns pull requests. Start with one small recurring task, review its diff and tests, and only then move the rest. That order keeps the migration to a set of reviewed changes, instead of a pile of unreviewed pull requests left behind when Jules closes.

For estimating the cost of the replacement work, the PromptStaging AI Cost and Token Calculator can help you model token use, but it does not read your Jules or Antigravity bill, so treat its output as an estimate.

Written by TJ Singh

Creative Technologist & Full-Stack AI Architect. Author of PromptStaging's deterministic prompt frameworks, agent skills catalog, and developer tooling guides.

View Portfolio & Hire TJ →