R123 · Agent principles and patterns › Long-running agents and durable execution

Proactive agents: memory decides what's worth a check-in, UX decides if anyone answers

Read the original

long-running-agentsmemoryhuman-in-the-loopagent-uxscheduling

Source: Sydney Runkle, What We've Learned Building Proactive Agents (LangChain blog, 2026-11-17), shared by LangChain on LinkedIn. Lessons from two internal agents: GTM Agent (sales: watches leads and replies, sends daily briefs, drafts outbound email) and Robin (engineering, formerly Open SWE: drafts pull requests and reviews every new one). Both run on LangChain's Managed Deep Agents, where the post reports that more than 70% of runs now start from a schedule rather than a human prompt. The post is vendor-written and ends with a product pitch; the design lessons stand on their own.

The shape of a proactive agent

A proactive agent works toward a goal in the background and decides for itself when to come to a person. It wakes on three kinds of trigger:

When it wakes, there is no prompt saying what the person wants. Connectors bring fresh context (inbox, calendar, repo), but preferences and judgment come only from memory. Every check-in costs the person attention, so the core design problem is being proactive without being annoying. Human attention, not model context, becomes the scarce resource.

Memory: three signals, three maintenance problems

The post sorts memory inputs by time:

Storing memory is easy (often just a file). Keeping it useful is hard because the agent acts on whatever it remembers:

A common fix is "dreaming": a scheduled background job that reads recent traces and rewrites memory before the next run. To tell whether memory helps, track outcomes it should improve, such as time to approve a draft, reply rate, and, for any proactive agent, the share of its check-ins the person actually acts on. Memory is also what earns autonomy: once the person stops correcting a behavior (say, proposed meeting times), the agent can be trusted to do it alone.

UX: high signal, built for review, where people already work

The framing: context engineering for the model still matters, but proactive agents add context engineering for humans, giving the person the right context, in the right format, at the right time.

Tradeoffs

Failure modes to plan for

Review checklist

Connections

See R123 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.