Use Agentforce Vibes in a Scratch Org

Agentforce Vibes works in scratch orgs without admin involvement. Developers control access through the definition file.

How It Works

To control access for a specific scratch org, edit config/project-scratch-def.json in your Salesforce DX project.

Supported Editions

Agentforce Vibes is available in these scratch org editions:

Developer Edition
Enterprise Edition

Create Scratch Orgs with Unmetered Access

Starting in Summer ‘26, add AgentforceVibesUnmeteredAccess to the features array in your scratch org definition file to enable unmetered access in a scratch org. After creating the org, also assign the required permission set to your user.

Prerequisites

To use unmetered access (Summer ‘26 and later), the corresponding Dev Hub must have unmetered access. See Enable unmetered Agentforce Vibes.

Create the Scratch Org

Add the feature flags to config/project-scratch-def.json:

1{
2  "orgName": "AFV Unmetered Scratch Org",
3  "edition": "Developer",
4  "features": ["AgentforceVibesUnmeteredAccess", "EnableSetPasswordInApi", "EinsteinGPTPlatform"],
5  "settings": {
6    "einsteinGptSettings": {
7      "enableEinsteinGptPlatform": true
8    }
9  }
10}

Then create the scratch org:

1sf org create scratch --definition-file config/project-scratch-def.json --alias my-scratch-org

or use the VS Code command, SFDX:Create a Default Scratch Org…

Create and Assign a Permission Set

Follow the steps in Create and Assign the Unmetered Permission Set to create and assign the unmetered permission set to your user.

After you authenticate to this scratch org in the Agentforce Vibes extension, your user is recognized as an unmetered user.

Models and Limits (Unmetered)

Scratch orgs with AgentforceVibesUnmeteredAccess get the same model access and limits as the standard unmetered tier.

Create Scratch Orgs with Flex Credit Access

The ability to create scratch orgs using flex credits will be available in an upcoming release.

Disable Agentforce Vibes in a Scratch Org

To disable Agentforce Vibes for a specific scratch org, add the opt-out setting to config/project-scratch-def.json:

1{
2  "settings": {
3    "AgentforceForDevelopersSettings": {
4      "agentforceForDevelopersOptOut": true
5    }
6  }
7}

These changes take effect for new scratch orgs created from this definition file. Active scratch orgs aren’t affected.

Considerations

No admin setup required. Unlike production and sandbox orgs, the developer controls scratch org access through the definition file, not through Setup.
Dev Hub is the gate. If your Dev Hub doesn’t have Agentforce Vibes enabled, scratch orgs don’t have it either, regardless of what you put in the definition file. Contact your admin to confirm the Dev Hub state.