What happened
TestingCatalog reports that Google will discontinue Jules, its AI coding agent, on December 31, 2026. Jules will become read-only after November 11, and users can export their sessions and configurations before the service closes. The retirement itself is presented as a Google-confirmed change; the Antigravity details are observations from a current build rather than a Google product announcement.
The reported build includes a toggle above Antigravity's prompt bar for switching between local and cloud environments. Cloud execution is not currently available in Antigravity. The distinction matters because cloud execution was a core Jules capability: developers could connect repositories and run asynchronous coding tasks outside a local interactive session.
The same report describes an experimental, developer-only Running Jobs area in Antigravity settings. It is intended to show active background tasks and terminal sessions. TestingCatalog also says that advanced scheduled runs are expected there, but that expectation is not a confirmed product commitment. Other reported work includes an interface redesign, a prompt-bar option to attach files from Google Drive when connected, and continuing development of a Chief of Staff agent.
Antigravity has already launched a Plugin Marketplace with integrations and connectors, according to the source. Taken together, the local/cloud switch, background-job surface, and connected-service work point to an attempt to make Antigravity a broader environment for agentic coding. TestingCatalog compares the prospective direction with OpenAI Codex and Anthropic Claude Code, which it says already support remote execution and background workflows. Google has not confirmed a release date, feature set, limits, or whether Jules functionality will transfer directly.
What the archive adds
This is a new fact on a known story, not a restatement. The retirement schedule and export path were covered in Google is winding down Jules: sessions until Nov 11, read-only after, shut down Dec 31, 2026. The new element is the reported Antigravity interface evidence that may explain where cloud-oriented coding work could move.
Trend signal
The report weakly supports Harness architecture outlives model choice. If Antigravity becomes the shared surface for local work, remote runs, repositories, integrations, and job monitoring, the operational value would reside in that harness rather than in a separately branded coding agent. This remains a directional signal, not proof of a shipped architecture.
Why now
The timing is set by Jules's shutdown. Google has given users a read-only date of November 11 and a final shutdown date of December 31, 2026. A local/cloud control and job-monitoring area appearing during that wind-down makes a consolidation hypothesis plausible, but Google has not said that Antigravity will replace Jules feature for feature or announced when any cloud mode will ship.
Connections to other events
The archive also notes that OpenAI models and Codex are slated for Antigravity through Google Cloud Model Garden in OpenAI models are coming to Google Cloud. That item concerns model availability and purchasing, while this report concerns execution surfaces. Together, they describe different parts of a possible Antigravity expansion, but neither source establishes how those parts will be combined.
Why it matters
Teams using Jules should treat its retirement as an immediate continuity task, not wait for an implied Antigravity replacement. Export sessions and configurations while the option exists, identify which workflows require asynchronous repository work, and record the operational assumptions behind them: repository access, environment setup, approvals, artifacts, and task completion criteria.
For teams evaluating Antigravity, the reported controls are more consequential than a visual redesign because remote execution changes where code runs and how background work is observed. But an interface toggle is not an API, service-level commitment, or migration guarantee. Planning should distinguish the confirmed Jules shutdown from the unconfirmed shape of Antigravity cloud execution.
What happens next
- Google announces or exposes an initial Antigravity cloud-execution capability. (3 months, 55%). Watch for: product documentation specifying access, repositories, limits, or pricing.
- Jules users receive final migration guidance before shutdown. (3 months, 75%). Watch for: an official mapping of exports or workflows to another Google product.
Limits and uncertainty
The public report is based on observations in a build and explicitly says cloud execution is not currently available in Antigravity. It does not establish whether the toggle is functional, which users can access it, whether it will reach general availability, or how it will handle repositories, credentials, network access, costs, schedules, or data retention. The report also does not prove that Running Jobs, Drive attachments, or the Chief of Staff agent will ship together. Google has confirmed the Jules wind-down, but has not confirmed that Antigravity is its direct replacement.
Skill to build now
Make a small migration inventory for every Jules workflow this week. For each one, capture the repository, task trigger, expected artifact, required secrets or permissions, human review step, and how completion is verified. That inventory is useful whether the destination becomes Antigravity, another remote coding agent, or a local process, because it separates the workflow contract from the product that happened to run it.
Reader takeaway
Jules has a confirmed end date; Antigravity cloud execution does not yet have a confirmed launch. The reported build is a meaningful clue that Google may consolidate coding-agent work into Antigravity, but builders should preserve Jules data and document workflows rather than assume compatibility.
Open question
Will Google publish a supported migration path from Jules to Antigravity, including cloud execution, repository access, and background-job behavior?