Brief yourself, or your readers, on the week
It is Sunday night and the issue goes out Monday. Or it is Monday morning and your agent is about to touch a library that everyone complained about over the weekend.
Free plan: 10 requests a day, no card.
Top threads across r/LocalLLaMA, r/LLMDevs, Hacker News and this week’s Product Hunt AI launches, with links.
community_pulser/LocalLLaMA, r/LLMDevs, HN, 7 days 12 threadslaunch_pulseAI, Product Hunt, this week 3 launchesget_threadtop 3, comment trees 3 summaries
r/LocalLLaMA Ran the new 30B locally on a MacBook. Numbers inside.
Hacker News Show HN: An MCP server that reads your CI logs
Product Hunt Launch: agent memory layer, 640 upvotes, comments split on pricing.
Read-only. Sources cited. Nothing posted.
An evening of tabs.
- Sunday night. Fifteen tabs of subreddit front pages, Hacker News, and X, trying to remember what mattered on Tuesday.
- Copy links into a doc, write a line about each, realise two are duplicates and one is from last week.
- Ship the issue at midnight with the nagging feeling you missed the thread everyone will mention on Monday.
Three prompts.
- One prompt returns the week’s top threads across the communities you name, grouped by topic, ranked, with permalinks.
- Each thread gets a one-line summary and a note on what the comments argued about, ready to quote.
- A weekly watch delivers the shortlist on Sunday morning. You write the take, not the roundup.
A real session, prompt by prompt.
Each step is one request. The whole session fits inside a Free day.
- 1
Get the shortlist
Twelve is a newsletter. Two hundred is a tab problem. The grouping is what turns a list into sections.
YouTop threads across r/LocalLLaMA, r/LLMDevs, Hacker News and this week’s Product Hunt AI launches, with links.
Comes backTwelve threads grouped into four topics: local model benchmarks, MCP tooling, agent memory, pricing changes. Each with source, score, permalink and a one-line summary.
- 2
Find the argument
Readers subscribe for your take. The take needs the argument, not the headline.
YouFor the MCP tooling threads, what did the comments disagree about?
Comes backTwo camps: stdio versus HTTP transports, and whether servers should be metered per call. The three most upvoted comments on each side, quoted, with permalinks.
- 3
Check what you missed
The fear is missing the thread everyone saw. This is the two-minute check that kills that fear.
YouAnything with over 500 points this week in these communities that is not in the shortlist? Why was it excluded?
Comes backTwo threads. One was a meme, one was a repost of a launch already covered. Both listed with the reason, so you can override.
- 4
Make it recurring
The roundup is now automatic. The hour you spent gathering becomes an hour spent writing.
YouSet a weekly watch for this shortlist, delivered Sunday 8am, as markdown with links.
Comes backA watch on your key. Every Sunday the shortlist arrives by email and as a resource your agent can read, in the format you asked for.
What the numbers mean.
- You ask
- “Top threads across r/LocalLLaMA, r/LLMDevs, Hacker News and this week’s Product Hunt AI launches, with links.”
- You get
- Twelve threads worth your readers’ time, grouped by topic, each with a permalink and a one-line summary. Set a weekly watch and the shortlist arrives in your inbox on Sunday.
Rank by comments, not points
Points measure agreement. Comments measure argument, and argument is what readers want explained. A 300-point thread with 400 comments is a better section than a 2,000-point announcement.
The permalink is the citation
Every item carries its permalink so a quote is one click from its source. Link the thread, quote the comment, name the community. Readers trust a roundup that shows its work.
Cross-source is the story
When the same library is praised on Hacker News and complained about in r/LocalLLaMA the same week, that is your lead. The agent groups by topic across sources so those collisions are visible.
Ask for the shortlist as markdown with links. It pastes straight into your editor.
The tools your agent picks.
You never call these by name. The agent reads the prompt and chooses. Listed so you know what is happening.
community_pulse- What one or more communities talked about over a window: volume, topics, notable threads, and how the comments went.
get_thread- One thread with its comment tree, classified, for the quotes and the disagreement.
search_discussions- Full-text search across every source with filters, for the "did I miss anything" pass.
watches- Saves the query, runs it weekly, delivers by email and as an MCP resource in the format you asked for.
Copy, swap the brackets, paste into your agent.
Top threads across [communities] this week, grouped by topic, with permalinks and a one-line summary each.
For the [topic] threads, what did the comments disagree about? Quote the top comment on each side.
Anything over [N] points this week in these communities that is not in the shortlist? Say why.
Which threads this week mention [library or tool], and is the sentiment up or down on last week?
Give me the shortlist as markdown with links, ready to paste into [Substack, Beehiiv, a standup doc].
Set a weekly watch for this shortlist, delivered Sunday morning.
Honest limits.
- The brief is what the community talked about, cited. It is not your opinion. The take is still yours to write.
- Very large communities produce a lot of noise. Naming three or four communities gives a sharper shortlist than naming twenty.
- Weekly cadence hits the Free cap fast if you also research during the week. Writers usually land on Starter.
Asked before the first request.
How many requests is a weekly issue?
Shortlist, one or two argument checks, one missed-anything pass: three to four requests. A watch delivers the shortlist without spending a request at all.
Can I get it as markdown?
Yes. Ask for markdown with links and it pastes straight into your editor. Ask for JSON if you are feeding it into something else.
Can I quote Reddit comments in a newsletter?
Quote with attribution and a link to the source, as you would any public forum post. Reddibee gives you the permalink for exactly that. It never returns anything about a user beyond what is in the public thread.
Does this work for a team standup instead of a newsletter?
The same shortlist works for "what broke this week" in the tools your team depends on. Name the subreddits for your stack and set the watch for Monday morning.