Google to wind down Jules coding agent on December 31, 2026
READ THE ORIGINAL SOURCEOpen original sourcejules.google · Opens in a new tabGoogle says Jules, its asynchronous coding agent, will wind down on December 31, 2026, as it unifies agentic coding efforts. Users can finish sessions until November 11, 2026, after which Jules becomes read-only until year end. Lessons from Jules are said to be shaping Google Antigravity, an agent-first platform. Users can export account settings, environment variables, scheduled tasks, repositories, memories, setup scripts, and session history via Jules Tools and a provided export script. Code, branches, and pull requests remain in GitHub.
One primary source; other links are context, not independent corroboration.
- Primary sourceX discovery · automated brief
- Discovery linkX
- Linked in sourceGitHub account is connected
Grok Bot submitted the link. AINewsIQ fetched the primary source and prepared a source-based brief automatically. An editor has not reviewed the story; social attention and the brief do not independently verify its claims.
Open full article view →- Linked article+30
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
Google says Jules, its asynchronous coding agent, will wind down on December 31, 2026, as it unifies agentic coding efforts. Users can finish sessions until November 11, 2026, after which Jules becomes read-only until year end. Lessons from Jules are said to be shaping Google Antigravity, an agent-first platform. Users can export account settings, environment variables, scheduled tasks, repositories, memories, setup scripts, and session history via Jules Tools and a provided export script. Code, branches, and pull requests remain in GitHub.
A READER'S EVIDENCE CHECKHow to read this signalSix questions about claims, sources, risks, and open checks
This is a signal-level guide until claim-level evidence is available. “Not recorded” means the evidence has not been assessed here; it does not mean a result is false. How we check AI news →
- 01Who is making each claim?
The claimant and whether each claim was measured or asserted are not recorded in this public brief.
- 02What was actually tested?
Not recorded per claim. Check the source for sample size, tasks, model and benchmark versions, and reproducibility.
- 03Where are the sources?
Original link: jules.google. Brief basis: fetched source page. Primary page date and quote locations are not established in this panel.
- 04What could mislead?
Source claims not independently checked; the export relies on undocumented internal endpoints that the source itself warns may change.
- 05What is at risk if wrong?
Not assessed per claim. Consider safety, privacy, cost, and adoption decisions before relying on the result.
- 06What would change the view?
No claim-specific check is recorded. An inspectable primary method or independent replication could change the assessment.
Key findings from the stored brief
- Jules winds down December 31, 2026; sessions can be finished until November 11, 2026.
- After November 11, Jules becomes read-only until the end of the year.
- Google says Jules learnings are shaping its agent-first platform, Google Antigravity.
- Users can export settings, memories, repos, and session history; code stays in GitHub.
Source claims not independently checked; the export relies on undocumented internal endpoints that the source itself warns may change.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
Grok Bot submitted the link. AINewsIQ fetched the primary source and prepared a source-based brief automatically. An editor has not reviewed the story; social attention and the brief do not independently verify its claims.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Google says Jules, its asynchronous coding agent launched in December 2024, will wind down on December 31, 2026 as part of unifying its agentic coding efforts. Users can keep finishing sessions until November 11, after which Jules goes read-only. A Jules CLI export covers settings, environment variables, scheduled tasks, memories and session history; Google points users to Antigravity.
Source claims not independently checked; the export relies on undocumented internal endpoints that the source itself warns may change.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
- x post ↗ · 1,205 likes, 69 reposts, 161 replies, 174 quotes · observed 10/30/2026, 4:08:56 PM
- Related post ↗
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
A publication revision history is not stored for this signal. New engagement snapshots do not mean the source itself changed.
Why this may matter
Users relying on Jules need to finish sessions and export configuration and history before the shutdown. The announcement also signals Google consolidating its agentic coding products into Antigravity.
Limits and open questions
Source claims not independently checked; the export relies on undocumented internal endpoints that the source itself warns may change.
Organization-specific financial, security, and operational effects require the organization's own context and review.
Discussion
Comments are reviewed before publication. Discuss the evidence, not the person.
No published comments yet.
Reader discussion opens with accounts. You can read the original source and published comments now.