REPLACEMENT BRIEF

dev tools

Can AI replace Bolt.new?

EDITORIAL ANSWERNOT REALLYCurated prompt

Generate and edit a small web project in a local sandbox from structured prompts, index the repository, propose patches, run approved commands, and preserve an auditable session log.

See the closest workaround →

AT A GLANCE

price
$20/mo
listed annual price
$240/yr
replaceable scope
single-repository coding assistant
build time
closest consolation build: one sitting

what AI can build

Generate and edit a small web project in a local sandbox from structured prompts, index the repository, propose patches, run approved commands, and preserve an auditable session log.

A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Bolt.new, generate and edit a small web project in a local sandbox from structured prompts. The hard boundary is browser sandbox, model orchestration, package execution, deployment, and hosted compute, plus frontier models, context infrastructure, and execution safety.

The prompt was editor-reviewed; no completed build is recorded.

The honest tradeoff

who should keep paying

People still pay for Bolt.new because the UI can be copied, but high-quality code models, context ranking, safe execution, and constant evaluation are the product. The recurring cost buys model changes, indexing, prompt injection, tool permissions, sandboxing, evaluation, telemetry choices, and IDE compatibility, not just the visible interface.

what you lose

browser sandbox, model orchestration, package execution, deployment, and hosted compute

frontier proprietary model

large-scale code retrieval

cloud sandbox fleet

enterprise policy and support

Start with existing software

prior art · use these instead of building, if you'd rather

EVIDENCE LEDGER

What this page can prove

The verdict judges replaceability. The evidence level records what DeepFeather actually checked.

Read the methodology →
evidence level
Curated prompt

The prompt was editor-reviewed; no completed build is recorded.

replacement boundarysingle-repository coding assistant

known limits · browser sandbox, model orchestration, package execution, deployment, and hosted compute; frontier proprietary model

editorial reviewreviewed
closest workaround promptsecondary workaround · reviewed prompt · not run

the prompt

Curated prompt
Build a closest honest personal substitute for Bolt.new in an empty repository.
Use TypeScript, Node.js 22, a VS Code extension, SQLite, and one user-supplied model API; do not offer alternative stacks.
The core loop is: generate and edit a small web project in a local sandbox from structured prompts, index the repository, propose patches, run approved commands, and preserve an auditable session log.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Create a VS Code sidebar with chat, selected-code actions, repository search, and a patch preview.
Index only the open repository and respect .gitignore plus a separate assistant ignore file.
Require explicit approval before reading outside the workspace or running any command.
Represent edits as unified diffs with accept, reject, partial apply, undo, and Git status checks.
Capture tool calls, model requests, command output, and patch decisions in a local session log.
Add token and cost estimates, provider errors, cancellation, tests, and an offline data-flow diagram.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out training or reproducing a frontier coding model.
Deliberately leave out unattended command execution outside a sandbox.
Deliberately leave out cloud workspaces, team policy, and enterprise support.
Finish by running the tests and listing the exact commands used.
Copy or open in an agent

The prompt stays readable first. Choose a launch option when you are ready.

$ open in your agent (prompt prefilled, you press enter) or copy it raw

BUILD FEEDBACK

Did you try this build?

Report the outcome. Submissions enter a manual evidence queue and never auto-upgrade the verdict.

questions

Can AI replace Bolt.new?

Not really. Bolt.new's value is not just interface code — frontier models, context infrastructure, and execution safety. See the honest breakdown above.

How much does Bolt.new cost?

Bolt.new is listed at about $20/month (Pro, checked 2026-07-31), or $240 per year. This is a pricing reference, not evidence of a completed replacement or realized savings.

What do I lose by replacing Bolt.new?

Honestly: browser sandbox, model orchestration, package execution, deployment, and hosted compute; frontier proprietary model; large-scale code retrieval; cloud sandbox fleet; enterprise policy and support. If any of those are load-bearing for you, keep paying.

Is there an open-source alternative to Bolt.new?

Yes — Continue (Active open-source coding-assistant framework for IDEs and multiple model providers.). Using prior art is also a valid exit; the prompt is for when you want it exactly your way.