Save & Deploy

Two states for any blueprint: draft (what you're editing) and deployed (what's running). Saving updates the draft. Deploying ships it.

Saving

⌘S, or click Save. Creates a new version. Does nothing to the live runtime. Save as often as you want.

Deploying

Click Deploy. The wizard validates the draft, packages it, and ships it. In-flight conversations finish on the old version. New conversations land on the new one. Existing customers don't see any blip.

What gets validated before deploy

• Every node has its required config
• Skills referenced in nodes are still connected
• No disconnected branches
• No infinite loops without exits

If anything fails, the deploy is blocked and the offending nodes get highlighted. Fix, redeploy.

Rolling back

Open the bot's History tab. Click Restore on any past version. The runtime redeploys to that snapshot, same way as a forward deploy.

What ships atomically

A deploy is one atomic unit. It contains the blueprint (nodes plus connections), skill configuration, runtime config (image, env, limits), and channel bindings. If any part fails to apply, the whole deploy rolls back to the previous good version.