Devlog -Vibecodr 1.1.0 (“Source & Cuts”)

Thread body

I’ve been sitting on this update because it’s the kind of release that’s hard to describe without sounding like a changelog robot. But this one deserves a real post. So: I’m calling this push Vibecodr 1.1.0. Not because everything is “done.” Not because it’s “perfect.” But because this release changes how it feels to build here. V1 was: the loop exists — create → publish → play → remix. 1.1.0 is: the loop gets memory. It gets lineage. It gets a workflow that doesn’t fall apart the second you want to iterate like a real builder. The emotional truth of 1.1.0 Up until now, Vibecodr has been… powerful, but kind of feral. You could make something, ship it, remix it, even automate stuff with Pulses — but there was this underlying vibe of: “Cool… but how do I keep this connected to my real work?” “How do I update without fear?” “How do I go back if I break it?” “How do I stop treating publishing like a one-way door?” 1.1.0 is me answering those questions properly. What shipped (in plain, human English) 1) Source is real now (GitHub App–backed) You can link a GitHub repo to a project without handing Vibecodr your personal tokens. Install the Vibecodr GitHub App (user or org) Pick a repo + branch + root folder Sync pulls it into a draft capsule Nothing auto-publishes. Nothing “mysteriously goes live.” This is important because it keeps the trust boundary clean: your repo stays your repo, Vibecodr stays a runtime + studio + publishing layer, and you don’t have to do weird credential gymnastics to connect the two. Behind the scenes, this also meant building the boring but necessary backbone: webhooks (signed), idempotency, push coalescing, safe zipball fetch paths, D1 tables, feature flags — all the stuff you don’t notice until it’s missing and everything breaks. 2) Cuts: version history that doesn’t punish you This is my favorite part of the release because it changes the psychology of shipping. Cuts are Vibecodr’s version history: you can see past versions of a vibe, and you can “revert” without rewriting history. Not “delete and pray.” Not “upload a new thing and lose the old thing.” More like: append-only, git-revert style. And it’s wired into the places you’ll actually use it: Player now has an author-only Versions tab Settings has a Versions page Embeds can be pinned to a specific cut (so sharing can be stable even while you keep iterating) This is one of those features that makes a platform feel less like a toy and more like a home. 3) Pulses got more “normal” (Node.js compatibility) I’ve been slowly pushing Pulses toward “feels like server-side code you already understand” while still keeping the sandbox story intact. 1.1.0 upgrades Pulses with Node.js compatibility support, including: node:http / node:https node:fs as a virtual temp filesystem (not a full disk, not a footgun — but enough to support real patterns) And the docs now spell this out clearly, because the worst thing a platform can do is imply something works and let you discover the edge cases the painful way. 4) More obvious “edit my existing vibe” entry points Small change, big UX impact: From the Player you can go Manage → Open in Studio From Settings → Versions you can jump straight into Studio It sounds trivial, but it reduces the friction of actually iterating. You shouldn’t have to hunt for your own work. 5) Docs got updated where they needed to Not “marketing docs.” Real docs. Pulses Node compatibility (what works, what doesn’t) Source + Versions flows Where to manage versions How to open Studio for an existing vibe The stuff you won’t notice (but you’ll feel) This release also includes a bunch of cleanup that’s basically me trying to make Vibecodr stop tripping over itself. Internal tokens centralized in Secrets Store and bound across workers (less drift, fewer “why is staging different?” problems) Outbound alerting moved behind internal-api with dedupe + sane routing Immutable caching for artifact bundle + manifest paths so runtimes start faster and cold loads hurt less Studio file loading fixes (no more weird “blank file” situations) Path normalization hardened across server/client/shared utilities (less “this worked yesterday but not today” energy) Runtime error events and admin error lookup got unified so debugging isn’t archaeology None of that is sexy. It is, however, the difference between “cool demo” and “I trust this.” Why I’m calling this 1.1.0 Because it’s not just more features — it’s a shift. V1 proved the concept. 1.1.0 makes it sustainable. Source linking means your work can live in the world the way you already work. Cuts means you can ship without fear. Node-ish Pulses means server-side power feels less alien. The backend hardening means I’m not asking people to build on vibes alone. What I want from you (if you’re here reading this) If you’ve been building on Vibecodr quietly… or remixing things but not publishing… or waiting because you don’t want to ship something you can’t update… This release is me saying: you can breathe a little now. Ship the weird thing. Ship the half-finished thing. Ship the thing you think only three people will care about. Because those three people are the entire point. That’s Vibecodr 1.1.0. — Braden