Jules is winding down. Keep your work ready

Start with the work you want to keep

If you use Jules to help build an app, begin by listing what you need from it: unfinished tasks, useful instructions and the history behind important changes. That list gives you a clear starting point for moving on.

On October 29, Google announced that Jules, its AI coding tool, will close on December 31, 2026. Sessions can finish until November 11. It becomes read-only after that, available for viewing through year-end.

Google points to Antigravity, another AI building tool, but gives no automatic migration plan or promise of matching features.

Read the announcement: Google Jules: Jules Turndown.

Know what your export contains

The export saves settings, scheduled tasks, stored instructions and session records to your computer. Those records can include the request, plan, activity and code changes.

Code and proposed changes already in GitHub stay there. GitHub keeps project code and its history. Exporting saves what lives inside Jules; check both places for unfinished work.

Exports include environment values: stored settings that can contain secret access details. Keep the folder private and outside code repositories. Remove private values from any copy used for discussion.

Make a small handover plan

Google's notice links its official export instructions. If you work with a builder, review them and open the resulting files together. Confirm the records you wanted were actually saved.

Google's notice gives dates without times of day. Plan the handover before the last working day, leaving room to resolve sign-in problems and review changes not yet in your main project.

1. Mark November 11 and December 31 in your project calendar.
2. List active tasks and decide which to finish, stop or hand over.
3. Make the private export and open a few important sessions to confirm the records are present.
4. Keep a readable note of the instructions, checks and recurring tasks your project depends on.
5. Try one familiar task with your chosen replacement and review the result before moving more work.

Carry your understanding forward

Our view: this is a useful reminder to keep the knowledge behind your app somewhere you control. Record what it does, how to check it and which decisions still need a person. Those notes help whether you build yourself or work alongside a team.

Changing tools can interrupt a comfortable routine. A clear handover lets you keep the understanding you have gained and make the next choice with evidence. Check the replacement's actual features, access and costs, then build confidence through a task you already know.