Harrison Chase

we are thinking a lot about how to make deepagents more async native. specifically about making async subagents work better/more prominent one key question is how does a finished subagent "notify" the parent agent? some default behaviors we're considering for when the parent is still running: 1/ interrupt parent run, apply subagent update, continue (basically same as "steer") 2/ wait for parent run to finish, then batch subagent update with any other new messages (basically same as "queue") another question is how to handle human in the loop? what if main agent is not running but paused and waiting explicit human response to an action? a/ wait for human to respond, then batch the subagent update with that b/ resume thread (which would cancel the human interrupt) with the subagent update (thread could then re-ask for the same human approval) any other options we're missing?