three weeks in: the real numbers

Build in public posts usually show up after the graph goes vertical. This is the other kind. claude-rpc launched on May 20. Here is exactly where it stands three and a half weeks later.

That last line is the whole story.

the loops i built

I did the homework, or what I thought was the homework. The Discord card carries an install button with referral attribution. Every shared card, badge, and Wrapped page links back here. The site has proper OG images, JSON LD, a sitemap. There is a community page with live totals, a leaderboard with GitHub verification, share nudges in the CLI. I even wrote launch posts for every channel, tailored per community, with a posting schedule.

Then I never posted them. I kept finding one more feature that should land first, one more rough edge to sand. The drafts sat in a folder while I shipped a leaderboard, squads, a VS Code extension, and a dashboard nobody outside this domain has seen.

what the data says anyway

Even at this size the referrer table teaches something: every visitor came from GitHub itself, from this site, or from a stray Google query. Growth loops amplify traffic. They do not create it. A flywheel with no first push is furniture.

The stars that did arrive came in a small cluster right after the busiest shipping week, which suggests the obvious: activity is visible, and visible activity converts, even when nobody is promoting it. Four of the seven stars landed within two days of the v0.14 release.

the plan, stated publicly so i actually do it

• Submit to the awesome claude code list.
• Post the Show HN and the r/ClaudeAI thread that have been drafted since June 4.
• Publish the VS Code extension to Open VSX for Cursor and Windsurf users.
• Keep writing these posts, because the numbers only get interesting if you start recording them before they are good.

If you are reading this because one of those finally went out: hi. The install is one command, npx claude-rpc setup, and the source is short on purpose.