Harrison Chase outlines async subagent notification options for deepagents
Overview
Harrison Chase, LangChain's head of agent work, says the most interesting agent harness work sits at the intersection of harness and infrastructure.
In an X post on October 15, 2026, he cites four examples: dreaming, async subagents, heartbeats, and agent-scheduled reminders. He says all four belong in managed deep agents and gives this as his reason for being bullish on managed agent platforms. The post is a statement of view and does not describe a released feature or pricing.
Written by AI from the articles below · updated Oct 15, 3:50 PM ET
Check the sources:
Developments
2 developments
- Oct 15, 3:23 PM ET · 1 articleHarrison Chase says agent harness work is moving to infrastructure layerHarrison Chase: Harrison Chase says agent harness work is moving to infrastructure layer
- Oct 13, 5:23 AM ET · 1 articleHarrison Chase outlines async subagent notification options for deepagentsHarrison Chase: Harrison Chase outlines async subagent notification options for deepagents
Article timeline
The articles in this story. Times are ET.
Harrison Chase@hwchase17XHarrison Chase says agent harness work is moving to infrastructure layerAIHarrison Chase says the most interesting agent harness work is at the intersection of harness and infrastructure, citing dreaming, async subagents, heartbeats, and agent-scheduled reminders. He says this is a reason he is bullish on managed agent platforms, and that all four belong in managed deep agents.
Harrison Chase@hwchase17XHarrison Chase outlines async subagent notification options for deepagentsAIHarrison 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.
Heat trend
- Current comparable heat
- 5
- Peak comparable heat
- 10Oct 13, 6:00 AM ET
- Change in past 24 hours
- -51%
The trend compares only continuously observed participants, so its scope may be smaller than the current heat total. Hover or tap for hourly heat; use arrow keys with a keyboard.