Environment variables

Projects need configuration — API keys, connection strings, feature flags. They live in the project's Env tab.

When an agent asks

If an agent needs a value it cannot have, it asks rather than inventing one or hard-coding a placeholder that breaks later. You supply it in Env; the run continues.

That request is a good signal. An agent that silently invented a key would produce code that looks finished and fails in a way that is hard to trace.

Steps

1. Open the project's Env tab.
2. Add each variable with its real value.
3. Restart the preview so the new values are picked up.

You're done when the app runs without configuration errors in the Logs tab.

Gotchas

• Env values are per project. They do not leak between projects, and they are not your workspace's provider keys.
• Restart after changing. A running process holds the values it started with.
• Never paste a secret into chat. Put it in Env — chat is a transcript.