Replit previews a Windows app that builds and runs software locally

Why it matters

Replit is moving its AI app-building workflow onto users' Windows machines, where local files and permissions raise higher stakes. The preview also gives Microsoft and NVIDIA a route to put their agent-containment tools into a widely used creation product.

Replit CEO and co-founder Amjad Masad said on October 7th that the company is previewing a Windows desktop app designed to build and run applications on a user's computer. Replit says each build runs in its own sandbox, using Microsoft Execution Containers and NVIDIA OpenShell. The preview is available by waitlist, not as a general release, through Replit's desktop preview page.

https://x.com/Replit/status/2107896848044437766

The move takes Replit's app-building pitch beyond the browser. The company built its product around making software creation accessible without requiring users to set up a conventional development environment. Masad has described how, as a young coder in Amman, he repeatedly had to rebuild his setup when switching computers. He later worked at Codecademy and Facebook before founding Replit. A desktop product that runs code locally changes where that familiar promise has to hold: on a user's own machine, alongside files and applications that may contain sensitive information.

That makes the sandbox part of the announcement central to the product. Replit says each generated build runs separately rather than sharing unrestricted access to the host computer. Microsoft describes its Execution Containers SDK as a way for developers to apply containment policies to local agents, including process and session isolation. NVIDIA describes OpenShell as an agent runtime that applies sandboxing and policy controls around agent access. Those descriptions explain the intended safeguards; they do not establish how every permission will be configured in Replit's preview or guarantee that generated code cannot cause harm.

NVIDIA's OpenShell documentation lists a Windows Microsoft Execution Containers runtime as "Coming soon." That is consistent with Replit presenting this as an early-access preview rather than a finished, broadly available product. The waitlist page says selected users will be contacted for access and shows an example app running at localhost:13000. Replit has not given a general-release date, published hardware requirements, or announced a price for the desktop app.

The shift also tests a tension in Replit's longstanding product design. Masad and co-founder Haya Odeh built a browser-based coding environment that reduced setup work and lowered the barrier for new creators. Odeh, Replit's co-founder and vice president of design, helped shape the interface around people who were not professional developers. Replit's own account of its early product emphasized going from writing code to hosting a project in one environment. Local execution asks the company to preserve that simplicity while exposing a more complex layer: operating-system permissions and the boundary between an AI-generated app and a user's computer.

For Microsoft and NVIDIA, the partnership puts their agent-containment tools inside a consumer-facing developer product. Microsoft says Execution Containers are intended to control what local agents can access under policy; NVIDIA says OpenShell can govern agent execution and access. Replit supplies a practical use case: a user asks an AI system to create an app, then wants to run it without first sending the build to a cloud environment. The partners' descriptions establish the architecture they are promoting, while the waitlist preview will show how much of that control is visible to users.

Replit's October 7th post on X calls the app a preview and invites users to join the waitlist. The announcement does not say whether projects can move between the desktop app and Replit's existing cloud tools, what data or files a build can access by default, or whether users can inspect or change sandbox policies. Those product details will determine whether local execution offers a useful alternative to cloud-based app building or mainly shifts the security and setup questions onto the desktop.