Background Agent (GitHub, Slack, Linear,…)
Using Cloud Agents, I want to delegate browser validation to another sub-agent to keep the main agent’s context window un-polluted.
But sub-agents do not have the Task tool available to spawn computerUse sub-agents.
Hey @Kaarel_Reinvars!
When your cloud agent spawns computerUse directly today, only its final assistant message is returned to the parent. All the screenshots, clicks, and intermediate turns stay inside the subagent and never enter the main agent’s context. I’m curious what context are you actually seeing pollute the main agent! Would be really helpful to understand.
Hey @Colin!
I’d like to have the whole manual browser validation step inside a separate sub-agent to avoid the related context, e.g. starting the stack locally, deciding what flows exactly need to be tested and so on to stop polluting the main agent’s context.
So basically, I’d expect the main agent to spawn a validator sub-agent that then spawns computerUse sub-agents itself.