discatch buddy, listeningdiscatch
Get a key

discatch for devrel

Developer conversation happens in threads, not feeds. The questions your docs should answer are asked on Hacker News, Discourse forums, GitHub Issues, and Stack Overflow. discatch reads these sources directly, keeps the thread context on every result, scores them with a free prescore, and pushes to whoever owns the area. The changelog-listen playbook catches reactions to a release and routes each to the engineer who owns the feature. The forum-triage playbook watches a Discourse forum, classifies threads, and files bugs to GitHub with a link back. discatch is not an AI-visibility tool. It delivers mentions from public developer conversation to your agent, not mentions inside ChatGPT answers.

Threads, not just posts
Every result carries parent_url, reply count, and score. A mention in comment seven of a Hacker News thread arrives with the full thread it belongs to. A Stack Overflow question arrives with its answer count and accepted state. Your agent has the context to decide whether to act.
Route by owner
The changelog-listen playbook reads your changelog, builds one query per feature name plus the version string, and registers a catch per query. Each catch routes to the owning engineer through a webhook or a Doozy todo. Catches live for about a week and cost nothing when they fire nothing.
Forum triage
Watch any public Discourse forum by URL with a site: query. The forum-triage playbook classifies threads into bug, question, feature request, or praise using the classify flag and your own criteria. Bugs file to GitHub Issues with a link back. Questions route to whoever answers them.
Relevance your way
A free, non-LLM prescore on every result ranks and filters without cost. It weights exact phrase hits, term coverage, title hits, recency, engagement, and a per-account source weight. Pass classify with your own criteria for an LLM verdict on relevance, sentiment, and intent, charged as a classify unit.
One query syntax
Quotes, AND, OR, NOT, site:, author:, lang:, and grouping with parentheses. Translated per source by the planner, then re-filtered locally so every source returns correct results. site:community.example.com restricts to one Discourse forum. repo:owner/name restricts to one GitHub repository.
An event log you can replay
Every result every catch finds is appended to one per-account, append-only event log. Agents read it from a cursor and never lose an event. Change your handler and re-read from an older cursor. Stream it over SSE or subscribe targets to it. Nothing is lost while your agent was asleep.

Playbooks for you

forum-triage

Forum triage
Watches a Discourse forum by URL, classifies threads into bug, question, feature request, or praise, and files bugs to GitHub Issues with a link back.
alertresultclassify

changelog-listen

Changelog listen
After a release, catches reactions mentioning the version or the feature names from the changelog and routes each to the engineer who owns that area.
alertresult

reply-draft

Reply draft
Given a catch firing, your own agent drafts a reply in your voice and puts it where you can review and post it.
alertresult

Questions

Can I watch one forum or one repository?

Yes. site:community.example.com restricts a query to one Discourse forum. repo:owner/name restricts to one GitHub repository. Both work in one-off searches and in standing catches. Combine them with boolean operators and grouping with parentheses to watch several forums or repos in one catch. The planner translates the query per source and re-filters locally.

How is this different from GitHub notifications?

GitHub notifications tell you about activity in your own repositories. discatch catches issues in other repositories that mention your tool by name, READMEs that list your package, Stack Overflow questions about your API, and forum threads on Discourse and Hacker News that GitHub never sees. It crosses the boundary between your code and the conversation about your code.

Does it post replies?

Never. The reply-draft playbook has your agent draft in your voice using a voice file and a set of rules. You review the draft and post through the platform’s own interface. discatch never posts on any platform on your behalf. Reddit removed 40M or more spam posts in H1 2025.

Can I route different types of mentions to different people?

Yes. Use the forum-triage playbook with the classify flag. You pass your own criteria, such as bug, question, feature request, or praise. Threads classified as bugs route to the engineer who owns the area through a webhook or a GitHub dispatch. Questions route to whoever answers them. Each catch has its own destination, so the routing is per query.

What is the changelog-listen playbook?

After a release, it reads your changelog, builds one query per feature name plus the version string, and registers a catch per query at one hour across Hacker News, GitHub, Discourse, and the web. Each catch routes to the owning engineer through a webhook or a Doozy todo. Catches live for about a week and cost nothing when they fire nothing.

Does discatch cover Stack Overflow?

Yes. Stack Overflow and the other Stack Exchange sites are a first-class source with no listening-vendor pages. Zero vendor pages exist for the "Stack Overflow keyword alerts" query today. The DevRel angle: catch the questions nobody answered and route them to the person who should.

What sources does developer conversation happen on?

Hacker News, Discourse forums, GitHub Issues and Discussions, Stack Overflow, web, and news are the live sources today. These are where developers ask questions, file bugs, compare tools, and discuss releases. Bluesky, Mastodon, YouTube, and Product Hunt are planned. Reddit, X, and LinkedIn are reserved until a cleared path exists.

Can I track reactions to a new feature across all sources?

Yes. The changelog-listen playbook builds one query per feature name plus the version string and registers a catch per query across Hacker News, GitHub, Discourse, and the web. Each catch routes to the owning engineer. Run them for a week; catches that fire nothing cost nothing.

What does it cost for a DevRel team?

Free on free sources with no credit card. A trial key gives a daily unit allowance on Hacker News, Discourse, GitHub, and Stack Overflow. Starter at $19 a month adds catches at 15 minutes across all sources with a unit bundle. The quote says the exact cost before each call and the charge never exceeds it. No per-keyword charge.

Is there an MCP server?

Planned for roadmap phase 3, with OAuth 2.1 and PKCE at mcp.discatch.com. Until it ships the REST API with a trial key is the surface. Catches push independently of MCP because MCP is pull-only by spec. Both reach the same account once claimed.

Last reviewed by , founder, dcouple. Copy from docs/vision.md, docs/onboarding.md, docs/playbooks.md.