SeaTicket: AI agent unifies GitHub and Discord issues

SeaTicket began as an internal tool. The Seafile team, which has maintained open-source file-sync software since 2012, realized that duplicate bug reports scattered across GitHub Issues and Discord created unnecessary friction. The same underlying issue would surface multiple times, forcing maintainers to search backward through conversations to check whether a problem had already been reported or solved. No existing tool connected these platforms seamlessly.

The team built SeaTicket to solve this for themselves, then decided to open it to other teams. The tool ingests issues and conversations from GitHub Issues and Discord, along with knowledge stored in Notion, Confluence, Linear, and Jira. When a new issue arrives, an AI agent retrieves related issues, past resolutions, and relevant knowledge-base content, then proposes a next step. Importantly, it does not act unilaterally: every suggestion awaits human approval before the tool sends a reply, closes an issue, or interacts with users. This constraint reflects the builders' conviction that automation in user-facing workflows should remain supervised.

The technical hardest problem has been matching identical issues across sources with radically different vocabularies and levels of detail. A two-line Discord comment ("app crashes on upload") and a ten-line GitHub bug report with stack trace and environment details may describe the same root cause but share no keywords. The builders' matching algorithm solves this by understanding the semantic content beneath surface language—a capability that required the most engineering focus.

SeaTicket is positioned for open-source maintainers, product teams, and support teams that manage multiple repositories and Discord servers. It explicitly avoids the assumptions of platforms like Zendesk or Fin, which organize work around a shared support-ticket queue staffed by dedicated support personnel. Instead, SeaTicket assumes teams prefer to keep issues in GitHub rather than adopting yet another tool, and that issues arrive through multiple uncontrolled channels. Pricing includes a free plan and paid tiers, neither with per-seat charges. The builders are soliciting feedback on whether the underlying problem—scattered bug reports across platforms—is one that users actually feel as a bottleneck.

The problem SeaTicket targets is rooted in the workflow reality of distributed teams. After fourteen years maintaining Seafile, the builders noticed "go check if someone already reported this" became one of the most common lines in their team chat, because the same bug appeared multiple times across unconnected channels. GitHub Issues and Discord have become the de facto homes for issue tracking in open-source and modern product teams, but neither platform was designed to deduplicate reports across both—let alone across Notion wikis, Confluence documentation, Linear backlogs, or Jira instances. The core innovation is semantic matching: aligning a fragmentary Discord comment with a formal GitHub bug report despite zero keyword overlap. This differs fundamentally from support platforms like Zendesk or Fin, which assume a centralized queue and dedicated support staff. SeaTicket instead assumes teams already live in GitHub and Discord and want to keep issues there, avoiding the friction of context-switching to a separate tool. The builders' insistence on human approval before any action—no unsupervised replies or closures—also reflects a conservative stance on automation in customer-facing workflows.

No comments yet. Be the first to share your thoughts!