Jules Turndown

Google will wind down its Jules asynchronous coding agent on December 31, 2026, with users able to finish sessions until November 11, 2026, after which Jules becomes read-only through year-end. Google said learnings from Jules are shaping its agent-first platform Google Antigravity, and it now offers a Jules Tools CLI export that writes account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts and every session's prompt, plan, activity log and code patches to ~/jules-export. Code, branches and pull requests remain in GitHub, and Google warned that env-variables.json holds environment variable values, so the export folder should be kept private and out of repositories.

Jules Turndown October 29, 2026 We’re writing to let you know that as part of our work to unify our agentic coding efforts, Jules will wind down on December 31, 2026. You have until November 11, 2026 to continue finishing up sessions. After November 11, 2026, we will be turning Jules to read-only until the end of the year. When we launched Jules, it was an experiment to learn how asynchronous coding agents could help you tackle your backlog and ship faster. What you built with it taught us where agentic development is headed, and those learnings are shaping products across Google, including our agent-first platform, Google Antigravity. You can now export everything Jules knows about your work into a local folder: account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and every session, including its prompt, plan, full activity log, and code patches. Your code, branches, and pull requests already live in GitHub, so they stay where they are. The export covers the configuration and history that live inside Jules. To export, install Jules Tools https://jules.google/docs/cli/reference and sign in: Then open a CLI coding agent, such as Antigravity CLI https://antigravity.google/product/antigravity-cli , from your home directory and paste the export prompt below. The agent checks your setup, runs the export, and tells you what it saved. Show the export prompt Your data lands in ~/jules-export : connected repositories in sources.json , a folder per repository with its setup script, test command, and memories, your settings, environment variables, and scheduled tasks as JSON, and a folder per session with a readable summary.md , the full activity log, and its diffs. env-variables.json contains your environment variable values, so keep the export folder private and out of your repositories. If you use Jules with GitHub, make sure your GitHub account is connected https://github.com/apps/google-labs-jules/installations/select target first, or the export won’t include repository data.