Ambient and asynchronous
Event triggers
Event triggers start agent work in response to something happening, such as an email arriving, a build failing or a threshold being crossed, rather than in response to a prompt.
Control sits with the agent
When to use it
Recurring work with a clear signal, particularly work that is currently done by a person noticing something.
What it prevents
The interaction overhead of having to remember to ask.
Triggersno prompt involved
Build failsDiagnose, and open a draft fix
Invoice arrivesMatch to a purchase order, flag what does not fit
Stock under 20Draft the reorder, wait for approval
Nobody has to remember to ask.
Who ships it
- LangChain ambient agents: with an open-source email assistant as the reference implementation
Sources
Related patterns: Agent inbox