execution subagent doesn't work with new async terminal stuff

[roblourens]

Testing #307987

The execution subagent only gets the run_in_terminal tool, so it can't check the output of terminals or do other things. Also, since it wants to finish its task before yielding, I see it just do random stuff while waiting until it runs out of turns

8405ab43.copilotmd

But even if it did have those tools, the async terminal strategy seems awkward with the execution subagent. If it starts async tasks, then yields, then the main agent gets the notification that the task is done, will the main agent have the right context to take action on that? Maybe, but that just needs some thinking for different scenarios.

cc @vikramnitin9

[roblourens]

Or, if it starts a sync task, which times out, so it can't complete its work. It will yield back to the main agent with unfinished work and tasks running.

[meganrogge]

The timing out of sync/async before was also possible.

If it starts async tasks, then yields, then the main agent gets the notification that the task is done, will the main agent have the right context to take action on that?

I do not know this. Maybe we could pass something in to run_in_terminal that indicates the subagent is invoking it and thus not register the listeners?

[meganrogge]

@roblourens what terminal commands did you give it & see weird things?

[meganrogge]

Also note that this happened before the async work too