Summary: Replit shipped three updates on October 9, 2026: a private-preview Windows desktop app built with Microsoft and NVIDIA, the ability to work across multiple projects from a single chat, and TikTok Ads campaign management through MCP. Together they push the agent from a per-project coding helper toward something that coordinates across your workspace and even your marketing stack.
Local builds on Windows, one sandbox per run
The headline item for anyone who prefers a native machine over a browser tab: Replit Desktop can now build and run apps locally on a Windows PC, in private preview. Each agent build runs in its own isolated sandbox powered by Microsoft Execution Containers (MXC) and NVIDIA OpenShell, per the changelog, and early access is behind a waitlist.
The isolation detail matters as much as the platform port. If the agent is going to install dependencies, run builds, and execute code on your actual hardware, you want each run fenced off rather than executing loose on your dev machine. Replit’s choice of container-backed sandboxes suggests they’re treating local execution with the same caution as their cloud environment.
One chat, many projects
The second change addresses a friction I hear about constantly from teams running agent workflows: context is trapped per project. You can now ask Replit to find existing projects, read their files, and dispatch tasks to them from one conversation. Name a project or describe it, and its context becomes usable without switching.
Two guardrails stand out. Changes run as background tasks you can review, and nothing publishes automatically. That’s the right default — cross-project operations are exactly where a runaway agent does the most damage.
The use cases Replit names are concrete: port a feature from one app to another, compare how your apps behave, or draft documentation across several websites at once. If you’ve worked with tools like Cursor plugins, you know the value of keeping the agent inside the surface where you already think. This extends that idea across project boundaries instead of just file boundaries.
Ads become an agent workflow
The third update is the most surprising. Through MCP, you can connect a TikTok Ads account and have Replit create, launch, and track campaigns from a chat — set a budget and schedule, ask for performance reports, and use Replit’s asset tools to generate the creative.
For a solo builder or a tiny team shipping a product, this collapses a workflow that normally spans a code editor, an ads console, and a design tool. It’s also a telling sign of where MCP is heading: the protocol isn’t just connecting agents to databases and browsers, it’s reaching into ad platforms where real money gets spent. That raises the stakes on review and permissions — I’d want granular budget caps before letting an agent launch anything.
What to watch
This changelog sketches a trajectory: execution moving local, agent scope widening from one repo to many, and integrations reaching beyond development into operations. The Windows preview is invite-only, so most readers can’t test the local sandbox story yet — and the supplied changelog doesn’t specify pricing or availability timelines.
The practical next step is the one you can do now: the cross-project chat and TikTok Ads integration are live, so pick a low-risk task — a documentation sweep across two projects, or a small test campaign with a hard budget — and see how the review-before-publish flow holds up before trusting it with anything bigger.
If you’re thinking about which agent tooling deserves a slot in your setup, it’s worth reading how I approached that filtering problem for another editor in Twelve Cursor Plugins Worth Your First Install.
Sources
View the original post on X