ProPR: where Gemini keeps working after Jules shuts down

Google is retiring Jules for Antigravity: sessions stop on 11 November 2026 and the product shuts down on 31 December 2026. ProPR keeps Gemini on the job through Antigravity CLI on your own server.

ProPR
vs
Google Jules

After the shutdown

Jules tied the Gemini agent to Google's VMs and Google's product lifecycle. ProPR ties nothing to one vendor: the agent is a per-task choice and the workflow lives on your infrastructure.

Jules path, until 31 December 2026Task → Google-hosted VM → branch or pull request → @JulesSessions stop on 11 November 2026 and the history turns read-only.
ProPR pathPlan → isolated workspace → GitHub PR → follow-up commitGemini through Antigravity CLI, on your Google AI plan, on your server.

Switch from Jules to ProPR.

Google Jules stops sessions on 11 November 2026 and shuts down on 31 December 2026. Move your workflow to ProPR.

What you keep: your GitHub repositories and review process, and the Google AI Pro or Ultra plan, which ProPR runs through Antigravity CLI.

The same ideas, ProPR's names

JulesProPR
TaskTask
Google-hosted VM per taskIsolated workspace per task on your server
Branch or pull requestPull request on every task
Comment or @Jules on the PRAny plain PR comment
Task quotas on Google AI Pro or UltraYour Google AI plan through Antigravity CLI, no markup
Gemini onlyGemini, plus Claude Code, Codex, Mistral Vibe, and OpenCode per task

From zero to the first pull request

Install ProPR, or skip the server

Run npm install -g propr-cli and propr setup on a Linux Docker host (quickstart). ProPR Hosted runs a dedicated instance for you when you would rather not run one.

Add the same repository and sign in your agent

Open the web UI, sign in with GitHub, and add the repository. Sign in Antigravity CLI with the Google account that carried your Jules quota.

Start the first task and approve the plan

Add the AI label to the issue and a model label such as llm-antigravity-argon to route it to Gemini, then approve the plan.

Review the pull request in GitHub

Review the diff the way you review any pull request. A plain comment on it becomes the next commit on the same branch; /review posts scored findings and /fix applies them. Put a second model on the review with the cross-model review playbook.

What stays with Jules: Jules needed no server; ProPR runs on a Linux Docker host you own, or on a ProPR Hosted plan.

Jules was Google's asynchronous coding agent: it cloned a GitHub repository into a fresh cloud VM, made the change, published a branch or pull request, and pushed follow-up commits when you commented on the PR or mentioned @Jules. Task quotas came with the Google AI Pro and Ultra plans. Google's October 2026 changelog announces the wind-down and names Antigravity as the agentic coding platform going forward.

ProPR starts every change with a plan, runs the agent in isolation on your server, opens the pull request, and turns plain GitHub comments into follow-up commits. Gemini runs through Antigravity CLI on your Google AI plan, and the same loop runs any supported agent. Put several model labels on one issue and compare their pull requests side by side.

Antigravity CLI in Agent Configuration: Gemini 3.8 Flash as the default, with Gemini 4 Argon, Claude Sonnet 5.5, Claude Opus 5.5 and GPT-OSS 120B behind the same login
Antigravity CLI inside ProPR: Gemini 3.8 Flash as the default, with Gemini 4 Argon and other models behind the same login.

Jules fits best when...

  • You have Jules sessions to finish before 11 November 2026 and history to export before the shutdown.
  • A Google-hosted VM per task, with no server of your own, was the attraction.
  • The Google AI Pro or Ultra plan already covers your Gemini usage.

ProPR fits best when...

  • Gemini keeps working on your repositories through Antigravity CLI, with Claude Code, Codex, Mistral Vibe, and OpenCode a label away.
  • Plans, task history, logs, and credentials live on your own infrastructure.
  • PR comments turn into follow-up commits through one loop that outlives any single vendor's agent.

A retiring hosted agent versus a self-hosted PR loop.

QuestionGoogle JulesProPR
Status in November 2026Read-only from 11 November; shuts down 31 December 2026Active, Apache 2.0
Where the agent runsGoogle-hosted VM per taskYour server
Gemini implements the changeYesYes, through Antigravity CLI
Claude, Codex, Mistral, or OpenCode insteadNoYes
BillingTask quotas on Google AI Pro or UltraYour provider plans or API keys; no markup
PR comments become follow-up commitsYes: comment or mention @JulesAny plain comment, any agent
Task records and logs self-hostedNoYes

Verified November 2026: Jules wind-down changelog, Jules usage limits, Jules PR comment support, Jules FAQ.