Publish an app people can open

Publishing gives visitors a URL for a release of your app. Start with the path that matches your workspace.

Publishing creates a separate release. Your editable workspace and conversation remain private. Review what your app exposes before sharing its URL.

Publish a Free Browser project

1. Finish the current agent run and try the app in your browser preview. Click its main controls and check it at a phone-sized width.

2. Confirm the project has an index.html entry point. If the preview is missing, ask the agent to create or repair that page and its links to the other files.

3. Choose Publish on desktop, or open the three-dot Session menu and choose Publish app on a phone.

4. Review the app name and URL. Choose Publish app in the dialog and follow its progress.

5. When the release succeeds, open the public URL in a private browser window. Try the same actions you tested in the preview.

Free Browser workspaces do not run build commands or server processes. If your project needs package installation, server-side code, a private service credential, or a database server, use a hosted workspace.

Free includes one published static app and one current release. Its published files can total up to 25 MiB. This is separate from your account's editable-project storage allowance.

Publish a hosted application

Start with an app that works in its hosted preview. Ask the agent to inspect the application's production setup:

Prepare this existing app for publishing. Keep its current functionality.
Identify its production build command, start command, listening port, and health path.
Run the relevant checks and report their output.
Tell me which environment variables are required and whether they are needed
during the build or at runtime. Do not put private credentials in browser code.

Resolve build or startup errors before proceeding. A development preview alone may not use the same command or configuration as the published app.

Choose Publish in the simple project view, or open Session menu → Publish app in the Developer workspace or on a phone. Review the name and URL, and inspect the proposed launch details. Rigless can prepare missing launch configuration through the publishing flow. Choose Publish app to start the release.

If the app needs production environment values, open its record in Apps and find Production variables. Enter each required name and value, then choose Add & apply. If the first release stops because a value is missing, configure it here and retry publishing. Values embedded in browser bundles are public; keep private service credentials in server-side code and configuration. A build-time value requires a new build to appear in the app.

Follow the progress through build, startup, and readiness checks. Open the resulting URL in a private browser window and exercise a meaningful behavior, such as submitting a form or loading a page that uses the backend.

Find releases, logs, and configuration in Apps. Use the app's domain settings if you want to connect a custom domain; follow the DNS values shown for that app.

Publish an update

Return to the source project, ask for or make your changes, and check the result. Open the publishing dialog again and choose Publish update for the app associated with that project.

Editing your workspace does not automatically change its existing published release. After publishing, verify the public URL contains the update. Hosted plans retain release history according to their limits and provide rollback controls. Free keeps one current release, so keep a source export before replacing work you may want to restore.

Resolve a publishing failure

Taking an app offline does not necessarily release its plan allocation. Export anything you need before deleting an unused app, or choose a plan with more capacity. Read about plans and limits.

For a complete Free example, follow Build and publish your first app.