Apps I’ve Vibe-Coded Lately That Are Pretty Damn Useful To Me, Actually CodePen co-founder Chris Coyier detailed two vibe-coded internal tools built with AI agents: a Cloudflare Workers CRON job that pulls direct engagement from Bluesky, Mastodon, X, LinkedIn, Instagram, Facebook, TikTok, YouTube and Threads into a Slack channel, and a "One Report to Rule Them All" dashboard that snapshots JSON data from services including Cloudflare, Stripe, Postmark, Front, Sentry and Notion and has an LLM flag anomalies. Coyier said the social-engagement tool took weeks because each platform's API required manual provisioning — X's API is paid, LinkedIn app approval took roughly two weeks, and Meta's permissions were "easily the most awkward" — while TikTok lacks an API for replies. The write-up argues the economics of small side projects have shifted, since tasks that were too annoying to hand-code are now straightforward LLM work. I’m sure you’re all very impressed that I can type out what I want to an AI agent and it’ll do work for me. Amazing stuff, right? Well, I’m not here to show off my prompting skills, as much as I know y’all could use it. I think what’s valuable is seeing what other people are building that’s actually useful. I’m not talking about the main thing. Your primary project. The big dog. That, you need to have dialed. That’s where your real engineering and design muscle is going. You know, the one where you deeply care about the code, sweat the details, do the research, and wake up thinking about. I’m talking about little stuff. Stuff that would be nice, but you just never found the time to actually do. Stuff that might have value, but working on the big dog is just so much more worthy of your time. Or stuff that would just be annoying to code in the past and you couldn’t prioritize. Now the math on what is worth coding has changed, so talking about what makes the cut now is more interesting. CodePen has social accounts across Bluesky, Mastodon, X, LinkedIn, Instagram, Facebook, TikTok, YouTube, and Threads. That’s a lot to try and stay on top of. Definitely too much to expect every team member to do. My goal was to build a cloud function on a CRON that would gather any direct engagement on these platforms and send the messages/links to a Slack channel so our whole team could see it and respond personally. Every one of them, except for TikTok, has APIs available to access stuff like replies. But each one is different. This is the kind of thing that would be obnoxious to code by hand, but is straightforward work for an LLM. This ended up taking me weeks of poking at it to get done, because each one required some human work in the form of provisioning API keys and, in some cases, waiting for approval of “apps”. Every app is a little different. - X requires you to put a few bucks in an account because their API is paid. - LinkedIn required app approval, which took ~2 weeks. - YouTube is weird because you have to check a big swath of recent videos and just look for comments you haven’t seen before. - Getting the right permissions and keys on all the Meta apps was easily the most awkward. In the end, I’m really happy with how it all works. It uses Cloudflare Workers because: - It’s easily executable code, great for this purpose - We already use them for a bunch of other stuff - It needs to remember stuff between runs, and it can use a K:V store for that - There are a bunch of API keys involved that need to be kept secure, and Cloudflare has a Secrets Store just for that - They can run on a CRON We have tons of data available to us at CodePen, from our own database to a variety of third-party services we use e.g. Cloudflare, Stripe, Postmark, Front, Sentry, Notion, etc . We’ve also built all sorts of reporting tools for us over the years. We get an idea to track a certain metric, and we do it. Honestly, a lot of the reporting is spread out. We can log into Cloudflare, Stripe, or Postmark and look at their reporting tools and dashboards. They all do a decent job, but that’s disseminated. We’ve got our own admin site where we’ve built a bunch of bespoke reporting dashboards. We use redash https://redash.io/ for building out database-powered dashboards. I wouldn’t call it a mess since there is a rhyme to the reason, but it does mean all this data doesn’t always get looked at with equal regularity. So I built One Report to Rule Them All. It works like this: 1. Programmatically, it looks at everything, and it saves JSON data snapshots. 2. Then it has an LLM look at the snapshot and previous snapshots , purposefully looking for data anomalies and interesting standout bits of data. 3. It produces general insight that it attaches to the data snapshot where relevant. 4. Then the JSON data is templated into a very fancy website that produces a scrolling dashboard of charts, insights, raw data, etc. 5. The website becomes a Pen, naturally, via our API https://blog.codepen.io/docs/api/api-v2/ . My goal, of course, is to automate this completely. Like our social media checker, it should generate the report, produce the Pen, and send it to our general channel in Slack for us all to see. I’m like 90% there, but like everything, there are some harder human parts left I haven’t prioritized yet. I only mention that out of solidarity — I’m just sure y’all have projects in this so close state. I think keeping the entire team seeing these important numbers across everything we’ve already decided we care about is pretty darn good. We’ve got a whole fancy system for sending HTML email at CodePen that we’ve built ourselves and honed over the years. It even includes a nuclear submarine-style two-approval system for sending emails, ensuring human accountability for the quality of what goes out. But a little automated help is nice too I wired up a little that… 1. For any given HTML email, finds all the