• Home
  • Technology
  • Gaming
  • Entertainment
  • World & Business
  • Science
  • Sports
  • AI
HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
AI
Reaction

How DeepAgents could handle asynchronous subagent updates

A post weighs whether a finished subagent should interrupt a running parent agent or wait to batch its update.

Harrison ChaseHC
1 Source, 59m ago, first seen 59m ago

TLDR

The post’s author says they’re considering how to make DeepAgents more async-native. For a finished subagent, they outline two options while the parent agent is running: interrupt it and continue after applying the update, or wait until its run ends and batch the update with other messages. If the parent is paused for a human response, they ask whether the update should wait too or resume the thread, cancelling the pause and potentially prompting for approval again.

Combined views

—

1 Source, first seen 59m ago

— likes— comments— saves— reposts

Combined views

—

1 Source, first seen 59m ago

— likes— comments— saves— reposts

Sentiment

Positive——Negative

Summary

Not enough discussion yet.

No sentiment analysis available yet.

Featured Source

Sentiment

Positive——Negative

Summary

Not enough discussion yet.

No sentiment analysis available yet.

1 Source

Harrison Chase@hwchase17we 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?59m
    • Home
    • Technology
    • Gaming
    • Entertainment
    • World & Business
    • Science
    • Sports
    • AI

    1 Source

    Harrison Chase@hwchase17we 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?59m
    Today's Rank

    #7

    Today's Rank

    #7