A Private Workspace and a Live Preview for Every Project

Every Mythex project runs in its own private cloud workspace with a live preview beside the chat. How it works, how to use it, and what to expect.

Mythex Team · 2026-09-29 · 4 min read

Every Mythex project gets its own private cloud workspace: files, running processes, a preview and a terminal, kept separate from everyone else's. The right side of the workspace shows your app running live while you chat, so you can click through it, check it at phone size and share a link to it before anything is published.

What it does

A workspace per project

When Mythex builds your app, it isn't writing code into a void. It works inside a private workspace that belongs to that one project. That is where packages get installed, where your app's server runs, and where the terminal opens when you switch to Code.

Because each project has its own, three things follow:

Your installs and servers never collide with anyone else's.
Mythex can safely install packages and run your app for that project.
Preview and the terminal always point at your project.

A live preview beside the chat

The right side of the workspace toggles between Preview and Code. Preview shows your app running — not a screenshot, not a mockup. You can click through real flows, fill in forms, follow navigation and spot problems before you publish.

Code gives you the file tree, an editor, and an interactive terminal in the same private workspace, for when you want precision or a developer joins the project.

Why it matters

An app builder that only shows you code asks you to imagine the result. One that only shows you a picture hides whether the buttons actually work. A running app in its own space answers the question you actually have: does this do what I asked?

Keeping the workspace private matters for the same reason. When the agent installs something or restarts a server, it affects your project and nothing else, and nothing anyone else does can break yours.

Pausing and waking

A workspace you aren't using pauses on its own. It comes back the moment you need it — opening the project, chatting, editing or loading the preview all wake it. Running processes are restored with it, so there is nothing to restart.

Waking takes a few seconds. While it happens, the preview panel says where it has got to — provisioning the sandbox, then waiting for your app's server — and shows tips on what Mythex can do while you wait. You may see Starting your workspace…, Starting your app… or Getting your app ready…. That's normal.

What survives a pause:

Your project files and history
Project settings and secrets
Published apps, which run separately from the private workspace

How to use the preview

Open a project. The preview starts on its own as the workspace wakes.
Click through it as a visitor would. Try the forms and the navigation.
Visit a specific page by typing a path such as /about in the address bar and pressing Enter. Back and Forward walk through the pages you've opened this session.
Check phone size. Click the phone icon (Switch to Mobile) for a phone-size frame of your app, and drag its left or right edge to change the width. Drag it almost to full width and release to go back to desktop.
Resize the panes by dragging the divider between chat and preview. The panel icon hides or restores the chat.
Open in new tab or Refresh from the same bar when you need them.

If your project runs more than one service, a dropdown in the bar lets you switch which one you're previewing.

On a phone, the builder shows one pane at a time — the chat or your app — and you swipe or tap to move between them. The preview is already full width there, so to see how your app looks at phone size, use a laptop and Switch to Mobile.

Share, next to Publish, creates a link that opens your project's live preview for someone without a Mythex account. It's for showing work in progress — to a client, a teammate or a group chat — without publishing something that isn't finished.

Create new preview link asks you to name it, then copies it to your clipboard. The name is only shown to you, so a list of links reads as a list of audiences.
Copy copies a link again later.
Delete stops the link working within seconds, everywhere.

Someone with the link sees your app exactly as Preview does, and nothing else: no chat, no code, no terminal, no settings, no way to edit. Make one link per audience, so deleting one is a decision about that audience only.

Limits worth knowing

The first open of a shared link can take up to a minute while the project wakes and your app's server starts from cold. The visitor sees a page that reloads itself until the app answers. If you're demoing live, open the link yourself a minute beforehand.
A shared link shows the live sandbox, including changes mid-build.
Waking a project uses your plan's credits and sandbox limits, whether you open it or someone with a link does. Delete links you're done with.
The phone-size frame is for responsive web layout. Native phone apps are still coming soon.
If the preview is blank or stale, check that the app is running in the terminal, click Refresh, or use /fix. If the workspace won't wake, refresh and retry, and contact support with the project ID if it persists.

When you want an agent to click through the preview for you, see App Testing. For why it pays to try changes somewhere other than your live site, see our guide to staging environments.

Full details are in the docs: Private workspace and Preview and Code.