展示HN：SeaTicket – 一款能够解决GitHub和Discord问题的AI代理
在维护开源文件同步软件 Seafile 以来的 14 年里，“去检查一下是否有人已经报告过这个问题”成为我们团队聊天中最常见的台词之一，因为同样的 bug 往往会多次出现。在我们团队想起在其他地方见过“那个东西”之前，GitHub 和 Discord 问题之间并没有任何连接。
SeaTicket 是我们为了解决这个问题而构建的工具，然后才决定将其开放给其他人使用。它将 GitHub 问题、Discord 以及 Notion、Confluence、Linear、Jira 等其他来源连接到一个工作区。当有新问题出现时，AI 代理会汇总相关的问题、过去的解决方案以及知识库中任何相关的信息，并提出下一步的建议。它不会自行发送、回复或关闭任何内容，因为它首先会等待对其建议的批准。我们不想发布一个可以不受监督地与用户对话的工具，因此我们也不希望其他人这样做。
真正困难的部分是将不同来源中几乎没有共享词汇的相同基础问题进行匹配，比如一个两行的 Discord 评论和一个十行的 GitHub Bug 可能指向同一个 bug，但却没有任何关键词。如果 HNPs 愿意，我很乐意在评论中详细说明我们是如何处理这个问题的；这是我最想深入探讨的部分。
这个工具是为那些问题不是通过单一队列到达的团队而设计的，特别是开源维护者，但也适用于管理多个代码库和 Discord 服务器的产品和支持团队。它故意不想成为 Zendesk 或 Fin，因为这些工具假设支持团队在处理共享的工单队列，而我们假设你的团队已经在 GitHub 中工作，并希望在那儿处理问题，而不是在一个单独的工具中。所有计划，包括免费计划，都没有按座位收费。
我认为分散在多个代码库和 Discord 中的 bug 报告必须有一个地方可以解决。我想知道这对你是否真的有用，或者我们是否在解决一个你并不存在的问题。欢迎随时询问关于其内部运作的任何问题。
查看原文
<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.