Example of a real working loop orchestrator
热度趋势
百分比基于当前可用热度信号，而非评论数或独立用户人数。
一位开发者分享了一个名为 Lloyd 的循环协调器实例，其主要目标是管理自己的内部工单表，在本例中是一个简单的 SQLite 表。Lloyd 已经成功管理了 600 多个工单，功能类似于内部 Jira 系统。这种设置使得协调器在出现新工单时能够查询以前相关的工单，从而提高其高效处理新任务的能力。开发者强调了为协调器提供数据库来管理自身内存的复合价值。
Wanted to give a little peak into what one of my loop orchestors looks like as a 20+ year senior engineer & designer, so people could see a real working example.
My orchestrator Lloyd's primary goal is managing it's own internal tickets table. In my example thats just a simple SQLite table. An orchestrator can do anything, so giving it a database to manage its own memory has compounding value. Lloyd has managed over 600 tickets for me that it can query (like it's own internal jira, that I can click through). This means every time I have a new ticket, it can look up previous related tickets. Just like any of us should when assigned new work.
It gives the agent a database of tribal knowledge that can be passed to any model.
https://preview.redd.it/0nyyd00bl7jh1.png?width=1940&format=png&auto=webp&s=f383811da3c23f3bc0645672291bcfa05e6de1ac
The main concept I want to point out is the heart beat, and the pulse action items.
- first it runs a playbook (automation script) to check my email for any new bug reports from customers, checks for previous context before staffing a ticket - checks if any docs need to be updated on the website - check's the own app's running logs to just see whats up -- this is such an important practice, it will surface bugs you didn't know existed because nobody reported them, and the logs didn't produce and error, but maybe a noisy problem. - adding it's own tickets for bugs and enhancements along the way, gives the agent a voice to surface ideas and problems for _me_ to triage as well.