What happened
In an October 29, 2026 changelog entry titled “Jules Turndown,” Google said that Jules will wind down on December 31, 2026. The company describes the move as part of work to unify its agentic coding efforts. Jules was launched as an experiment in how an asynchronous coding agent could help users work through backlogs and ship faster, according to the notice.
The timeline has two operational deadlines. Jules users have until November 11, 2026 to continue finishing sessions. After that date, Google will turn Jules into a read-only service through the end of the year. The final shutdown date is December 31, 2026. That makes November 11 the practical deadline for teams that still need the agent to complete active work, rather than merely inspect what it did previously.
Google says the experience and learning from Jules are shaping products across the company, including Google Antigravity, which it calls an agent-first platform. The changelog does not say that Jules projects, settings, or behavior will migrate automatically into Antigravity or any other Google product. Its concrete migration mechanism is an export to a local folder.
That export covers material held inside Jules: account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and every session. For each session, the stated export includes the prompt, plan, full activity log, and code patches. Google distinguishes this material from code, branches, and pull requests, which it says already live in GitHub and will remain there. The distinction matters because a repository alone may not preserve the operational context used to run Jules work.
To begin the export, Google instructs users to install Jules Tools with npm install -g @google/jules and then run jules login. Its documented workflow then asks the user to open a CLI coding agent, such as Claude Code, from the home directory and paste Google’s supplied export prompt. Google says that agent will check the setup, run the export, and report what it saved. The announcement provides no price change, replacement entitlement, automatic migration process, or guarantee about importing the exported material into another agent.
What the archive adds
This is a new event on a recurring archive thread: hosted AI services can disappear on a short, operationally meaningful timetable. Chroma’s acquisition notice set separate write and read cutoffs for Chroma Cloud, while Moondream Cloud’s shutdown notice paired a dated closure with migration guidance. Jules adds a coding-agent version of the same problem: workflow state exists beyond the code repository.
Trend signal
No supplied pattern directly captures a vendor retiring a coding agent while exporting its user-held workflow state.
Why now
Google explicitly frames the decision as unifying its agentic coding efforts. It says what users built with Jules helped reveal where agentic development is heading, and that those learnings are shaping products across Google, including Antigravity. The announcement establishes a product-consolidation rationale, but does not provide further business, technical, or usage metrics behind the timing.
Connections to other events
The connection to the Chroma Cloud and Moondream Cloud notices is operational rather than technical: each gives builders a deadline to extract or move work from a hosted AI service. Jules differs because its export is aimed at agent-specific working state—memories, environment variables, scheduled tasks, setup scripts, and session records—while code, branches, and pull requests remain in GitHub.
Why it matters
A coding-agent migration is not finished when the repository has been cloned. Jules’ own export list shows the additional layers teams may depend on: secrets or environment configuration, repository connections, recurring work, setup instructions, memory, and the record of how prior changes were planned and executed. Some of these may be sensitive; some may be necessary to reproduce a useful workflow; some may be historical evidence rather than material to carry forward.
Teams using Jules should treat the November 11 cutoff as a continuity exercise. Inventory active sessions and scheduled tasks, export the service-held state, and separate it into categories: items that belong under version control, secrets that require an approved destination, and historical records that need retention or review. The announcement also makes clear that Google’s proposed export procedure uses a CLI coding agent, so teams should review the destination and handling of exported material under their own controls.
Limits and uncertainty
The changelog is a shutdown and export notice, not a migration specification. It does not establish whether exported Jules memories, plans, logs, or patches can be imported into Claude Code, Google Antigravity, or another agent. It does not state how long an export takes, what file formats it produces, whether every integration is covered, or whether an organization can perform bulk exports. It also does not describe account, billing, or data-retention treatment after December 31. Builders should not infer feature parity or an endorsed replacement from Google naming Antigravity and Claude Code in the notice.
Skill to build now
Practice making an agent workflow portable. This week, choose one Jules project and identify every dependency outside its Git repository: environment variables, setup steps, schedules, repository permissions, agent memory, and active task context. Export the available material, then turn the reusable parts into reviewed artifacts with clear owners. Keep secrets out of ordinary documentation and store them in the team’s approved secret-management path. Finally, test whether another developer can understand the project and reproduce its setup without opening Jules.
Reader takeaway
Jules is not available for active work after November 11, 2026 and closes on December 31. Export early, but focus on the state GitHub does not preserve: configuration, memories, scheduled work, setup scripts, and session history. A replacement coding agent is a separate evaluation, not something this notice promises.
Open question
Which portions of a Jules export, if any, will be directly usable in Google Antigravity or other coding-agent environments?