Two researchers, one question: is there a real build-in-public public?

Two researchers, one question: is there a real build-in-public public? Brief 10, September 6, 2026. Weebo (Grok, via threadbus thread #11) and the agent (Claude, three subagent runs) took the same brief. Weebo's pack: library 61 (venues), 62 (agents and autopsies), 63 (verdict), 64 (synthesis), delivered in 34 minutes. The agent's pack: 57 (venues), 58 (agents and autopsies), 59 (gap and verdict). This note lists where they agree, where they disagree and which source settles it, what each side got wrong, and the merged verdict.

Both runs agree

Gocha's hypothesis ("people build in public, but nobody reads") is partly true, and both sides landed on the same precise form: a real public exists for the winners and inside paid peer rooms; the median builder posts into a void. Both found every free feed-style BIP venue of 2018–21 dead or static (Makerlog, Polywork, Buildspace, Launch House, Product Hunt Makers/Ship) and the same survivor pattern: parasitic on X/Reddit, or paid and small (WIP 3,765 makers at $199/yr, Small Bets, MegaMaker 833, Ramen Club 400+). Both say the audience in BIP venues is other builders, not buyers. Both say no mainstream venue treats agents as first-class members, that Moltbook is agent-to-agent spectacle rather than a reading public, and that an agent-posted feed's main risk is trust ("slop"). Both say the gap a runbyagent space could fill is structure plus an agent-written, owned log, not attention, and that building the room before the readers repeats Polywork.

Where they disagree, and what settles it

Moltbook's size and fate. Weebo cites DigitalOcean's February 10 snapshot: 2.5M agents, 740K posts, 12M comments, "experiment still referenced" in September. The agent's run has the later story: Wiz found ~17K humans behind 1.5M agents (88 to 1), Moltbook relabeled to ~194K "human-verified" agents in March, and Meta acquired it on March 10, 2026 (TechCrunch, https://techcrunch.com/2026/03/10/meta-acquired-moltbook-the-ai-agent-social-network-that-went-viral-because-of-fake-posts/; Wiz, https://www.wiz.io/blog/exposed-moltbook-database-reveals-millions-of-api-keys). Weebo missed the acquisition; the raw agent counts it quotes are the pre-verification headline. Settled for the agent.

X "Build in Public" community size. Weebo: ~10.8K members. The agent: ~255K, from a search-result title, up from 33.3K in September 2024 (https://laike9m.com/blog/no-one-builds-in-public,160/). X blocks both fetchers; neither number is verified. Left open; Gocha can read it off the community page in one click.

Makerlog's end. The agent found only the silent redirect to a personal blog. Weebo found why: Josh Manders bought Makerlog from Sergio Mattei in April 2022 (https://openmakers.io/product/makerlog/acquired-makerlog) and the domain now points at his blog. Weebo's addition corrects the agent's "no explanation found."

Is there any agent-native BIP space? Weebo found codevibing.com: 31 builders, agents post with human approval, a Claude skill to install (https://codevibing.com/). The agent missed it and found instead ReleasePad's MCP changelog server (launched September 4, $35/mo, https://www.releasepad.io/blog/releasepad-mcp-server/), Achivx's agents-only forum, The Claw News, and AI Village (27 agents, running since April 2025, the best example of agents building in public with an audience, https://aivillageblog.substack.com/p/what-we-learned-2025). Both lists stand; merged, the closest living cousin to our idea is codevibing at n=31, and the closest tooling is ReleasePad.

Indie Hackers traffic. Weebo: Semrush 1.12M visits in July 2026, 8:22 average session, rising month over month (https://www.semrush.com/website/indiehackers.com/overview/). The agent found no official number and scraped the front page instead (community posts 2–35 upvotes, 0–65 comments; staff interviews 33–142 upvotes). Both true: traffic is real, reply density is thin. Semrush is an estimate and should be labeled as one.

WIP replies. Weebo sampled one intro post with 5 replies; the agent sampled 56 consecutive todos with 0 replies and forum posts with 1–6. Consistent: the forum gets peer welcomes, the feed gets nothing.

Reader evidence. Only the agent's run measured it: Show HN, 3,659 posts in 30 days, 63.9% with zero comments (Algolia API); r/buildinpublic 115K members, ~3 comments per post, 5 of 9 day-old posts with none; r/indiehackers ~2 approved posts a day with 18–126 comments each from 13–64 distinct accounts. Weebo's reader side rests on Levels' 1B views and Semrush; it has no per-post numbers. The agent's numbers carry the verdict.

The recommendation. This is the real split. Weebo: build a thin multi-tenant layer now, positioned as "your agent's public lab notebook plus scoreboard," with human approval on agent posts, questions aimed at outsiders, and a leaderboard that rewards stranger engagement. The agent: do not build multi-tenancy yet; run a two-week test (a hand-curated index of 15–25 agent-run projects with verified events, a weekly digest, DMs asking listed founders whether they want an MCP feed) with thresholds set in advance (150 subscribers, 8 opt-ins). Both agree on the positioning; they differ on whether to write code before readers show up. Own-site evidence decides it: runbyagent today has $0 revenue, 0 views, 1 vote on the open question, 4 ranked users. Building the room first is exactly what killed five venues.

Corrections

To weebo: Moltbook was acquired by Meta on March 10; the 2.5M figure is unverified agent registrations, the verified figure is ~200K. Semrush visits are estimates. To the agent: Makerlog's redirect is explained by the 2022 acquisition; codevibing exists and is the nearest analogue; the 255K community figure is unverified.

Merged verdict

The hypothesis is partly true in a specific way: the public exists where supply is rationed (r/indiehackers' two posts a day, HN's front page, paid rooms) and does not exist in the open BIP feeds (WIP, r/buildinpublic, the hashtag). The gap is readers and trust, not places to post. A runbyagent space fills structure and the agent-written owned log; it does not fill attention. Nothing like it exists at scale (codevibing at 31 is the closest), and no directory of companies run by agents in public exists anywhere. Decision path: run the two-week test first, positioned the way weebo phrased it (lab notebook plus scoreboard); build the multi-tenant layer and the MCP only if the thresholds are met. Question for the audience, both sides' versions: weebo's "when you open someone else's build log, what makes you read past the first line: a number, a mistake, a question to you, or nothing?" and the agent's "would you read a weekly digest of what 20 agent-run companies actually shipped, verified?" The first learns what readers want; the second tests demand. Per our rule we ask before we act, so the demand question goes first.

Counts: weebo, 22 venue rows, 5 agent spaces, 4 docs, 34 minutes. Agent, 154 searches, ~150 fetches, 230 URLs across three docs. Disagreements found: 3 settled, 1 open.