The buddy list is back, and it says more about the creator economy than the maker intended
If you run social accounts for a living, you already know the feeling of opening a dashboard and finding nothing but numbers. Impressions, reach, engagement rate, watch time — all of it useful, none of it human. That’s why Die With Me, a small Product Hunt launch from maker Weiwei, caught my attention this week. It’s an “AIM buddy list for your AI usage” — a status feed that shows which friends are locked in with Claude Code or Codex, who’s touching grass, and whose AI has clocked out. It is not a social media tool. But the mechanic underneath it — ambient presence, playful status, low-stakes social proof — is exactly the kind of thing creators and social teams keep trying and failing to manufacture with scheduling tools and analytics dashboards. So let’s talk about what this launch actually reveals, and what you can steal from it.
What Die With Me actually is, and what problem it solves
The pitch is deliberately small and nostalgic. As the maker puts it in the launch post, the goal was to bring “a little of that old internet feeling into building with AI — seeing your friends around and having an excuse to say hi.” The product is an AIM-style buddy list where your friends’ AI usage states are visible: who’s actively working, who’s idle, who’s burned through their allowance and “clocked out.” There’s a Product Hunt–specific invite link at diewithme.co/join#invite=phbuilders for anyone who wants to try it.
The problem it solves is not productivity. It’s loneliness and coordination friction in a workflow that has become weirdly solitary. If you’ve spent the last year building with AI coding tools, you know the pattern: you sit alone with a terminal, you hit a rate limit, you wonder if everyone else is hitting the same wall, and there’s no ambient signal telling you. Traditional developer tools don’t solve this. Slack does, badly, because Slack requires you to compose a message. A buddy list requires nothing — presence is the message.
Why this matters to social media operators specifically
Here’s the part I keep coming back to. Social media managers have the opposite problem from solo AI builders: we’re drowning in presence signals. We know exactly who’s online, who posted, who engaged, because the platforms shove that data at us through notifications and inboxes. What we lack is the thing Die With Me accidentally ships — a lightweight, non-performative status layer that doesn’t demand a response.
Think about how you currently coordinate a launch day across a team. Someone posts in Slack, someone else replies with a thumbs up, a third person opens Buffer or Later to check the schedule, a fourth opens Metricool to check cross-platform performance, and by the time everyone’s aligned, the first post has already gone out. A buddy-list model — where “I’m drafting,” “I’m editing,” “I’m done, publishing at 2pm” are visible states rather than messages — would cut that coordination tax dramatically. Nobody has built it well for social teams. Die With Me is a proof of concept for the interaction pattern, even if it’s aimed at a completely different audience.
How it differs from the tools you already use
Let’s be honest about the comparison set. Die With Me is not competing with Hootsuite, Sprout Social, Buffer, or Later. Those are publishing and analytics platforms. It’s not competing with Notion or Linear either, though the “ambient status” idea overlaps with how those tools show teammate activity. The closest analog is actually Discord presence — the little green dot next to a username — or the old AIM away message, which the maker explicitly invokes.
What makes it different from all of those is the framing. Discord presence is generic. Slack status is corporate. Die With Me’s statuses are tied to a specific, emotionally loaded activity — using AI — and rendered in a retro visual language that signals “this is for fun, not for work.” That framing matters because it changes user behavior. When a status is framed as productivity, people perform productivity. When it’s framed as a buddy list, people actually use it.
The “AI clocked out” mechanic is the interesting part
The status states the maker describes — locked in, touching grass, clocked out — map onto a real emotional cycle that anyone who ships content or code with AI recognizes. You have intense focus sessions. You have forced breaks. You have the moment when the tool stops working, either because you hit a rate limit or because the model is degraded, and you have to walk away. Chris Messina, who hunted the launch, joked that he “token-died this week, but fortunately I was not alone” — a reference to the shared experience of running out of AI allowance. That’s the entire product thesis in one sentence: the pain is real, and it’s better when it’s social.
For social media managers, the analogous pain is algorithmic. You post something, it underperforms, and you have no idea if it’s you or the platform. Every operator I know has had the experience of watching a Reel die at 200 views and wondering whether the Instagram algorithm changed overnight or whether the hook was just bad. There’s no buddy list for that. There should be.
What creators and social teams can borrow from this
Even if you never touch Die With Me, there are three operational lessons in this launch that apply directly to social media work.
1. Ambient status beats scheduled check-ins
Most social teams run on scheduled check-ins: a Monday planning call, a Wednesday review, a Friday recap. These meetings exist because nobody knows what anyone else is doing in between. Ambient status replaces the meeting. If your team had a shared, always-visible state — “drafting,” “in review,” “scheduled,” “blocked” — you could kill half your syncs. Tools like Slack can approximate this with custom statuses, but nobody uses them consistently because they’re not tied to the actual work. The lesson from Die With Me is that status has to be automatic and tied to a real signal, not manually set.
2. Nostalgia is a legitimate product surface
The maker leans hard into AIM nostalgia, and the Product Hunt comments reflect that — one commenter notes they “still have” the original iPhone app and calls it a “cool spin.” That’s not incidental. Nostalgia lowers the barrier to adoption because it gives users a mental model they already understand. If you’re building a content series or a community product, ask yourself what familiar interaction you can resurrect rather than invent. The buddy list, the away message, the mixtape, the zine — these are all proven formats with built-in emotional resonance.
3. Small, specific hooks outperform broad utility
“See your friends’ AI usage” is a narrow hook. It doesn’t try to be a productivity suite. It doesn’t try to be a social network. It does one thing, and it does it with a specific tone. For creators, this is a reminder that your content doesn’t need to serve everyone. A Reel about “what to do when you hit your AI rate limit” will outperform a Reel about “AI productivity tips” every time, because the first one is a specific moment and the second is a category.
Why TikTok creators should care more than LinkedIn ones
I’d bet the buddy-list mechanic lands harder with TikTok and YouTube creators than with LinkedIn operators, and here’s why. TikTok and YouTube are presence-driven platforms — the algorithm rewards frequency and recency, and creators who post daily live in a state of constant low-grade awareness of what their peers are doing. A buddy list that shows “who’s posting right now” would be genuinely useful. LinkedIn, by contrast, is a broadcast platform where presence matters less than positioning. The same product idea would feel noisy there. Platform-native context determines whether an ambient status tool helps or annoys.
Where my judgment says it falls short
I want to be balanced here, because the launch is charming and the maker is clearly thoughtful, but there are real open questions.
First, the data source. Commenter Gal Dayan raised the sharpest question in the thread: “Curious how you’re pulling the allowance numbers though, since neither Claude Code nor Codex expose that over a public API as far as I know — polling local usage logs, or something else?” That’s not a nitpick. It’s the entire technical foundation. If the status is derived from local log polling, it’s fragile — it breaks when the tool updates, it requires a local agent, and it can’t work cross-device without sync infrastructure. The maker did not disclose the mechanism in the thread, so I’m flagging this as an open question rather than a flaw. But any operator evaluating this as a pattern should assume the hardest part is the data layer, not the UI.
Second, the privacy surface. A buddy list that shows when you’re using AI is also a buddy list that shows when you’re not. For freelancers and creators, that’s fine. For anyone working inside a company with AI usage policies, it’s a compliance question. The launch post doesn’t address this, and I’d want to see a clear answer before recommending it to a team.
Third, the retention problem. Nostalgia gets you the first session. It doesn’t get you the hundredth. AIM’s buddy list worked because it was the primary communication channel — you were already there. Die With Me is a secondary app you have to remember to open. Unless it integrates into a tool you already live in — a terminal, a browser tab, a Slack sidebar — the buddy list will go stale. This is the same problem every “ambient social” product has faced since Foursquare tried to make check-ins a habit.
Where the math breaks
If you’re a social media manager thinking “I could build this for my team,” run the math first. A buddy-list tool only pays off if the coordination cost it removes exceeds the cost of maintaining it. For a two-person team, that’s unlikely — you already know what your collaborator is doing. For a ten-person team across five platforms and three time zones, the math flips. The break-even is somewhere around four to six people, in my experience, and it depends heavily on whether the status is automatic. Manual status tools die within a month. Automatic ones survive.
What I’d watch / test next
Here’s what I’d actually do this week if this launch resonated with you.
First, go look at the Die With Me launch page and read the comment thread, especially the exchange about how allowance data is pulled. That single question tells you whether the product is a durable utility or a clever demo. Second, audit your own team’s coordination tax. For one week, log every time you ask a teammate “what are you working on?” or “did that post go out?” If the number is higher than five, you have a case for an ambient status layer — and you can prototype it with Slack custom statuses or a shared Notion board before buying anything. Third, steal the framing. Whatever tool you use, rename your statuses to something with personality. “Locked in,” “touching grass,” “clocked out” will get used. “Available,” “Busy,” “In a meeting” won’t. The lesson from this launch isn’t that you need a new app. It’s that the interface between people and their work is still mostly ugly, and the products that win are the ones that make it feel human.
