Skip to content
View original post on X: Harrison ChaseX· 24/100AI score24/100

Harrison Chase outlines async subagent notification options for deepagents

AISummary

Harrison Chase says LangChain is working to make deepagents more async native, with better support for async subagents.

He lays out two options for notifying a parent agent that is still running: interrupting it to apply the update, or batching the update after the run finishes.

For a paused parent awaiting human approval, he proposes either batching the update with the human response or resuming the thread, which would cancel the interrupt.

Post on XView on X
Harrison ChaseVerified on X
@hwchase17

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?

Source: Harrison Chase · x.comPublished · added here