LangChain says most Managed Deep Agents runs now come from schedules
Overview
LangChain says more than 70% of Managed Deep Agent (MDA) runs on LangSmith are triggered by schedules rather than by a person typing a message.
The company gives this figure for the period since it launched dynamic scheduling for MDA in September.
In a LangChain Blog post, the company says nearly all emerging proactive agents run as cron tasks that start agent runs on a schedule. It names four cron-driven behaviors: memory consolidation, proactive messages, smart triage, and follow-up reminders.
LangChain says teams can distribute a proactive agent across their organization using the mda init and mda deploy commands.
Written by AI from the articles below · updated Oct 28, 1:03 PM ET
Check the sources:
Developments
2 developments
- Oct 28, 12:18 PM ET · 1 articleLangChain describes building proactive agents with Managed Deep Agents and scheduled runsLangChain: LangChain says over 70% of Managed Deep Agents runs are scheduled
- Oct 28, 12:00 AM ET · 1 articleLangChain explains how cron jobs power proactive, always-on AI agentsLangChain Blog: LangChain explains how cron jobs power proactive, always-on AI agents
Article timeline
The articles in this story. Times are ET.
LangChain@LangChainOfficialLangChain says over 70% of Managed Deep Agents runs are scheduledAILangChain says over 70% of Managed Deep Agents runs on LangSmith come from schedules rather than human messages, since it launched dynamic scheduling in September. It says teams can distribute a proactive agent in their organization with mda init and mda deploy.

- LangChain BlogOfficialLangChain explains how cron jobs power proactive, always-on AI agents
AILangChain says nearly all emerging proactive agents run as cron tasks that trigger agent runs on a schedule. The post names four cron-driven behaviors: memory consolidation, proactive messages, smart triage, and follow-up reminders. It says more than 70% of Managed Deep Agent runs on LangSmith come from scheduled runs rather than a human typing a message.
Heat Trend
- Current comparable heat
- 16
- Peak comparable heat
- 17Oct 28, 1:00 PM ET
- Change in past 24 hours
- –
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.