StackBlitz Bolt

Connectors run on MCP with eight shipping built in, Notion, Linear, GitHub, Miro, Sentry, Context7, Granola and Jira, authenticated by API key or sign-in, and any tool with a remote MCP server can be added as a custom connector. Each connector's individual actions of read, create, edit and delete can be toggled for granular access control.

Documented first-party integrations span Figma and Google Stitch for design, GitHub for version control with organization access controls, Netlify and built-in Bolt hosting for deployment, Stripe for payments, Supabase and Bolt Database for data, Expo for mobile app store publishing, and Google SSO for authentication, plus a project import path from Lovable.

Sourcebolt.new Connectors announcement and support.bolt.new integrations sectionread 2026-08-31

A documented project lifecycle covers working a project from prompt through to published app, with Code View exposing the generated files for direct editing. Plan Mode separates planning from code generation as an explicit phase. Skills apply reusable rules and workflows during planning or building, and a Prompt Library saves prompts for reuse alongside built-in prompts for common tasks.

Project context can be actively managed to control the context window, chat tools allow selecting UI elements, tagging files and queueing prompts, and backups and version history allow restoring an earlier point. Generation runs across multiple files inside an in-browser Node runtime with package installation and a live dev server.

Sourcesupport.bolt.new project-lifecycle, plan-mode, skills, prompt-library, code-view, chat-tools and manage-context pagesread 2026-08-31

The customer's design system becomes a stored object Bolt builds from. Design systems are documented across six pages covering adding a design system so projects build using the company's UI guidelines and components, viewing and managing the generated system, starting a project so Bolt builds with the customer's real components from the first prompt, keeping the design system in sync when its sources change, and best practices.

The stored design system is a persistent object derived from the customer's material, which can be viewed and managed, rather than context assembled per run. Knowledge is separately a managed object at account, workspace and project scope, with project knowledge set in project settings and shared knowledge held at workspace level. Files and images attach to a project as per-request context, and MCP connectors supply context from external tools and data.

Sourcesupport.bolt.new design system section including the sync page, account, workspace and project settings, upload files and connect-mcp pagesread 2026-08-31

An optional review mode and a set of constraints, with no approval gate in the build path.

Plan Mode is an optional chat mode in which Bolt plans and answers questions without changing code, ending with quick actions such as Implement this plan that switch to Build Mode; the user chooses whether to use it, and Build Mode applies changes directly with no documented approval step.

Connector actions can each be toggled, team admins control member roles, publishing, integrations and data exports, GitHub organization admins control which repositories Bolt can reach, and generation carries security constraints in its system prompts.

Sourcesupport.bolt.new plan-mode and team-settings pages, bolt.new/platform/securityread 2026-09-29

The vendor's security page states Bolt is SOC 2 Type 2 certified and compliant with GDPR and CCPA, with audit reports and policies on a trust profile at trust.bolt.new, AES-256 encryption at rest and TLS 1.2 or higher in transit, continuous scanning and intrusion detection watched by a 24/7 security operations team, and annual independent penetration tests with report summaries on request.

Enterprise and Team customers under an MSA or DPA are excluded from model training. On access, the pricing page lists team-level access management and granular admin controls with user provisioning on Teams, and SSO and audit logs on Enterprise; team settings restrict roles, publishing, integrations and data exports to admins.

Sourcebolt.new/platform/security, bolt.new/pricing and support.bolt.new team-settingsread 2026-09-29

Backups, restore and version history let a project be returned to a previous point, managed from the chat. GitHub integration syncs commits automatically and works across branches, providing an external record of changes. Hosting analytics show engagement with a published project, and database logs are available for the generated app's database. Team settings include data exports. The help center documents no agent-level run trace, tool-call record or organization audit log, and troubleshooting is covered by issue-specific guidance rather than by inspecting a run.

Sourcesupport.bolt.new rollback-backup, git, hosting analytics, database logs, team-settings and llms.txt indexread 2026-08-31

Projects are durable objects with a documented lifecycle covering viewing, organizing and maintaining them over time. Backups, restore and version history allow returning a project to a previous point and are managed from the chat. Project knowledge, design systems and saved prompts persist as project and workspace configuration.

Project context is documented as something to actively manage and keep small for performance. Skills and Prompt Library entries are authored by the customer and are not documented as being updated by the agent. Third-party coverage of the August 2026 agent migration notes that switching agents manually clears chat history.

Sourcesupport.bolt.new projects-files, rollback-backup, manage-context, skills and prompt-library pagesread 2026-08-31

The vendor's security page states that BYOK deployment lets a customer run Bolt inside its own AWS or Azure tenant with full infrastructure isolation and no shared compute, meeting HIPAA, FedRAMP and SOC 2 requirements. Development executes client-side in an isolated WebContainer in the browser. Bolt Cloud hosts published projects at bolt.host or a connected domain, Netlify and Expo are documented alternative targets, GitHub sync exports the full codebase, and the bolt.diy fork runs locally.

Sourcebolt.new/platform/security, support.bolt.new hosting and git pagesread 2026-09-29

The vendor publishes a Templates catalog at bolt.new/resources/templates of working templates filterable by category (websites, apps, portfolio, SaaS, blog, internal tools, editorial, ecommerce, travel, finance, real estate), each named, previewable and opened in Bolt with one click, among them a retail dashboard, a pooled analytics dashboard, a personal finance tracker, a SaaS landing page and dashboard, and a social media posting and analytics platform.

Team templates skip repetitive project setup, the Prompt Library supplies built-in prompts, and skills add reusable rules and workflows. The catalog sits on the product site rather than in the help center.

Sourcebolt.new/resources/templates, support.bolt.new team-templates, prompt-library and skillsread 2026-09-29

Work reaches Bolt through the chatbox in the web application, documented with chat tools for selecting UI elements, tagging files and queueing prompts. Projects can be initiated from a blank prompt, uploaded files, a Figma or Google Stitch design, or a team template, and imported from Lovable, all of which are inputs to a manually initiated build. Collaborators can be invited to work on a project in real time. No scheduled, recurring, webhook or event-driven trigger for starting a build is documented.

Sourcesupport.bolt.new llms.txt index, chat-tools, start-project and collaborate pagesread 2026-08-31

The customer can pick the model in one of Bolt's three agents. In Bolt Forge the customer selects among open-source models from several makers, GLM 5.3 and GLM 5.3 Flash, Kimi K3 and DeepSeek v4 Pro, with new open models added as released; the Standard and Max agents run on proprietary models with model selection handled behind the scenes.

Forge is included with every individual Pro plan and offered through a $9 Lite plan by waitlist, is not available on Teams or Enterprise, and is a research preview running 14 September to 14 October 2026; whether it continues after that is not stated. The open-source bolt.diy fork supports customer API keys across OpenAI, Anthropic, Ollama, Gemini and LMStudio.

Sourcesupport.bolt.new bolt-forge and agents pagesread 2026-09-29

Bolt can be extended around what it produces, but not driven from outside. No API or SDK for driving Bolt itself is documented, and no first-party MCP server exposing Bolt is documented; the API reference section is no longer in the documentation index.

What it does offer is two-way GitHub integration that backs up a project and syncs commits across branches with full codebase export, MCP connectors through which Bolt calls out, and the open-source bolt.diy fork maintained by StackBlitz Labs, which customers can modify and run locally. There is no documented programmatic route into Bolt itself.

Sourcesupport.bolt.new llms.txt, git and connect-mcp pagesread 2026-09-29

A documented project security check finds and fixes security problems in a generated project. A live preview renders the running application during development, backups and restore return a project to an earlier point, and GitHub branch support isolates changes. Dedicated troubleshooting pages cover Bolt issues, preview issues, publish issues, integrations issues and login issues. Token efficiency and context management guidance address build cost and reliability. No test generation, regression suite, scoring or evaluation capability comparing builds is documented.

Sourcesupport.bolt.new security, rollback-backup, troubleshooting section, maximizing-token-efficiency and llms.txt indexread 2026-08-31

Bolt executes builds in StackBlitz WebContainers, a Node runtime with filesystem, package manager and dev server running client-side in the browser tab, which is a code execution environment rather than operation of third-party software lacking a programmatic interface. The live preview renders the application the agent has generated for human inspection. External systems are reached through MCP connectors and documented API integrations, all of which are programmatic interfaces. No browser navigation, form filling, screen control or computer-use capability is documented.

Sourcesupport.bolt.new intro-bolt, preview-issues, connect-mcp pages and llms.txt indexread 2026-08-31