5-minute runtime mutation · Developer Preview

Getting Started with Xpell 2

Install the starter, connect your AI provider, open Xpell Vibe Studio, and make your first runtime mutation while the app is running.

Start with the starter repo Watch setup video

Install starter -> configure AI key -> run app -> open Xpell Vibe Studio -> prompt mutation -> preview/apply -> save view.

Watch the setup walkthrough

A short beta demo shows the runtime mutation workflow used throughout Xpell 2 Developer Preview.

This short beta demo shows the runtime mutation workflow used throughout Xpell 2 Developer Preview.

Install the starter

Start from the Developer Preview starter instead of installing low-level packages manually.

Step 1 — Clone the starter

git clone https://github.com/xpell-ai/xpell-vibe-starter
cd xpell-vibe-starter
pnpm install

Step 2 — Configure AI keys

cp .env.example .env

Add the AI provider key required by your local starter configuration.

Step 3 — Run the app

pnpm dev

Keep the app running. Xpell edits the running application through the runtime workflow.

Open Xpell Vibe Studio

Xpell Vibe Studio is the runtime editor for Xpell 2. Use it to describe changes, inspect runtime artifacts, edit view JSON, and save accepted mutations.

Prompt Preview mutation Apply Save View

Make your first runtime mutation

Use a small app request so you can focus on the runtime loop first.

First prompt

Create a todo app with priorities and a small statistics panel.

The goal is not to regenerate a full project. The goal is to update the runtime artifacts the application is already interpreting.

TypeType the prompt in Xpell Vibe Studio.
GoClick Go.
ReviewReview the generated mutation.
ApplyApply the change.
SaveSave the view.

What changes when you save?

Xpell saves accepted runtime artifacts, such as views, flows, entities, and generated modules. These artifacts are interpreted by the runtime instead of requiring a full source-code regeneration loop.

Generated modules

Some prompts require behavior, not only UI. In those cases Xpell may generate a module that can be inspected, edited, disabled, deleted, or regenerated.

Developer Preview note

Generated modules are available in the Developer Preview, but module repair and advanced runtime-aware planning are still experimental.

Troubleshooting

Use the starter logs and Xpell Vibe Studio runtime state as the first places to inspect local setup issues.

AI key missing

Check your local .env file and restart the dev server.

App did not update

Refresh runtime state from Xpell Vibe Studio, then retry the prompt.

Save View did not persist

Confirm the starter app is running with file-write permissions and check the dev server logs.

Generated module failed

Open the generated module source, inspect the error, and retry with a smaller prompt.

Next steps

After the starter workflow is running locally, use the examples and source links for deeper inspection.