mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-07 22:36:35 +02:00
ac84b8c70c
agy's --print-timeout defaults to 5m when the flag is omitted, but the daemon treated "omit the flag" as "no cap". In the default no-cap config every Antigravity turn was therefore silently capped at 5 minutes: any run whose build/tests outlived the budget had agy abort mid-turn, print "Error: timed out waiting for response", and exit 0 — which the backend recorded as a successful "completed" with truncated output (the reported "Antigravity disconnects", MUL-3570 / #4453). - Always pass --print-timeout: the configured cap when positive, else a large value (24h) that defers to the daemon's idle/tool watchdogs. - Detect agy's print-mode timeout marker in the run log and surface the result as a timeout instead of a truncated success. Verified by reproducing against agy 1.0.8 and with new unit + end-to-end backend tests. Co-authored-by: J <j@multica.ai> Co-authored-by: multica-agent <github@multica.ai>