做自动化工作流的开发者终于有了更优雅的循环机制——Fleet 的触发器+智能体组合让 AI 在后台持续运行，省去手动轮询的麻烦，建议试试。
LangChain 创始人 Harrison Chase 在 X 上分享了 Fleet 平台中“循环”与“触发器”的概念。循环是指 AI 在后台反复执行某个过程，而触发器则是启动循环的机制，例如定时任务、邮件或 Slack 消息。用户无需手动定义循环，只需将触发器连接到智能体，智能体就能在触发时自动获取上下文并执行任务。Fleet 目前已经支持通过视频演示的这种方式构建循环，适合自动化工作流的开发者。
loops are great because its just ai running in the background "triggers" are the way we kick those ...
loops are great because its just ai running in the background "triggers" are the way we kick those off in fleet Caspar Broekhuizen @caspar_br What are loops, and how do you build one? A "loop" is the repeated process where some event or input kicks off an action. For example: 1. CI fails -> you fix it 2. CI fails again -> you fix it 3. CI passes -> merge That loop resolved in three iterations. Others may run much longer, but every loop begins the same way: with a trigger. Therefore, building effective loops starts with designing good triggers In Fleet, we don't make you define loops directly. You create one (often without realizing it) whenever you connect a recurring trigger to an agent. A trigger can be an event, like a daily 9am alert, or an input, like an email When a trigger fires, your agent gets the full input as context (the email, Slack thread, or whatever kicked it off). For scheduled triggers, you provide the context yourself: what the agent should do, and which skills it should use Made a quick video to show these features off. You can start building loops in Fleet today fleet.langchain.com Your browser does not support the video tag. 🔗 View on Twitter 🔗 View Quoted Tweet 💬 5 🔄 4 ❤️ 22 👀 2900 📊 8 ⚡