Show HN：SeaTicket——可处理 GitHub 和 Discord 问题的 AI Agent

https://seaticket.ai/

自 2012 年以来，我们一直在维护开源文件同步软件 Seafile。在这十四年间的某个时刻，“去看看是否已经有人报告过这个问题”变成了团队聊天中最常见的话之一。

因为同一个 Bug 往往会多次出现。在我们的团队恰好记得曾在别处见过“那个问题”之前，没有任何东西能把 GitHub 和 Discord 上的问题连接起来。

SeaTicket 是我们为自己解决这一问题后，再决定向外开放的产品。它将 GitHub Issues、Discord，以及 Notion、Confluence、Linear、Jira 等其他几个来源整合到同一个工作区。当有新问题进入时，AI Agent 会汇总相关问题、过往解决方案，以及知识库中所有相关内容，并提出下一步建议。

它不会自行发送消息、回复或关闭任何事项，因为会先等待对建议的批准。我们不希望发布一个能在无人监管下与自己用户交谈的产品，因此也不会要求其他人这么做。

真正困难的部分，是在不同来源之间匹配同一个底层问题：这些来源的描述几乎没有共同词汇。例如，一条只有两行的 Discord 评论和一份十行的 GitHub Bug 报告，可能追溯到同一个 Bug，却完全没有任何相同关键词。

如果 Hacker News 的朋友们想了解，我很乐意在评论中进一步介绍我们的处理方法；这是我最希望大家深入剖析的部分。

它面向那些问题并非通过单一队列进入的团队，尤其是开源维护者；当然，也适用于管理多个仓库和 Discord 服务器的产品与支持团队。它有意不把自己做成 Zendesk 或 Fin：那些产品假设支持团队在一个共享工单队列中工作，而我们的假设是，你的团队已经主要在 GitHub 中工作，并且希望问题就在 GitHub 中处理，而不是转移到另一个工具。

包括免费版在内的所有套餐均不收取按席位计费的费用。

我认为，分散在多个仓库和 Discord 中的 Bug 报告应该有一个可以集中解决的地方。我想知道这对你是否确实有用，还是我们正在解决一个你并不存在的问题。也很乐意回答任何关于其底层工作原理的问题。

https://seaticket.ai/

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.

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.

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.

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

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.