Understanding your app's URL environment variables

Use the production and preview URL values for their intended contexts without putting secrets in browser variables.

VITE_APP_URL represents the app's production address. VITE_APP_PREVIEW_URL represents its preview address. They are different contexts; a link meant for customers should not send them to the editor's preview.

The platform maintains these system values when the app's address or canonical domain changes. Check the current values in Env Vars instead of copying an old address from another app. Replacing a URL in a source file is not the same as changing the app's configured domain.

Variables beginning with VITE_ are available to browser code. Do not put private API keys, tokens or passwords in them. Store private values as secret server environment variables.

For links that should stay on the current website, ask the builder whether a relative URL is appropriate. Do not replace every address with the production URL: authentication callbacks and preview behavior need their own correct destinations.

Publish changed app code before testing the live address.

Was this helpful?

Thanks for the signal — it helps us improve the docs.

More in Advanced

Using Overskill from AI agents (Claude, Cursor, Codex)

Connect your assistant to Overskill with the hosted MCP URL and browser sign-in. Check the connected team, access and credits before building.

Getting started with the Overskill partner API

Generate, manage, and deploy apps programmatically. Auth, the core call sequence, and working code in Node, Python, and curl.

Overskill API errors and how to handle them

What 401s, rate limits, credit exhaustion, and other API errors look like — and the right way for your code (or your agent) to respond.

Still need help?

If this didn't answer your question, our team is one click away.