What's New
What's new in VibeSharing. We ship fast and often.
Feedback-driven deploys, share page redirect, and interaction analytics
Deploys now prompt for feedback focus — set what stakeholders should review, what to ignore, and guided questions. The deploy becomes a deliberate “ready for eyes” moment.
Direct prototype URLs now redirect to the VibeSharing share page, so stakeholders always land on the full feedback experience with guided questions and context.
Interaction analytics — tracking exports, downloads, shares, source views, and feedback panel opens to understand how teams actually use prototypes.
Dashboard improvements — Focused layout is default, two-column collections + prototypes view, sorted by most recent activity.
Feedback-driven deploys
- -Post-deploy MCP response prompts for feedback focus: awareness, design, feasibility, interaction, or full review
- -New scope_note parameter — tell stakeholders what NOT to focus on (e.g., “ignore visual polish”)
- -Scope notes display as amber disclaimer banner above guided questions on the share page
- -Auto-generated share slugs on every deploy — every prototype gets a /s/[slug] share link
- -Backfilled share slugs for all 144 existing deployed prototypes
Share page & feedback
- -SDK redirects direct prototype visits to the share page for the full feedback experience
- -New comment alerts exclude your own comments — no more self-notifications
- -Last-viewed tracking — visiting a prototype clears the “new comment” badge
- -Unpin collections directly from the Focused dashboard view
Dashboard
- -Focused layout is now the default — Classic toggle hidden for one-week test
- -Two-column layout: pinned collections on the left, watching prototypes on the right
- -Collections and prototypes sorted by most recently updated
- -Removed collapse arrows and status dots from watching list for cleaner UI
- -Nav bar contrast fixed over bright thumbnails (bg-black/80)
- -Active/press states on all buttons and nav links
Analytics
- -Lightweight event tracking for 8 key interactions: export, download, share, feedback, source view
- -Netlify credit monitoring in the diagnose tool — shows remaining credits and warns when low
Deploy reliability
- -Deploy status API is now provider-aware — checks Netlify or Vercel based on project setting
- -No more phantom “No Vercel project associated” errors for Netlify-migrated prototypes
- -Auto-disconnect Vercel projects when deploying to Netlify — prevents ghost builds
- -Static HTML projects deploy correctly on Netlify — no build command, publish from root
- -Auto-inject netlify.toml with correct config based on framework detection (Next.js plugin, Vite SPA, static)
Multi-provider hosting — deploy prototypes to Vercel, Netlify, or bring your own
Prototypes are no longer locked to Vercel. Organizations can now choose their hosting provider — starting with Netlify, with AWS Amplify and Fargate coming soon.
Provider abstraction layer — a single HostingProvider interface powers project creation, deploy triggering, build polling, and URL resolution across all providers.
Netlify eliminates the Vite framework mismatch bug that required manual intervention on every new Vercel branch deploy for component library prototypes.
Infrastructure settings updated — org admins can switch to Netlify and configure tokens from Dashboard > Settings > Infrastructure.
Multi-provider architecture
- -New HostingProvider interface with pluggable Vercel and Netlify implementations
- -Both deploy-code (MCP/CLI) and import-repo (GitHub import) routes use the provider abstraction
- -Each project records its deploy provider — status checks and re-imports resolve to the correct platform
- -Provider-specific SPA routing files auto-added (vercel.json or netlify.toml) based on org setting
- -Default is still Vercel — no change for existing orgs unless they opt in
Netlify provider
- -Full lifecycle support: site creation, GitHub repo linking, build triggering, status polling, URL resolution
- -Tested with Vite + React + MUI v7 prototypes — builds in under 10 seconds
- -Private .tgz dependencies resolve correctly from Netlify’s build environment
- -No framework auto-detection override — reads netlify.toml directly, eliminating the Vercel mismatch bug
- -Sites are publicly accessible by default (no SSO protection to disable)
MCP tools
- -All tool descriptions and user-facing messages are now provider-agnostic
- -Deploy name suggestions no longer hardcode .vercel.app URLs
- -Validation messages reference "the build" instead of "Vercel"
Infrastructure
- -Netlify button added to provider selector in infrastructure settings
- -Netlify Personal Access Token configuration with masked display
- -Database migration: netlify added to deploy_provider enum, netlify_token on orgs, netlify_site_id/name on projects
Enterprise infrastructure, import reliability, and UI polish
Infrastructure admin role and settings UI — configure GitHub orgs, deploy providers (Vercel, Fargate, Amplify), and custom prototype domains per org.
Pre-deploy validation — catches duplicate config files, conflicting output settings, missing frameworks, committed build artifacts, and case-sensitive path mismatches before they hit Vercel.
Collection thumbnails — live preview of prototypes on collection cards, with list/card view toggle and pin-to-thumbnail from the prototype menu.
Deploy status tool — check live Vercel build state from MCP without running diagnose repeatedly. Returns build output on errors.
Enterprise readiness
- -New infra_admin role — configure deploy infrastructure without full admin access
- -Infrastructure settings UI — GitHub org, service tokens, deploy provider, AWS config, custom domains
- -GitHub API URL, org, and Vercel API URL all configurable via env vars for behind-firewall deployment
- -22 files refactored — zero hardcoded external URLs in API routes
- -Role hierarchy enforced — only infra_admin can assign/modify infra_admin role
Import reliability
- -Binary files (PNG, JPG, fonts) now included in repo imports — previously silently skipped
- -New entry_point parameter — specify landing page for static HTML sites with no index.html
- -Batch file fetching — 10 concurrent requests with rate limit pauses (was sequential, hit GitHub limits on 100+ file repos)
- -Build output directories (out/, dist/, build/) filtered from imports
- -Orphaned repo reuse — re-imports succeed when GitHub repo exists but prototype was deleted
- -Retry resilience — partial failures (repo created, Vercel failed) recover on retry
- -Default branch detection — tries main, master, then GitHub API for actual default
- -deploy_files guardrail — 100KB+ payloads redirect to import_repo with clear message
- -Tool descriptions steer AI toward import_repo for existing repos
MCP tools
- -deploy_status — live Vercel build state with build output on errors
- -deploy_prototype now accepts collection_id and parent_project_id for upfront placement
- -import_repo branch parameter added to remote MCP server
- -import_repo entry_point parameter for static HTML landing pages
Dashboard
- -Follow → Watch rename throughout the UI (GitHub mental model)
- -Action bar collapsed into Share / Watch / ••• overflow menu
- -Collection thumbnail previews with list/card view toggle
- -Set as collection thumbnail option in prototype overflow menu
- -Paste Code auto-detects HTML and routes to static deploy (no Next.js wrapping)
- -Project edit routed through admin API — owner reassignment now works
- -infra_admin shown in Admins panel, not Members
Validation & safety
- -Pre-deploy config conflict detection (duplicate next.config files, output:export conflicts)
- -Case-sensitivity warnings for file path mismatches (macOS vs Linux)
- -Branch protection on new repos — blocks force-pushes and branch deletion
- -Fixed ambiguous PostgREST joins caused by thumbnail_prototype_id FK (broke update_prototype and delete_prototype)
Bug fixes
- -Fixed display_name column typo (was querying non-existent full_name)
- -Fixed import-repo retry after partial failure (orphaned GitHub repos)
- -Fixed dashboard crash from server/client render-prop mismatch
- -Fixed Edit button in overflow menu (menu closing before modal opened)
- -Post-push QA hook runs test suite automatically and notifies on failure
Designer role, Claude Code skills, and template QA
New 'designer' role — give your design team template access without full admin rights. Invite, assign, and manage from org settings.
/prototype — scaffold and deploy a prototype from a design system template in one command. Pick a template, describe what you want, get a live URL.
/theme — generate a complete design system template from a Figma URL, screenshot, or text description. All 38 CSS variables, plus AI design instructions.
/diagnose — triage broken deploys, blank pages, and permission errors with a structured diagnostic walkthrough.
Roles & permissions
- -New 'designer' org role — can create, edit, and delete design system templates
- -Designers see the Settings gear in nav, auto-redirect to Templates page
- -Role available in invite form, join codes, and role change dropdown
- -Teal badge color to distinguish from editor (purple) and admin (blue)
- -RLS policy updated — designers can manage templates via Supabase row-level security
MCP tools
- -list_templates — browse your org's design system templates with variable counts and instruction status
- -quick_prototype — describe what you want, pick a template, and get a deployed prototype. One tool call from idea to live URL
- -Templates API now supports deploy token auth — MCP tools can list templates without browser session
Claude Code skills (repo maintainers)
- -/prototype — pick a template, describe intent, get a deployed prototype in one step
- -/theme — generate templates from Figma URLs, screenshots, or descriptions with full variable coverage
- -/qa-template — validate template completeness (38 vars), WCAG contrast ratios, format correctness, and design instructions
- -/diagnose — systematic triage for deploy failures, blank pages, template issues, and permission errors
Design system templates, version control, and fork workflows
Design system templates — deploy prototypes pre-themed with your org's design system. Light, dark, and product-focused variants available.
Full version control — every deploy is tracked with version numbers, file manifests, and git metadata. Browse history with list_versions.
Fork prototypes — create a copy with its own URL to experiment freely. The original stays untouched. Built for safe iteration.
Rollback to any version — one command to restore a previous deploy. Works for both git-based and static prototypes.
MCP tools
- -fork_prototype — clone a prototype into a new one linked to the original
- -list_versions — browse deploy history with file manifests and commit info
- -rollback_deploy — restore a previous version by re-pushing its files
- -delete_prototype — remove prototypes via MCP (creator or admin only)
- -update_prototype — rename, update descriptions, and fix URLs without creating duplicates
- -template parameter on deploy_prototype and deploy_files — apply a design system template at deploy time
Design system templates
- -Admin template management UI — create, edit, toggle, and delete templates from Settings without code changes
- -Database-driven templates with CSS variable editor and color preview
- -Templates include light, dark, and product-focused theme variants
- -Each template gets a slug for use with the template parameter on deploy tools
- -Org-scoped — each organization manages their own design system templates
- -deploy_prototype now supports multi-file deploys (files, file_paths) — no more jamming everything into one file
Deploy pipeline
- -deploy_prototype now creates a Git repo (previously used Vercel direct with no source history)
- -Every MCP deploy gets version history, forkability, and push-to-deploy
- -Empty files are stripped before push to prevent broken Vercel builds
- -Vercel project IDs now reliably stored via admin client (fixes 'no Vercel project associated' errors)
Dashboard
- -Cleaner prototype detail page — Share and Follow moved to top action bar, description width constrained
- -Trash button now offers deprioritize (soft archive) or delete permanently
- -Removed redundant Prototype and Live badges
- -Mobile-friendly navigation with hamburger menu
- -Edit Project form no longer blocks saves due to URL validation
Onboarding & accounts
- -Auto-join by email domain now works for new signups (was blocked by RLS)
- -Onboarding email rewritten for both builders and stakeholders
- -GitHub team invite mentioned in welcome email so users know to look for it
- -All emails now have reply-to set to info@vibesharing.app
- -share_html auto-registers a visible prototype in the dashboard hierarchy
Admin & analytics
- -Org analytics dashboard — members, deploys, feedback, MCP usage, and activity charts scoped to your org
- -Template management UI — create and edit design system templates from Settings
- -@mention autocomplete in feedback — type @ to tag org members and notify them
Deploy reliability overhaul, feedback loops, and MCP registry
Major deploy reliability overhaul — fixed 10+ bugs across 6 deploy paths. Shared deploy-post module ensures consistency.
Published to the official MCP registry. One-click install in Cursor. Auto-update checks on startup.
Closed-loop feedback — stakeholders get notified when their feedback is addressed. 'See what changed' flow.
Full-text search across prototypes, projects, and collections. Source viewer for code review in the browser.
Deploy reliability
- -Shared deploy-post module — all 6 routes (code paste, ZIP, GitHub import, deploy-code, static, import-repo) call the same post-deploy logic
- -Deploy lock rewritten (read-then-write instead of broken .or() filter)
- -maxDuration=120 on all deploy routes to prevent Vercel function timeouts
- -Deploy token auth added to all routes
- -Auto-redirect for ZIPs missing index.html
MCP tools
- -diagnose — comprehensive health check with auto-fix for stuck deploy locks
- -send_support_request — email admin directly from MCP with session context
- -close_feedback_loop — deploy + auto-resolve feedback items in one step
- -generate_feedback_topics — auto-generate guided questions after deploy
- -share_html with auto-bundling — inline CSS, SVGs, and images from local files
- -Unread feedback surfaced on first tool call of each session
Platform
- -Full-text search across prototypes, projects, and collections
- -Source code viewer with syntax highlighting
- -Export as ticket (Linear, Jira, GitHub Issue)
- -Context tab with CLAUDE.md content and related resource links
- -Onboarding email for new org members
- -Engineering review feedback with accuracy ratings
- -Documentation hub at /docs with MCP tools reference
Feedback experience, collections, and named deployments
Feedback triage — filter by status, priority, and assignee. Bulk update from MCP. Resolution notes.
Feedback briefs — set context that stakeholders see before commenting. Auto-extracted from CLAUDE.md.
Features
- -Feedback triage with status (open/in_progress/resolved/wont_fix/deferred), priority, and assignee
- -Feedback briefs — ## Feedback Brief in CLAUDE.md auto-populates stakeholder context
- -Auto-generated feedback questions categorized by theme (vision, feasibility, design, interaction)
- -Named deployments — set friendly Vercel URLs (e.g., my-prototype.vercel.app)
- -resolve_target tool for fuzzy name matching
- -Collections with nested folder support
- -Fuzzy search on list_collections and list_prototypes
MCP server launch, Claude Code integration, and push-to-deploy
MCP server for Claude Code and Cursor — deploy prototypes, register projects, and manage feedback without leaving your editor.
Push-to-deploy via GitHub — push to main and your prototype auto-deploys to Vercel within 30 seconds.
Features
- -MCP server published to npm as @vibesharingapp/mcp-server
- -register_prototype, deploy_prototype, deploy_files, list_prototypes, list_collections tools
- -get_feedback, sync_context, verify_token tools
- -GitHub service account creates repos in vibesharing-prototypes org
- -Vercel project auto-creation linked to GitHub repos
- -Deploy tokens (vs_*) for CLI and API authentication
- -Claude Code marketing page at /claude-code
- -Auto-sync CLAUDE.md as context entry on deploy
Collaboration, sharing, and the feedback widget
Email invites with pending invite flow — invite teammates by email, they land directly in your org after signup.
Prototype sharing with @mentions — select org members, send share notifications, auto-invite to VibeSharing.
Sharing & collaboration
- -Share modal with org member picklist and batch sharing
- -Email notifications for prototype shares (via Resend)
- -Feedback widget embedded in every deployed prototype
- -Always-on feedback input with optional guided questions
- -Owner vs. reviewer feedback views
- -Follower system with notifications on deploy
Dashboard
- -Activity stream on dashboard sidebar
- -Live iframe preview for VibeSharing-hosted prototypes
- -Drag and drop to move projects between folders
- -Organization logo upload
- -Full-path breadcrumbs in project cards
Org management
- -Email invite flow with pending invites and invite links
- -Multi-org support with org switcher
- -Role-based access (admin, editor, member)
- -Onboarding stepper for new signups
- -Auto-join by email domain
Prototype detail page, handoff, and deployment pipeline
Redesigned prototype detail page — live preview iframe, right-side action rail, and feedback panel below.
Git-based handoff — source code stored, ZIP export, and clone instructions for developers picking up work.
Prototype hosting
- -ZIP upload deployment to Vercel
- -GitHub import — deploy from any public repo URL (supports subdirectories)
- -Code paste deployment — single page.tsx wrapped in Next.js template
- -Static HTML deployment served from Supabase storage
- -Source code storage with auto-delete and delete-on-download options
Page redesign
- -Prototype detail page with live scaled iframe preview
- -Right-side action rail: collaborate, update, export
- -Feedback section below preview with guided questions
- -Browser frame component with URL bar and refresh button
Project hierarchy
- -Project to Prototype parent-child hierarchy
- -Nested folder structure with org-level visibility
- -Collection creation for organizing prototypes
- -External URL support for prototypes hosted elsewhere
VibeSharing launches
Foundation
- -Next.js 14 + Supabase + Tailwind stack
- -Supabase Auth with email/password
- -Organization and folder-based multi-tenancy with row-level security
- -Dashboard with project listing and creation
- -Dark mode UI
- -Vercel deployment for the platform itself
VibeSharing ships continuously. Follow along as we build.