FrameworksOfficial

Google Antigravity gets a first-party AG-UI integration for file, shell, subagent and approval workflows

On November 3, CopilotKit formally announced `ag-ui-antigravity`. The adapter maps Antigravity text, reasoning, tool, and subagent steps into AG-UI events so CopilotKit, Slack, Teams, and other AG-UI frontends can stream the work with A2UI, frontend tools, shared state, attachments, and human approval. The accompanying Repo Doctor shows an end-to-end path for fixing CI, rendering diffs and test results, and pausing risky steps.

Why it matters

The integration connects a stateful agent runtime with real file and shell authority to a visible, approvable product surface. It shows AG-UI becoming a governance boundary between agent computers and host applications, while also making clear that streaming visibility and approval cards are only part of the control plane: workspace isolation, duplicate calls, session recovery, and side effects remain shared adapter and host responsibilities.

A closer look

Antigravity runs a Go localharness subprocess, while the Python adapter connects over WebSocket and translates steps into AG-UI 1.0 events. Sessions share harness processes. A human-interrupted turn can span several AG-UI runs, so the adapter preserves the iterator, event translator, and frontend-tool results to avoid retranslating and re-executing the same call after resume. The official 0.2.1 package reports 315 unit tests and 19 live Gemini checks on September 30 against google-antigravity 0.1.9: 15 passed and four were cut short by free-tier 429 or Gemini 503 errors. The November announcement marks first-party integration, documentation, Dojo, and OpenBot/Repo Doctor productization; adapter 0.2.1 had already shipped on October 6.

Who this is for

Platform, security, and product engineering teams bringing coding agents, agent computers, CI repair, or long-running workflows into web, Slack, Teams, and generative UI surfaces.

Original sources

Revisions & corrections (1)

— Merge the November 3 launch posts, package verification record, cookbook and official SDK source into one dated first-party AG-UI integration event while preserving the adapter's earlier October release date.

Related events

Frameworks

AG-UI Kotlin 0.5.0 aligns with 1.0 through interrupts, activities, multimodality, and strict state boundaries

AG-UI released Kotlin core, client, and tools 0.5.0 on November 5. The SDK now targets AG-UI 1.0 with REASONING events, interrupt/resume outcomes, ACTIVITY snapshots and deltas, tool errors, and multimodal user messages, while adding browser Wasm and macOS Arm64 targets and tightening event, input, and RFC 6902 state validation.

Frameworks

AI SDK 7.0.163 honors telemetry content controls and preserves Google streamed tool order and signature history

Vercel released AI SDK 7.0.163 on November 5. `recordInputs` and `recordOutputs` now govern content delivered to integrations and the `ai:telemetry` channel, filtering prompts, tool inputs, response text, and raw span results while retaining application results such as usage. The same release preserves the order of text, complete function calls, and thought signatures in streamed Google responses and across replayed history.

Frameworks

json-render 0.22 streams one generative-UI catalog into native Slack and Teams cards

json-render 0.22.0, released November 4, adds `@json-render/chat`. One component catalog can become a Chat SDK card; `streamCard` edits a thread message as elements arrive, while `toCard` validates the final card against component schemas and optional platform limits. The official example previews Slack Block Kit and Teams Adaptive Cards.