Show HN：为编码 Agent 维护动态更新的事实真源
一位独立创始人希望让多个编码 Agent 并行工作，但不信任 AI 总能基于正确上下文作出决定；过去必须逐个检查会话，因此同时只能管理约 4 个。为减少人工瓶颈，他开发了 Meetless Agent（MLA）：监控编码 Agent 的任务与动作，补充最新上下文；持续核对文档、Agent 输出和决策，以维护当前事实真源；当操作触发仓库规则时，把规则注入 Agent 上下文。作者称其基准测试显示，这种主动监控可提高质量与准确性、减少 token、缩短完成时间。Agent 不能单独裁定事实真源，矛盾仍需要人类审核。作者计划把这一 AI 协调层扩展到 Slack、Jira、Confluence 等业务系统，使跨工具的决策与后续动作保持一致；编码 Agent 连接器已开源。
查看英文原文
Show HN: Active Source of Truth for Your Coding Agents
Howdy! Happy Saturday everyone! As a solo founder, I have always tried to maximize my speed by letting coding agents build as much as possible in parallel. However, as an engineer, I don't trust that AI will always make the right decisions and work with the right context. In the past, I always needed to click through my sessions to glance at the AI's output, try to understand what it was doing, and hopefully steer it or stop it in time. As a result, the maximum number of concurrent sessions I could manage at once was only 4. I didn't want to be the bottleneck, so I built Meetless Agent (MLA). It basically does what I had to do manually before: - Monitors the coding agent's tasks and actions to supply it with the correct, up-to-date context. - Continuously reconciles running information (such as provided/tagged documentation, the agent's output, and the agent's decisions) to actively maintain the source of truth at all times. - Keeps track of the current rules for the repo, and if an action triggers a registered rule, the rule is injected into the agent context. My benchmarks show that running coding agents with the help of an active monitor improves quality and accuracy, consumes fewer tokens, and finishes faster: https://research.meetless.ai/stale-context/ Of course, the agent alone can't decide the source of truth; it requires human review and decisions for contradictions, etc. But for the most part, it can safely build a consistent ontology of the current source of truth. From this, I want to build an AI layer to maintain the source of truth across the business, so I will release more connectors for Slack, Jira, Confluence, etc., soon. The goal is for this AI to assist in every part of the business. Eventually, the same coordination layer will understand that a decision made in Slack affects a Jira task, a document, an email conversation, and what a coding agent should do next without every tool becoming another isolated memory silo. The coding agent connector is open source at: https://github.com/Meetless/mla I am looking forward to your feedback!
Show HN: Active Source of Truth for Your Coding Agents
Howdy! Happy Saturday everyone!<p>As a solo founder, I have always tried to maximize my speed by letting coding agents build as much as possible in parallel. However, as an engineer, I don't trust that AI will always make the right decisions and work with the right context. In the past, I always needed to click through my sessions to glance at the AI's output, try to understand what it was doing, and hopefully steer it or stop it in time.<p>As a result, the maximum number of concurrent sessions I could manage at once was only 4. I didn't want to be the bottleneck, so I built Meetless Agent (MLA). It basically does what I had to do manually before:<p>- Monitors the coding agent's tasks and actions to supply it with the correct, up-to-date context.<p>- Continuously reconciles running information (such as provided/tagged documentation, the agent's output, and the agent's decisions) to actively maintain the source of truth at all times.<p>- Keeps track of the current rules for the repo, and if an action triggers a registered rule, the rule is injected into the agent context.<p>My benchmarks show that running coding agents with the help of an active monitor improves quality and accuracy, consumes fewer tokens, and finishes faster: <a href="https://research.meetless.ai/stale-context/" rel="nofollow">https://research.meetless.ai/stale-context/</a><p>Of course, the agent alone can't decide the source of truth; it requires human review and decisions for contradictions, etc. But for the most part, it can safely build a consistent ontology of the current source of truth.<p>From this, I want to build an AI layer to maintain the source of truth across the business, so I will release more connectors for Slack, Jira, Confluence, etc., soon. The goal is for this AI to assist in every part of the business. Eventually, the same coordination layer will understand that a decision made in Slack affects a Jira task, a document, an email conversation, and what a coding agent should do next without every tool becoming another isolated memory silo.<p>The coding agent connector is open source at: <a href="https://github.com/Meetless/mla" rel="nofollow">https://github.com/Meetless/mla</a><p>I am looking forward to your feedback!
- 来源
- Show HN · show-hn
- 证据角色
- project_and_comment_discovery
- 时间状态
- known
- 用户判决
- 未判