Edittextandfeatureflagswithoutadeploy

Your agent hardcoded the headline. Also the phone number, the opening hours, and the banner you only meant to run for a week. Now every tiny change means another prompt, another build, another deploy — a full round-trip for a single word.

VibeKit gives your app a Variables tab instead: central values your app reads at runtime. Change one in the admin and it updates in the live app instantly, with no redeploy.

What goes in a variable

Strings, numbers, and booleans — a headline, a phone number, an on/off feature switch. Anything you (or whoever runs the site after you) will want to change after launch belongs here rather than baked into the code. Booleans double as feature flags: turn a section on for a launch and off again when it ends, straight from the admin.

Built for agent-built apps

Each variable has a stable reference your agent reads through the client. So instead of asking your agent to bake the value in, you ask it to read the variable — and from then on, the admin is where that value lives. Your agent can also subscribe to a variable, so a change you make in the admin lands in pages that are already open, not just on the next load.

A tiny CMS and a flag service in one

In practice it works like a tiny CMS plus a feature-flag service — except there's nothing to sign up for or integrate, because it's already wired into your app. Each app keeps its own set of variables, so nothing leaks between projects.

Beyond text and switches

Your logo and colour theme get the same treatment with their own dedicated home — see instant branding. And when the thing that changes is the data itself rather than your copy, live data pushes record updates onto the page the same way: no refresh, no redeploy.