I can’t write code. I built my own 08:00 briefing anyway, and now it installs in five minutes
Every morning at 08:00 a message arrives in my Discord. Today’s weather, today’s calendar, and what moved in my Obsidian vault yesterday. I didn’t open a single app to get it. I’m not a developer, and I built the thing that sends it.
It has run every day for more than three months. Today I’m packaging it and selling it: Vibe Coder Kit. One script, five minutes, and the same system runs on your Mac.
Vibe Coder Kit on Gumroad — ₩25,000 early bird (about $18)
Why I built it in the first place
My morning always went the same way. Open the weather app. Open the calendar. Open the vault and try to remember where I’d stopped the night before.
None of that is hard. That’s the problem with it. Every one of those steps happens before I’m properly awake, and none of them needed a human. So I handed the whole sequence to a scheduled script and went back to drinking coffee.
The briefing pulls three things: weather, calendar, and vault activity. Only the third one needed building. The other two already had apps, and I just stopped being the person who opens them.
Three things broke before any of it worked
I set all of this up by hand the first time. Three traps cost me the most, and every one of them is written into the kit’s troubleshooting chapter.
- launchd PATH. The scheduled job registered without a single complaint, and then 08:00 came and nothing arrived. launchd doesn’t run with the PATH my terminal has. The script went looking for Python and found nothing.
- TCC permissions. macOS blocks a background script from reading folders until permission is granted. It’s one click once you know which click it is.
- Discord webhook 404. The URL looked correct and the post came back 404 anyway.
Not one of those is about programming. They’re about the seam where a Mac, a scheduler and a web service meet, and that seam is where I lost my time. install.sh exists because I already lost it.
What’s actually in the kit
- Obsidian vault template — my Plan system, copied straight across, ready to use.
install.sh— Homebrew and Python checks, venv creation, folder placement, launchd registration.- Daily Automation kit — the morning briefing and health-check scripts I run.
- Setup guide PDF, 13 chapters (00–12) — written at “press this button” level.
- Claude Code integration guide — how I write
CLAUDE.md, the memory system, slash commands. - The trial-and-error section — TCC, launchd PATH, webhook 404, and the rest of what I walked into.
Setup is five minutes, and most of it isn’t yours
| The script does this | You do this |
|---|---|
| Checks Homebrew and Python | Click through the TCC permission prompt |
| Creates the venv | Paste a Discord webhook URL (optional) |
| Places the vault and code folders | Open Obsidian once |
| Registers the launchd job for 08:00 | — |
| Runs a dry-run smoke test | — |
The smoke test is the part I care about. It fires the whole chain once, immediately, so you find out on day zero instead of at 08:00 tomorrow.
Price
- Early bird: ₩25,000, first 100 buyers. That’s roughly $18.
- Regular price after that: ₩39,000.
Don’t buy this if
Here’s where I talk you out of it. I’d rather lose the sale than take money for the wrong thing.
- Don’t buy it for Windows or Linux. This is macOS only.
install.shleans on launchd and TCC, which are Mac-specific, and I have no port. I don’t know what a good Windows equivalent looks like, because I never built one. - Don’t buy it expecting Claude Code inside. The briefing automation runs on stock Python and a Discord webhook. No API key, no subscription, nothing metered. Claude Code only enters when you follow the guide chapters to build more automation, and that’s a separate subscription you’d pay for yourself.
- Don’t buy it to learn programming. The guide tells you which button to press. That’s deliberate, and it’s the opposite of a course.
- Don’t buy it if Discord is out of the question for you. The webhook is optional, but the briefing needs somewhere to land, and Discord is where mine lands.
- Don’t buy it hoping the default briefing is the finished product. Mine is the shape of my own mornings. Chapters 00–12 exist so you can bend it into the shape of yours.
What I don’t know yet
I’ve run install.sh on my own machines. How it behaves on a Mac that’s been set up very differently from mine, I don’t know — that’s not a measurement I have, and I won’t pretend otherwise.
I also won’t dress this up as a long-running bestseller. It just came off a round of review by friends, and this post is the first time I’ve said it out loud in public. There are no sales figures here, because there’s barely any sales history to quote.
What I can stand behind is the three months the system has been waking up before I do, and the five minutes it takes to get it running on a second machine. Those two numbers are mine and I’ve lived in both of them.
If install.sh falls over on your Mac, tell me. This first round is exactly the round where I want to hear that.
