Post

"How does the harness handle long-running shell commands" turns out to be I think the most consequential question for overall satisfaction for me personally. Antigravity actually nails this. After a short timeout, the command goes into the background and retriggers on complete.

0 reposts1 like

This lets you continue work in the session while waiting for e.g. a long deploy. It can also schedule self timers to check in on progress of long running scripts. Huge QoL improvement and something I miss when I'm using agents that don't have it.

I've actually been quite frustrated with Antigravity here, or at least the way it communicates it. Long-running commands eventually complete. Why does it need to set a timer? Copilot just gets notified by the harness when the command is done and then continues.

It *does* notify on complete! You're right, this is a little UX bump because it's not obvious that it does/will, and it sets timers sometimes to check on the progress intermittently. I forgot about that because I got used to it.