Evidence · DiggingBeagle record
AG-UI protocol issue 2525: no expiresAt causes pending interrupt lock
The AG-UI issue documents a valid RUN_FINISHED interrupt outcome without expiresAt under @ag-ui/client 0.0.58 and shows subsequent runAgent calls failing to settle until all pending interrupt IDs are explicitly resumed.
- Source role
- primary disclosure
Evidence record
The AG-UI issue documents a valid RUN_FINISHED interrupt outcome without expiresAt under @ag-ui/client 0.0.58 and shows subsequent runAgent calls failing to settle until all pending interrupt IDs are explicitly resumed.
Claim-level citations (1)
- supportsAG-UI client could leave an agent thread blocked by interrupts with no expiry: The AG-UI issue documents a valid RUN_FINISHED interrupt outcome without expiresAt under @ag-ui/client 0.0.58 and shows subsequent runAgent calls failing to settle until all pending interrupt IDs are explicitly resumed.
Issue 2525, @ag-ui/client 0.0.58 reproduction and isInterruptExpired behavior