展示 HN：SeaTicket – 解决 GitHub 和 Discord 问题的 AI 代理
2 分•作者: Daniel-Pan•13 天前
<a href="https://seaticket.ai/" rel="nofollow">https://seaticket.ai/</a><p>自 2012 年以来，我们一直在维护开源文件同步软件 Seafile。在这十四年间，“去看看是否有人已经报告过这个问题”成了我们团队聊天中最常说的一句话。因为同一个 bug 经常会重复出现。在我的团队偶然想起“那个东西”在别处也出现过之前，GitHub 和 Discord 的问题之间没有任何联系。</p><p>SeaTicket 是我们为了解决这个问题而自行开发的产品，之后才对外开放。它将 GitHub Issues 和 Discord 与 Notion、Confluence、Linear、Jira 等其他一些来源整合到一个工作空间中。当有新问题出现时，AI 代理会汇总相关问题、过往解决方案以及知识库中的任何相关信息，并提出下一步操作建议。它不会自行发送、回复或关闭任何内容，因为它会等待建议获得批准。我们不希望发布一个可以自行与用户沟通的产品，因此我们也不要求其他人这样做。</p><p>真正困难的部分在于，如何跨越那些几乎没有共享词汇的来源匹配同一个潜在问题，例如一个两行的 Discord 评论和一个十行的 GitHub Bug 可能指向同一个 bug，但却没有任何关键词的重叠。如果 HNPs 感兴趣，我很乐意在评论区详细介绍我们是如何解决这个问题的；这是我最希望被深入探讨的部分。</p><p>它专为问题不会通过单一渠道进入的团队而设计，尤其是开源维护者，同时也适用于管理多个代码仓库和 Discord 服务器的产品和支持团队。它并非有意成为 Zendesk 或 Fin 的替代品：那些工具假设有一个支持团队在处理共享的工单队列，而我们则认为您的团队已经在使用 GitHub，并希望在那里处理问题，而不是在一个单独的工具中。所有套餐（包括免费套餐）均无按用户收费的定价。</p><p>我认为分散在不同代码仓库和 Discord 中的 bug 报告必须有一个统一的解决地点。我想了解这是否真的对您有用，或者我们是否在解决一个您并不存在的问题。我很乐意回答关于其内部工作原理的任何问题。</p>
查看原文
<a href="https://seaticket.ai/" rel="nofollow">https://seaticket.ai/</a><p>After maintaining Seafile, open-source file-sync software, since 2012. Somewhere across those fourteen years, "go check if someone already reported this" turned into one of the most common lines in our team chat. Because the same bug tended to show up multiple times. Nothing connected Github and Discord Issues until my team happened to remember seeing "that thing" somewhere else.<p>SeaTicket is what we built to fix that for ourselves before opening it up. It connects GitHub Issues, and Discords with a handful of other sources like Notion, Confluence, Linear, Jira into one workspace. When something new comes in, the AI agent pulls together related issues, past resolutions, and anything relevant in your knowledge base, and proposes a next step. It doesn't send, reply, or close anything by itself because it waits for the approval of its suggestion first. We didn't want to ship something that talks to our own users unsupervised, so we're not asking anyone else to either.<p>The genuinely hard part has been matching the same underlying issue across sources that describe it in almost no shared vocabulary like a two-line Discord comment and a ten-line Github Bug can be trace to the same bug and share zero keywords. Happy to go into how we approach that in the comments if HNPs want it; it's the part I'd most enjoy having picked apart.<p>It's built for teams whose issues don't arrive through one queue like open-source maintainers especially, but also product and support teams managing multiple repos and Discord servers. It's deliberately not trying to be Zendesk or Fin: those assume a support team working a shared ticket queue, and we assume your team already lives in GitHub and wants issues handled there, not in a separate tool. Pricing has no per-seat cost on any plan, including a free one<p>i think bug reports scattered across repos and Discord must have a one place that they can be resolved, I'd like to know whether this is actually useful to you or whether we're solving a problem you don't have. Happy to answer anything about how it works under the hood.