Why your Mac sleeps while Antigravity's agents are still going
Antigravity's agents spend most of a run waiting on the model — planning, generating code, verifying results — and waiting on a model response barely uses any CPU. But macOS doesn't decide from CPU at all — it goes by your idle time, how long since real keyboard or mouse input, plus the power assertions running processes hold. So a busy Mac sleeps on exactly the same schedule as an idle one. After your screen-sleep or system-sleep timer runs out, macOS suspends the Mac, and every agent in the Agent Manager is frozen along with it until you wake it back up.
Antigravity makes this worse than a normal IDE, in a good way: the whole point of the Agent Manager is dispatching agents to work asynchronously while you do something else. The moment you walk away is exactly when your sleep timer starts counting down.
The fix is to stop macOS from sleeping for as long as the agents are actually running — then let it sleep normally again shortly after they go quiet — within your grace window, 90 seconds by default. You can do that for free in two minutes, or with a tool that knows the difference between "agent working" and "agent idle" so you don't have to babysit it.