Gemini 4 Neon
Label an issue llm-antigravity-neon or use the neon alias. Neon runs at low, medium, high and xhigh effort, as Gemini 4 Hydrogen does. Google AI Pro accounts signed in with agy login have it, as do GEMINI_API_KEY accounts.
ProPR 0.9.3 · 19 November 2026
Pick Gemini 4 Neon or Gemini 4 Carbon on your Antigravity login, and run the current Codex, Claude Code and Antigravity CLIs. Every follow-up comment is picked up, a flaky runner no longer triggers a code follow-up, and each run tells you plainly how it ended.
New
Two Gemini 4 models join Argon and Hydrogen in the Antigravity catalog, each with a 1M context window, and the bundled coding agents move to their current releases.
Label an issue llm-antigravity-neon or use the neon alias. Neon runs at low, medium, high and xhigh effort, as Gemini 4 Hydrogen does. Google AI Pro accounts signed in with agy login have it, as do GEMINI_API_KEY accounts.
llm-antigravity-carbon and the carbon alias select Carbon at low, medium or high effort; an xhigh request runs at high. With agy login it answers only for Google AI Ultra subscribers, so remove it from the agent's models on a Google AI Pro account.
The propr/agent image moves to Codex 0.170.0, Claude Code 2.1.328 and Antigravity CLI 1.5.12. OpenCode 1.19.6 and Mistral Vibe 2.25.8 are unchanged from 0.9.2.
Codex 0.170.0 lists GPT-6.2 Astra and GPT-6.2 Sol in its own catalog and raises GPT-6.1 Sol to 500K, so reviews on GPT-6.1 Sol get the larger budget.
Claude Code 2.1.328 no longer hangs a headless run when a model-settings fetch stalls. Antigravity CLI 1.5.12 retries a request after a brief connection problem and finishes the turn.
OpenCode Zen no longer serves the free GLM 5.3 Flash model, so it leaves the catalog. Saved selections, the glm53-flash-free alias and the llm-opencode-glm53-flash-free label run DeepSeek V4.1 Flash Free.
Fixed
A plain comment on a ProPR pull request is the way to ask for changes. 0.9.3 closes the gaps where a comment was dropped or a follow-up failed before it started, and reads CI failures more carefully before acting on them.
A pull request that ProPR opened through its retry path, or found during final validation, now gets the AI and model labels, so your comments on it start follow-ups. A comment stored while another job for the pull request was running is picked up by a queued job; it no longer expires unread after an hour.
The worker checks for an existing local branch the way git worktree add -b does and reuses it safely: a branch behind the remote moves forward, a diverged one restarts from the remote head with its local commits kept, and a branch held by a worktree whose folder is gone is released.
While a follow-up suspends CI, the pull request's status block says so and counts the runs it cancelled. A failure whose evidence shows only a runner shutdown, lost communication, or a network, mirror or registry error in a setup step starts no follow-up; the status block names the job and tells you to re-run the failed jobs. Two or more failed steps, or a step that ran after the failed one, still count as a code failure.
With Auto CI follow-up on, a failed gate job that depends on other failed jobs in the same run gets one line naming them, so the follow-up agent checks those first. Every failed job keeps its own evidence section, in the order the checks were reported.
Fixed
When the agent succeeded and its changes were committed but the pull request could not be opened, the task ends as failed with status publication_failed. The issue comment names the step that failed and the branch that holds the commits, and the issue keeps its AI label.
When the agent's last message says it is still working or waiting, the issue comment reads AI Processing Ended Unconfirmed and a follow-up reply reads ⚠️ Committed follow-up changes, with the reason. The check rides on the existing summary request, so it costs no extra call.
Rate-limit, cancelled, started and merge-conflict notices post one comment and update it on a repeat, with how many times and when. The rate-limit notice shows the right reset time, including weekly resets, and is skipped when the retry is due within two minutes.
Creating a pull request makes a single label call, and the retry, existing-pull-request and final validation paths send only the labels the pull request lacks.
With fewer than 500 API requests left in the GitHub App's window, ProPR skips status-line edits that would only change check counts and reads the checks again when the limit resets. A run starting or finishing, a review score, ready to merge and a suspension are still written.
Fixed
A run's preview skips the headings every report repeats and shows the first sentence of the body, in the run list, the API, the MCP list_automation_runs tool and the CLI. The run list columns line up whether a row says "5h ago" or a full date.
On touch layouts, the dashboard's earlier-updates toggle, repository Select rows, the automation editor's segmented controls and the Inbox Dismiss button take taps across at least 32×32 px.
In Settings → Maintenance → Held follow-ups, a follow-up whose agent is working right now is listed as Running, with a link to its task.
Type chips and the type filter show labels such as "PR review" and "Title generation", the usage badge wraps cleanly, and the Type and Model columns widen on wide screens so long model names are no longer cut off.
Back up the database and .env, then update the CLI and restart the stack. No manual steps are expected.
npm install -g [email protected]
propr start --restart
Launcher installs pull the new propr/launcher image and restart. The maintenance guide covers backups, version pinning and rollback. Starting with this release, every GitHub release page opens with a checked-in summary of its highlights and upgrade notes.
npm ci after pulling.publication_failed), and its issue keeps AI without getting AI-done.reportPreview in the API, the MCP list_automation_runs tool and the CLI now holds the report's first sentence rather than its title.AI label still needs it added by hand before plain follow-up comments on it are accepted.agy login. On a Pro account, remove it from the Antigravity agent's models.Version-by-version notes when they ship, and nothing else. Every message carries an unsubscribe link.