Can FishOut create GitHub issues?

No. Your assistant needs its own GitHub connection — GitHub’s official MCP server, for example — or a Linear connector. FishOut supplies the reports.

Which platforms find the most bug reports?

GitHub, for anyone with an SDK or CLI; then Hacker News and the technical subreddits. Error strings make the best keywords.

Does it work on Free?

Yes. GitHub, Hacker News and Reddit are all on Free, and nothing in this playbook needs a paid feature.

Playbook · Weekly, or after each release

Turn public bug reports into issues in your tracker

People report bugs where they already are — someone else’s GitHub repo, an HN thread, a subreddit — and rarely in your tracker. This playbook finds them in FishOut and has your assistant file them through its own GitHub or Linear connection, linked back to where they were said.

Start free Connect your assistant

[01] THE PROMPT/ COPY IT

Paste this

Fill in the {{braces}}. Run below: Claude Code.

prompt

Using FishOut, list mentions from the last {{7}} days labelled has-a-problem on GitHub, Hacker News and Reddit with relevance of at least {{50}}. Open each, decide whether it is a real bug in our product, and group duplicates. For each real bug, file one issue in {{our GitHub repo or Linear team}} with your own connector, linking every report. Then archive those mentions in FishOut — ask me before you do.

[02] WHAT IT CALLS/ 4 TOOLS

Tools and arguments

2 of 4 read only.

ToolWhat it does hereArguments

list_mentionsread-only
Problem reports on the technical platforms.
filter: {"labels":["has-a-problem"],"platforms":["github","hackernews","reddit"],"minRelevance":50}
get_mentionread-only
The full report and thread: versions, stack traces, repro steps.
—
update_mentionasks first
Archives a mention once its issue exists. A destructive hint, so the client asks.
status: "archived"
record_feedbackasks first
When it was not about you after all — teaches FishOut so the next one is filtered.
kind: "not_relevant"

[03] A RUN/ FIXTURE

What comes back

Fixture data.

Claude Code · terminalfishout · mcp

File this week’s public bug reports as issues.

list_mentionsread-onlyarguments

{
  "filter": {
    "labels": [
      "has-a-problem"
    ],
    "platforms": [
      "github",
      "hackernews",
      "reddit"
    ],
    "minRelevance": 50,
    "from": "2026-10-13T00:00:00Z"
  },
  "limit": 30
}

get_mentionread-onlyarguments

{
  "mentionId": "mnt_…"
}

update_mentionasks firstarguments

{
  "mentionId": "mnt_…",
  "status": "archived"
}

orchard-dev/syncissue #772d

Webhook signature fails when the body has a trailing newline

Reply nowHas a problem

r/nodebrambleton3d

Signature verification randomly fails with their SDK

Reply, carefullyHas a problem

Nine reports, three real bugs. Filed #1204 (signature fails on trailing newline — the GitHub issue and the r/node post are the same bug), #1205 and #1206. Four were usage questions; two were about a different product, taught as not relevant. Archive the six filed mentions?

[04] GUARDRAILS/ LIMITS

FishOut does not file issues

It has no access to your tracker. The assistant files them with its own GitHub or Linear connection, which you control.

Ask before archiving

update_mention carries a destructive hint, so a well-behaved client asks first. Keep it that way.

No reporter details in the issue

Link to the public post rather than copying usernames into your tracker.

[05] SCHEDULE IT/ CRON

A prompt runs once

Weekly, or after each release: Codex, OpenClaw or Hermes Agent.

Hermes Agent · cron expression

hermes cron create "0 10 * * 1" \
  "Using FishOut, list mentions from the last {{7}} days labelled has-a-problem on GitHub, Hacker News and Reddit with relevance of at least {{50}}"

Or let FishOut do the scheduled part

FishOut labels problem reports and keeps GitHub issues from repos you do not own next to HN and Reddit. The assistant does the de-duplication and the filing.

[06] NO ASSISTANT/ RULES