Building on Vibes
Backends, data, the command line and connections to the rest of your tools: posts for people who want to see how their app works and take it further.
18 posts · follow this lane: RSS · Atom · or the whole blog
-
November 11, 2026
Put your app on your own site, or your own computer
Two new ways to run an app you made on Vibes DIY somewhere else. Paste one line into any web page and the app appears there. Or run one command and the app, its data and its backend run on your own laptop or server.
-
October 30, 2026
Make an app for your GitHub repo
A vibe can now connect to a GitHub repo and answer your team's pull requests on it. Describe the bot you want, connect a repo in one click, and its reviews land on GitHub as the pull requests open. Two of our test apps show the range: one turns your copy into pig Latin, one checks your house coding rules line by line.
-
October 24, 2026
Make vibes from Muse
Muse now makes vibes from the chat you already have open. Sign the Vibes DIY command-line tool in once on the machine Muse runs on, and from then on you can ask for a new app, a change to one you have, or a look at its data.
-
October 7, 2026
A quarter of a million towers
The technical sequel to the three.js tutorial: how a library import becomes a pinned URL, why React leaves you no choice but a cleanup, what a frame of a few thousand towers actually costs, and the same city with a quarter of a million towers in one draw call.
-
October 7, 2026
Every city gets an island
Part two of the browser three.js tutorial: give the city a memory. A kept city is four numbers and a handle, one document each — and the shared scene is an archipelago where every document is an island you can sail to, click, and load into your own.
-
September 16, 2026
Borrowing the GPU
The technical sequel to the p5.js tutorial: how a library import becomes a pinned URL, why React leaves you no choice but instance mode, what a frame of 1,400 particles actually costs, and the same flow field pushed onto the GPU with a fragment shader.
-
September 16, 2026
A picture is five numbers
Part two of the browser p5.js tutorial: give the painter a memory. Seed the randomness and a sketch redraws itself from five numbers forever — so saving a piece stores the numbers, not a PNG, and a shared wall of everyone's pieces is a grid of live sketches you can click to load.
-
September 11, 2026
Send your vibe's data anywhere you want
A lawyer's first prompt asked for an intake form whose submissions land in Clio. Now any Vibes app can hand a record to a Zapier Catch Hook, and Zapier carries it into Clio, Slack, Google Sheets or an inbox. One Zap, one saved URL, nothing to build.
-
August 22, 2026
Have your agent talk to my vibe
Instead of handing an AI agent your whole inbox, put one slice of the problem in a vibe and let the agent apply for a seat. You approve it, it works inside the rules your app already enforces, and revoking it is removing a grant.
-
August 21, 2026
Borrowing a WASM synth
The technical sequel to the Strudel tutorial: how runtime imports actually work in a vibe, stress-tested with zaltz — a C-compiled-to-WASM synth running in an AudioWorklet, dynamically loaded from the CDN, with the AGPL lineage story told properly.
-
August 21, 2026
Publish your groove
Part two of the browser drum machine tutorial: give it a memory. One hook turns the step sequencer into a shared groovebook — your saves appear instantly, sync in the background, and publish live to everyone reading this post.
-
August 8, 2026
There is no mailing list
A vibe can tap one person on the shoulder — your move, your request was approved. The obvious follow-up, notify everyone using this app, turns out to be unbuildable as phrased: there's no roster to iterate, because who can see a thing is computed when they ask, not written down. What that constraint gives you instead is better than the API you wanted.
-
July 21, 2026
Where your data lives
Your Vibes app's database isn't a server you call over the network — it's a local replica on the device that answers instantly. Here's the whole path a write takes, in one diagram.
-
July 11, 2026
Add a developer to your vibe
You can now let another account edit and ship one of your vibes — push code, publish, run codegen — without handing over your account. One command, or one row in the sharing panel. You keep the destructive and ownership levers.
-
July 11, 2026
Followers can see it: Vibes grew a social graph
One platform-wide follow graph, and every app can build on it: a one-line audience label makes a doc visible to your followers, resolved live at read time — new followers see history instantly, an unfollow revokes instantly. Follows now ring the bell and land in the weekly digest — and a follow request to your private account reaches your phone.
-
July 11, 2026
Your app is a database you can npm install
A 40-line Node script opens the same live Fireproof database as your deployed vibe — writes flow both ways in real time, with no REST API, no schema migration, and no API keys to manage. The vibe is the always-on peer; your script just drops in.
-
July 5, 2026
Your backend can call the model now — and there's no key to leak
backend.js gets ctx.callAI: one await, text in, text out. No API key exists anywhere in your app — the platform places the call like a switchboard operator, meters it to the user who triggered it, and hands your server code the answer.
-
July 2, 2026
Every vibe just got a backend
One new file — backend.js — runs on our servers for your app: answer webhooks at your own /_api URL, react to every saved document, and run work on a timer. Server writes go through the exact same access rules as user writes, so your permission model stays in one place.