Google Jules Shutdown: November 11 Session Deadline and What to Export

A generated conceptual illustration of preserving code separately from its working context. This is not a screenshot of Jules.

Google Jules will shut down on December 31, 2026. November 11 is the deadline to finish ongoing sessions, after which Jules will become read-only until the end of the year. Users should complete unfinished work first and preserve GitHub code separately from records inside Jules. This article covers the official timeline, export procedure, and checks before moving to Antigravity.

This is a preparation guide based on public announcements and documentation, not a report of exporting or migrating a real account.

Check the timeline and preservation scope first

Google published its shutdown announcement on October 29, 2026. Distinguish the two deadlines.

The announcement does not specify an exact transition time or timezone. These dates should not be arbitrarily converted to midnight in Korea. Avoid leaving the work until the last day.

Code, branches, and pull requests already stored on GitHub remain there. The separate export covers configuration and history inside Jules: account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and each session's prompt, plan, activity log, and patches. Official Jules shutdown announcement

1. Classify unfinished work before backing it up

The following is this article's suggested review order.

• Unreviewed changes: Record the originating session and the commit on which the changes were based.

• Changes already submitted as pull requests: Open the actual branch and PR on GitHub. Do not rely on a completion indicator alone.

• Reasoning that exists only inside Jules: Select failed approaches, reproduction conditions, test commands, and other information the next person needs.

• Recurring work: Record its purpose and schedule. Do not assume an exported configuration will run automatically in another tool.

For example, a patch may be on GitHub while the reason for excluding a particular test exists only in the conversation. Conversely, applying code that has already been merged duplicates a change. A useful preservation inventory records both where an item is stored and whether review is complete.

2. Check the official export procedure directly

The announcement instructs users to install Jules Tools, sign in, and run its supplied export prompt in a CLI coding agent. Results are saved to a local folder. These preparation commands come from the announcement and were not executed for this article.

Before running them, read the latest official export prompt. This article links to the long script instead of maintaining a separate copy that could become outdated.

The official example says it uses some undocumented endpoints. If an error occurs, identify the failing stage and response rather than changing authentication arbitrarily or treating the operation as successful.

3. Treat the export as a backup containing secrets

In particular, the official instructions say that env-variables.json includes environment variable values. They warn users to keep the exported folder private and outside repositories. Official export precautions

The following practices are recommended.

• Store the export outside code repositories and publicly synchronized folders.

• Decide its location and access permissions first. Share only the necessary scope with a team.

• When requesting help, provide error codes and sanitized logs rather than tokens or raw environment variables.

• Do not immediately feed the entire folder into a new coding tool. Separate secrets from confidential working context first.

Finishing an export does not mean migration is complete. Prompts, memories, and schedules have different meanings across tools, so review and reconstruct only what is needed.

4. Check recoverability separately from file existence

Backup verification can be divided into three layers. This is an operational proposal from this article, not an official product feature.

1. Inventory: Compare exported repositories and sessions against what is needed. Even a count of zero should be checked against actual usage.

2. Content: Open the summaries, activity logs, and patches for important work. A nonempty file alone is insufficient.

3. Usability: Check patch applicability and project tests in a separate working copy.

Git patches can be inspected for scope and applicability before applying them. The following documentation-based example requires replacing the path with your own patch file.

--stat shows change statistics; --check checks whether the patch can apply to the current working tree without applying it. Success does not establish that tests pass or requirements are satisfied. Review whether the change is already present before deciding to apply and test it. Official Git apply documentation

An Antigravity recommendation does not mean automatic migration

The shutdown announcement describes an effort to unify agentic coding work and mentions Google Antigravity. The official Antigravity website presents App, CLI, IDE, and SDK surfaces for its agentic development platform.

However, the shutdown announcement reviewed for this article does not provide a procedure for automatically restoring a Jules export into Antigravity. Distinguish the availability of an alternative tool from a migration that preserves the existing working environment. The following are suggested migration checks.

• Verify connected repositories, the base branch, and build and test commands in the new environment.

• Review Jules memories and setup scripts before adapting them to the new tool's instruction and configuration formats.

• Recheck schedules, targets, and permissions for recurring tasks. Check existing task states to avoid duplicate execution.

• Reconfigure only the required environment variables using the new environment's secret storage.

• Verify code changes, tests, and PR review with one small task before expanding the scope.

Antigravity installation, data import, and feature compatibility were not tested for this article.

What counts as preservation complete

The goal is more than running an export command: establish the location of important work, its context, secret handling, and practical reusability. Complete organization and verification while sessions can still be worked on, rather than waiting until shutdown.

The official announcement is dated October 29, 2026. The shutdown announcement and official Antigravity website were checked again on November 1, 2026. This article contains no results from account login, real data export, patch application, or performance measurement. Verify installation, export, and inspection commands in your own environment.

한국어 버전