Repository navigation
v0.25.2
Update if you run this on a Mac. The wrapper could hold a CPU core at 99% for minutes to hours after agy had already finished its work successfully.
/plugin marketplace update antigravity-for-claude-code
/reload-plugins
Reported and fixed by @MoonCaves in #66 / #67, with regression tests in #68.
Two places asked "did this output contain anything but whitespace?" by deleting every whitespace character from the whole string. On the bash macOS ships — 3.2.57, frozen in 2007, and what /usr/bin/env bash resolves to on a stock Mac — that is catastrophically slow: measured at 24 s for 8 KB, with every doubling costing about 6x. Two real background jobs sat at 99% CPU for 24 minutes and for over 2 hours. It is also not interruptible, so no wall-clock guard could bound it and agy-job status kept reporting running.
Both now use a glob that stops at the first non-whitespace character. Same whitespace set, same exit codes, ~0.01 s at 64 KB.
Reviewing that fix turned up the same shape in cloud-debug.sh, deciding whether gcloud logging read returned any logs — and its 200 KB cap is applied after that check, so a chatty service could pin a core before the cap ever ran. Fixed too.
Why 305 tests on a bash-3.2 machine never saw it: the cost switches on whether there is a match at all, not how many, and both large fixtures in the suite happened to contain no whitespace — 20 KB of solid x, and solid A inside JSON. Both now have whitespace-bearing counterparts, bounded so a regression fails in 30 s instead of hanging CI.
308 tests.