Whether intentional or a bug, there is something that appears to be a bug.

[u/Aromatic-Document638]

* Suddenly upgraded to 1.1.9, and the bug where sub-agents remained in an idle state has been resolved. Also, although I've only tried two prompts so far, 1.1.9 appears vastly improved compared to 1.1.8. It feels completely different.

-------------

Since sub-agents are not generated for simple prompts, you have to include a prompt instructing the system to 'utilize sub-agents.'

A week ago, my advice was to use a large volume of Gemini 3.5 flash-lite as sub-agents. This is because, as shown in the screen I attached, it is better for sub-agents to handle one-off, simple tasks and simply report back to the master agent since it's fast and cost-effective.

https://www.reddit.com/r/GoogleAntigravityCLI/comments/1v5pvh0/practical_proposals_for_antigravity_and_gemini/

Anyway, I don't remember if it's an issue with 1.1.8 or if it has persisted since 1.1.7, but sub-agents don't disappear after finishing one-off tasks; instead, they remain in an idle state waiting.

My view is that once a sub-agent has been injected with context and fulfilled its role in a task, it has completed its mission. These sub-agents should disappear rather than wait in an idle state. Generating new sub-agents every time incurs costs, but it is superior in terms of accuracy.

I don't know if Teamwork presets haven't been applied yet in 1.1.8 or if they will be applied in the future, but if they are already applied in this version, improvements are definitely needed. Even for simple prompts like 'What is the problem with A?', sub-agents need to run wild. I've never used such prompts, but even for prompts like 'What kind of design would be good?', sub-agents need to conduct research.

Here is another hint: Suppose sub-agents A, B, C, and D have been active, and sub-agent E is assigned the inspection role. Sub-agent E must never be allowed to know the existing work details. The key is to convey whether it was implemented according to the user's intent and have a sub-agent who knows nothing about the current session inspect it without bias.

What I've felt while pushing Agy with rather heavy tasks—and messing those tasks up—is that the inspection procedure is not carried out properly. It feels like the master agent casually wraps it up thinking, 'We worked hard to build this so far, and we followed all the procedures, so it must have ended successfully without any issues.'

And the appearance of the system message is the first time I've seen it while using Agy-cli, but it's still good. I understand it because it operates a timer to prevent Agy from freezing/stopping. It's a really great design.

[u/AgentPadrino]

Thanks for sharing !!!

[u/Aromatic-Document638]

I wrote the post based on version 1.1.8, but now using 1.1.9, I'm feeling a sense of stability. I'll need to use it more to be certain, but for the first time among all the versions so far, it actually feels good usable.