Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
31 commits
Select commit Hold shift + click to select a range
9af95d6
Keep Antigravity ACP turns open for reactive wakeups
j-asefa Nov 21, 2026
c6f631e
Bound unconfirmed Antigravity reactive completions
j-asefa Nov 21, 2026
74f6998
Resolve stalled Antigravity tools and answered steering
j-asefa Nov 21, 2026
22ad84c
Keep the reactive watchdog active through steering
j-asefa Nov 21, 2026
6ee1ed4
Ignore stale reactive usage and settle cancellation
j-asefa Nov 21, 2026
201be01
Track Antigravity wakeups across early tool settlement
j-asefa Nov 21, 2026
0220b60
Require pending wakeups to answer and preserve watchdog budget
j-asefa Nov 21, 2026
1a1641d
Handle delayed ACP tool metadata and blocked cancellation
j-asefa Nov 21, 2026
4e67356
Settle reactive completion after observed Antigravity wire ordering
j-asefa Nov 21, 2026
ef0f68b
Preserve unconfirmed Antigravity reactive output as partial
j-asefa Nov 21, 2026
e3242ab
Fence trailing progress and recognize late daemon metadata
j-asefa Nov 21, 2026
1d566cd
Handle synchronous tools and daemon-only steers
j-asefa Nov 21, 2026
f6db254
Keep daemon-only completion when a steer is rejected
j-asefa Nov 21, 2026
2a715f2
Recheck reactive work before completing a rejected steer
j-asefa Nov 21, 2026
54dbc05
Limit reactive waiting to outstanding work
j-asefa Nov 21, 2026
f74f176
Keep reactive work observed during unjoined steering
j-asefa Nov 21, 2026
652a789
Keep echoed steering inside the reactive boundary
j-asefa Nov 21, 2026
42d6d3b
Handle daemon identification and launch failures during reactive waiting
j-asefa Nov 21, 2026
6bdf9e2
Latch continuation evidence and cancel on reactive timeout
j-asefa Nov 21, 2026
d8f00df
Keep late daemon classification inside the reactive wait
j-asefa Nov 21, 2026
e26a906
Preserve normal completion for acknowledged synchronous steers
j-asefa Nov 21, 2026
c91ed9f
Follow acknowledged steers and preserve unjoined continuation text
j-asefa Nov 21, 2026
92f27af
Preserve response-based confirmation for bare steered commands
j-asefa Nov 21, 2026
c06ebe5
Bound acknowledged steering and distinguish a rejected response
j-asefa Nov 21, 2026
c53f480
Track inherited tools and observed steering progress
j-asefa Nov 21, 2026
affed23
Separate inherited tools from pending steering work
j-asefa Nov 21, 2026
11f2462
Preserve cancellation and approval across overlapping prompts
j-asefa Nov 21, 2026
07a85f2
Preserve the original tool baseline across overlapping steers
j-asefa Nov 21, 2026
6714ab0
Interrupt an unanswered overlapping prompt on cancellation
j-asefa Nov 21, 2026
afffcf4
Retain reactive work after late steering errors and usage
j-asefa Nov 21, 2026
261d4ac
Respect approvals from an acknowledged steering prompt
j-asefa Nov 21, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/harnesses.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,8 @@ Install [Antigravity CLI](https://antigravity.google/docs/getting-started?tab=cl

With **Antigravity CLI 1.5.9 or newer**, Loop uses the documented [ACP interface](https://antigravity.google/docs/ide/extensions/acp), launched with `agy acp --process-per-session`. Each native session receives its own authenticated Loop MCP connection through ACP session creation or resuming. This enables Agent mail, team delegation and Loop tool integrations without editing global or project MCP configuration. ACP must advertise HTTP MCP support; setup fails before sending a prompt if it does not. Enable Antigravity again after upgrading the CLI so Loop refreshes its saved runtime version and capabilities. Existing streaming sessions switch to ACP on their next turn; refreshing does not interrupt a running turn. See [session reuse](state-machines.md#companion_sessionsstate).

When Antigravity returns `end_turn` while a tool call or approval is still open, Loop keeps receiving output and approvals. For overlapping steering requests, Loop keeps waiting for inherited work that was open before steering. Otherwise, the final prompt response remains authoritative if all work has settled and reactive waiting has not started. An overlapping request that never resolves is subject to the one-hour watchdog. A tool that has already reported a terminal status cannot establish that another wakeup is pending. Antigravity can send usage updates both during a continuation and after its final text. Until ACP supplies a definitive completion signal, Loop bounds the wait and interrupts the run with its partial output preserved in the conversation trace. This can leave a successful background continuation without a published Result. Daemons identified before the prompt returns can outlive ordinary completed turns. A late daemon update can clear an open tool but does not certify completion after reactive waiting has begun. See the [upstream ACP discussion](https://github.com/google-antigravity/antigravity-cli/issues/1461).

Model discovery and session initialization send no model prompt. Saved instructions accompany explicit prompts, and interrupted tasks are never automatically replayed. Existing native conversation IDs and workspace bindings are retained when a newer runtime resumes a conversation created by the streaming adapter. Commands and skills come from the session’s ACP catalog. Catalog probes and slash-leading prompts or live replies wait up to five seconds for that catalog. A discovered command stays at the start of an explicit prompt, followed by saved instructions; other slash-leading text stays literal, including when discovery times out. Saved instructions starting with `/` also stay literal. The model catalog comes from ACP; if the account no longer offers a previously selected model through that interface, select an available model explicitly. Loop does not choose a replacement model after failure.

Antigravity requires `--billing existing`. Its native sign-in, billing and permission rules apply; Loop does not verify a subscription entitlement. ACP permission requests appear in Loop's approval flow. CLI 1.5.2–1.5.8 uses `agy acp` with approvals and live steering, while Agent mail and team delegation require 1.5.9 or newer. A reply during a running ACP turn uses another `session/prompt`; Loop waits for the original prompt echo, then confirms delivery from an exact reply echo or normal request completion. Replies wait while an approval is open. Unconfirmed replies are not automatically resent. Older streaming runtimes queue follow-ups for the next turn. Antigravity is not bundled in the Docker images.
Expand Down
Loading