Google shuts its Jules coding agent, read-only from 11 November

Google shuts its Jules coding agent, read-only from 11 November

29 October 2026: Google is closing Jules, its asynchronous coding agent, which works through a task and returns a plan and code patches. Users can keep running sessions until 11 November 2026; after that Jules turns read-only, and it winds down completely on 31 December 2026. Google says the move is part of its work "to unify our agentic coding efforts", and names its agent-first platform, Google Antigravity, as the place the lessons are going.

Not yet independently verified. Google has not said what happens to paid Jules plans or whether unused time is refunded. We will add it when Google states it. We will update this when it can be confirmed, and remove this note.

Three dates for teams using it

• Until 11 November 2026: sessions can be started and finished as now.
• 11 November to 31 December 2026: Jules is read-only, so history can be viewed and exported but no new work runs.
• 31 December 2026: Jules winds down.

The product page still showed its plans on 31 October, a free tier of 15 tasks a day and a Pro tier of 100, and the notice says nothing about billing or refunds for paid users.

What the export covers, and what it does not need to

Code, branches and pull requests already sit in GitHub, Google points out, so they stay where they are. What lives only inside Jules is the configuration and the history: account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and every session with its prompt, plan, full activity log and code patches. Google has published a way to pull all of that into a local folder.

The route is unusual. A user installs Jules Tools with npm install -g @google/jules, signs in with jules login, then opens a command-line coding agent in the home directory and pastes an export prompt from the changelog. The prompt has the agent check the login, list the connected repositories, save and run an export script, and report what it saved, without printing the access token or the values of environment variables. The notes warn that the access token expires about an hour after login, so a long export may need a fresh sign-in.

Before the read-only date

Teams that set up scheduled tasks in Jules should move those jobs before 11 November, because they stop running when Jules turns read-only. The export writes the values of environment variables to a local file, so it belongs somewhere access-controlled and the variables are worth rotating once the export is done. Google is listed in our catalogue as Google, and our AI coding assistant software category lists six products.

Related on TrustList:

• ChromeOS 16805.33.0 fixes 106 Chrome bugs, five of them Critical
• Google stops paying bounties for flaws in Go, Angular and other OSS
• Google and OpenAI both retire their custom assistant builders

Sources

• Google Jules: Changelog, "Jules Turndown", 29 October 2026
• Google Jules: product page with plans (read 31 October 2026), 31 October 2026