← Blog
Product Update· 5 min read

PromptUI Update: Visual Editing and a Broader Integration Catalog

PromptUI now treats visual editing and provider-aware app generation as first-class Builder capabilities, with click-to-select preview editing and 30+ integration contracts.

PromptUI is strongest when the generated app is not a sealed black box. The latest Builder pass moves visual editing and integration awareness closer to the core build loop.

Visual editing now targets the real preview lanes

PromptUI already had a click-to-select inspector in the lightweight preview fallback. The important upgrade is that the same visual edit protocol now targets the active preview engines: WebContainer for React SPA sessions, E2B cloud preview for Next.js and heavier paths, and Sandpack fallback.

Generated UI files also receive stable source markers so a selected rendered element can map back to the relevant file and line more reliably. That makes the edit loop feel more like selecting the product itself instead of hunting through files first.

The integration catalog is broader

Builder now has typed provider context for 30+ integration contracts across payments, auth, databases, email, AI models, AI media, voice, CRM, CMS, search, storage, analytics, and workflow tools.

That coverage includes providers such as Stripe, Supabase, Clerk, OpenAI, Anthropic, Gemini, Firebase, Neon, MongoDB Atlas, Shopify, PayPal, Slack, Notion, HubSpot, Sanity, Algolia, S3/R2, Replicate, fal.ai, and ElevenLabs.

What this means for app generation

When a prompt asks for provider-backed behavior, PromptUI can now carry the right packages, environment variables, safety notes, and server-versus-client guidance into the generation prompt. The goal is not fake marketplace checkboxes; it is better generated code that understands the provider contract before the first file is written.

Still evidence-gated

This is not a claim that every provider has a complete native OAuth dashboard, credential health UI, and live production smoke. Those deeper activation paths remain separate product work. The current improvement is provider-aware Builder generation plus a clearer integrations surface.

Explore the current provider list on PromptUI integrations, or read how the build loop fits together in How PromptUI Builds and Proves Apps Before You Ship.