Environments

Environments let you maintain separate resource configurations for different stages. Use a staging database for testing and production credentials when you deploy.

Creating environments

1. Go to Settings > Environments
2. Click Add Environment
3. Enter a name (e.g., “staging”)
4. Click Create

Every organization has a default environment that represents production. This environment cannot be deleted or renamed.

Configuring connectors per environment

When you edit a resource, you can configure each environment independently:

1. Go to Organization Settings > Connectors
2. Click on a connector to edit it
3. Select the desired environment
4. Enter the connection details for that environment
5. Click Save

Example

Default Build Environment

Organizations can designate a separate “default build environment”, distinct from the production environment. It is the environment you work in until you choose one yourself. This is useful for testing and development workflows where you want the AI to work against staging data.

Setting a default build environment

1. Go to Settings > Environments
2. In the environment list, select the Set as default build option next to your chosen environment
3. The environment will be marked with a “Default” badge

Your environment choice

Each person picks one environment per organization: their environment choice. It is yours, not an app’s, so it applies to everything you do by hand: Until you pick an environment, the calls that follow your choice use the organization’s default build environment. If your organization has only one environment, there is nothing to choose and the environment selector and tools don’t appear.

Selecting environments in the web editor

The web editor includes an environment selector in the bottom right of the preview. Click it to switch between available environments. When you switch environments:

• Your environment choice changes for every app, not just this one
• Every app preview you have open reloads with the new resource configuration
• API calls use the selected environment’s credentials
• Preview reflects the environment-specific data

The editor’s resource test panels (query tests, and the database and file storage inspectors) each have their own environment picker. They start on the default environment and don’t follow your environment choice.

Selecting environments from MCP clients and chats

In an organization with more than one environment, the Platform Agent and MCP clients have two tools:

• get_environment shows the environment your resource calls use, whether you chose it or it’s the default build environment, and lists the organization’s environments.
• set_environment switches your environment choice by name. Your open app previews reload in the new environment.

Agents don’t get these tools. They always run in the default environment.