There’s a weird ritual developers still perform in 2026. You want to build a web app, so you open a different app — a terminal, an editor, a local dev server — and you work on it there, on one specific machine, tethered to a desk. When you’re done for the day, you push your code and hope you remember where you left off tomorrow.

What if the place where you build the app was the app?

The tools exist. The workspace doesn’t.

Look at what’s available right now:

Bolt.diy — describe what you want, get a full-stack web app generated in front of you. Not a wireframe. A running application with real components, real routes, real logic. Iterate by talking to it.

Frontman — a visual frontend editor that works directly on your running app. Point at an element, change it, see the result live. No switching between code and browser.

Stagewise — bridge between your browser and your AI agent. Click on a UI element, describe what you want changed, and the agent modifies the actual source code. Visual editing that writes real code.

Each of these tools is powerful on its own. But they all need somewhere to run. A machine with Node installed, dependencies resolved, a dev server running, ports exposed. On a laptop, that’s your problem to solve. On a cloud VM with a public URL, it’s already done.

Put them inside a persistent cloud environment, and something clicks: you’re building a web app from inside a web app. The browser is the IDE, the preview, and the deployment — all at once.

The flow

You open your environment URL from a browser. Any browser. Your laptop, your tablet, your phone.

You tell Bolt.diy: “build me a SaaS landing page with pricing tiers and a waitlist form.” It scaffolds the entire project — framework, components, styles, a running dev server. The result is immediately live at your environment’s public URL.

You pull up Frontman to tweak the layout visually. Drag elements, adjust spacing, change colors — all on the live running app. No code editor needed.

You notice the CTA button feels off. You open Stagewise, click the button in the browser, type “make this more prominent, add a subtle gradient, increase the font size.” The agent modifies the actual source files. The page updates.

You commit. It auto-pushes to GitHub.

You close the tab and get on a train. An hour later, you open the URL on your phone. The environment wakes in under a second. You use Stagewise to tweak the mobile layout. Commit. Close the tab. The VM sleeps.

At no point did you open a terminal. At no point did you install a dependency. At no point were you locked to one device.

Why this matters now

The tools for building web apps visually and conversationally have gotten good enough to be real. Bolt.diy generates production-quality scaffolds. Stagewise and Frontman let you manipulate running applications without touching source code directly. The models behind them understand layout, styling, and component architecture well enough to make meaningful changes from natural language.

But these tools still assume a traditional development setup. Install them locally. Run them on your machine. Manage the dev server yourself. This undercuts the entire promise — if you need a full local environment to use a tool that’s supposed to eliminate the need for a full local environment, something’s broken.

The missing piece is a workspace that comes with these tools pre-installed, running on a VM you access through your browser. The workspace is a web app. The thing you’re building is a web app. The URL where you work and the URL where the result lives are the same place.

Auto-commit, auto-push, auto-sleep

There’s a specific quality of life unlock here that matters for how people actually work.

Auto-commit and push. The environment watches for meaningful changes and commits them to your GitHub repo automatically. You don’t lose work because you forgot to save before closing a browser tab. Your Git history stays current without you thinking about it.

Auto-sleep. Fifteen minutes of inactivity and the VM snapshots. Zero cost. Zero resources. The next time you open the URL — tomorrow morning, next week, from a different continent — it wakes in under a second, dev server and all.

This combination means you can pick up and put down projects with zero friction. Start something on your lunch break. Continue it on the couch. Show it to a friend by sending the URL. Walk away for two weeks, come back, and everything is exactly where you left it.

No “let me set up my environment.” No “let me start the dev server.” No “let me find where I was.” Open the URL. You’re there.

From anywhere means from anywhere

“Work from anywhere” usually means “work from anywhere that has your laptop.” A cloud environment with a browser-based toolkit actually means anywhere.

Waiting at the airport with just your phone? Open the URL, use Stagewise to make a visual tweak, commit, close. The whole interaction takes two minutes and the VM sleeps for the rest of your flight.

A client asks to see progress during a meeting? Pull up the URL on the conference room screen. It’s live. Make a change in front of them if they have feedback.

A designer wants to adjust spacing without filing a ticket? Give them edit access. They open the URL, use Frontman to move things around, commit. No developer context-switching required.

The environment doesn’t care what device you’re on. It doesn’t care where you are. It’s a URL, and behind that URL is a full VM with your code, your tools, and your running application — awake when you need it, asleep when you don’t.

Websites building websites

The logical endpoint of browser-based development tools running inside browser-based development environments is recursive in the best way: you’re using a web app to build a web app, and the result is immediately another web app that anyone can visit.

No local toolchain. No deploy pipeline. No device dependency.

Just a URL that’s simultaneously your workspace, your preview, and your production environment — accessible from a train, an airport, or a phone screen.