How WorkBuddy 5.8.4 Organizes Experts and Expert Teams
掘金 · 人工智能 reports that WorkBuddy 5.8.4 represents each expert as a directory-based plugin package and injects developer-written persona text into a {{ PluginAgentPrompt }} slot when the expert is selected. Expert teams add role-specific members, staged workflows, shared task tools, message protocols, and shutdown procedures, while tool permissions remain controlled by the runtime. The report also identifies conflicting guidance over whether members should communicate directly or route all cross-member communication through the team lead.
The account offers a concrete view of how WorkBuddy separates persona configuration from runtime permissions and how it coordinates multiple agents, while highlighting that conflicting collaboration rules can undermine multi-agent behavior.
在workbuddy提示词组装时,我们可以看到有个 {{ PluginAgentPrompt }} 槽位,收集器会往里填专家人格。这个槽位是整条链路里最特殊的一块——其它变量都来自系统和会话状态,只有它,内容是由第三方开发者写的。所以这篇把专家这件事单独拆开。
在 WorkBuddy 里点一个专家,表面上是换了个名字和头像。实际发生的事要多一些:会话模板切分支,人格正文被塞进固定槽位,后续轮次还会收到提醒「现在是谁在说话」。如果选的是专家团,背后还会多出一组团队工具和一套关机流程。
本文的顺序照着这条链路走:专家以什么形式存在(一个插件目录)→ 怎么创建和校验 → 人格怎么进会话 → 没选专家时系统怎么推荐 → 多个专家组队时靠什么协作,以及规范层和运行时层打架的地方。
#WorkBuddy#WorkBuddy 5.8.4#TeamCreate#TeamDelete#SendMessage#TaskOutput