Skip to content

Keep Antigravity ACP turns open for reactive wakeups - #412

Open
j-asefa wants to merge 31 commits into
mainfrom
fix/antigravity-reactive-wakeups
Open

j-asefa wants to merge 31 commits into
mainfrom
fix/antigravity-reactive-wakeups

Conversation

@j-asefa

@j-asefa j-asefa commented Nov 21, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Keep Antigravity ACP turns active across tracked background work, reactive updates, steering, and approvals. Daemons identified before end_turn do not keep a turn open. Late daemon metadata cannot certify a Result.
  • Preserve streamed reactive output in the conversation trace. Usage and idle time do not certify completion. If Antigravity never confirms completion, Loop interrupts and retires the live session without publishing a Result.
  • Bound settled reactive waits with a 60-second idle timer and stalled work with an hour of active time, excluding approval waits.

Verification

Submitted revision: 261d4ac31. Focused fixtures passed with 93 ACP adapter tests and 34 Antigravity integration tests. The integration fixture verified persisted reactive text after interruption and an unpublished Result. npm run check exited 0 with 445 contract tests. GitHub CI was still running at the last observation.

A prior live agy 1.5.14 trace on Linux received unsolicited tool and text updates after the first prompt response, but no explicit reactive end event. The conservative timeout policy was verified with fixtures. The request for a documented completion signal is upstream.

Limitation

ACP can make a synchronous steered command and an async command whose continuation has not yet announced itself look identical once their tool status and steering response have both settled. The fallback protects observed reactive work and does not establish a guarantee for that ordering.

Review

The conservative revision removes the quiet-interval publication path flagged by the previous review. Loop review 61a828fb-2bf9-485a-89cf-6294caf94e31 completed with all three reviewers responding. Merge remains blocked. The review identified ambiguous ownership for a tool across two steers and an approval that precedes its steer echo. The observed reactive-wait fallback is implemented, but these overlapping cases lack an authoritative association between ACP updates and their originating prompt or continuation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant