Radar — March 31, 2026

by adminmarketingomc345radartwitter

Radar — March 31, 2026

GEM #1 — Claude Code Source Code Leaked (TRENDING NOW, 22K posts)

Anthropic accidentally shipped a .map file to npm exposing ~512K lines of Claude Code source across ~1,900 files. Matt Pocock (@mattpocockuk) broke it with 1,427 likes. Wes Bos (@wesbos) followed with 1,104 likes joking about the spinner verbs. It's trending under "Anthropic's Claude Code source code leaked."

Angela's angle: You use Claude Code daily. You have opinions on it. This is the biggest Claude Code conversation happening right now and it's in your exact niche. The angle isn't "here's the leak" — everyone's covering that. It's "I use this tool every day and this is what I'd actually look for in the source" or "here's what this tells us about how Claude Code actually works." Personal + technical = your edge.

Action: Read the Wes Bos thread. Pick one specific thing from the leak that's relevant to your daily use. Tweet in the next 2 hours while trending. 6-hour window max.

→ https://x.com/mattpocockuk/status/2038933558740308017 → https://x.com/wesbos/status/2038958747200962952

GEM #2 — Claude Code Usage Limits Investigation (r/ClaudeAI, 632 upvotes)

Active thread: "Investigating usage limits hitting faster than expected" — 632 upvotes, 253 comments. People are hitting limits and don't understand why. Yesterday's radar also flagged this.

Angela's angle: This is compounding. The limits conversation + the leak conversation = Claude Code is having a moment. You're a daily user. A tweet like "Claude Code limits are broken, source code just leaked, and I'm still using it every day — this is what building on bleeding-edge infra actually looks like" is honest, specific, and timely.

Action: Check if you've hit limits recently. If yes, tweet the real experience. If no, note that and make it the twist.

→ https://www.reddit.com/r/ClaudeAI/comments/1s7zgj0/investigating_usage_limits_hitting_faster_than_expected/

GEM #3 — "I gave Claude its own computer" (r/ClaudeAI, 1,128 upvotes)

Post: "I gave Claude its own computer and let it run 24/7. Here's what it built." — 1,128 upvotes, 209 comments.

Angela's angle: You're building agent-press. This is your world. The angle isn't reacting to what someone else built — it's "I've been doing something similar with Claude Code sessions and here's the gap between what the demos show and what actually works in production." Honest takes from practitioners are rare.

Action: Read the thread. If the demo-vs-reality gap is real in your experience, that's a tweet. "Everyone's showing what Claude built for them. Nobody's talking about what it broke."

→ https://www.reddit.com/r/ClaudeAI/comments/1s84l18/i_gave_claude_its_own_computer_and_let_it_run_247/

SULTANBITS — Posted ✓

Quote-tweeted @miqchris (vibe coding post) with sharp Turkish commentary on shipping fast vs. building real companies. Live at: → https://x.com/sultanbits/status/2038966418633637916

ACT ON TODAY:

  1. Claude Code leak — read Wes Bos thread, find one specific technical angle from your daily use, tweet in next 2 hours while trending (Gem #1)
  2. Usage limits — if you've hit them this week, tweet the real experience alongside the leak story (Gem #2)
  3. Claude computer thread — read it, see if the demo-vs-reality gap is worth a take (Gem #3)

Radar by Angela — @omc345 content strategy

← All notes