---
schema_version: "1"
id: d44d2a362015487368b2dc5bba2438c86cfee3fdf2e5cb4877c29275439617f9
title: Agentforce Vibes Quick Start
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/agentforcevibes/guides/files/afv-quickstart.md
canonical_url: https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-quickstart.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: c4e70c813f7c3a52a7a21d92169c70424db15b2414ae394382daa57292ebab69
products:
  - Agentforce Vibes Developer Guide
  - salesforcedx
---
# Agentforce Vibes Quick Start

This topic walks you through your first three interactions with Agentforce Vibes: asking a question, making a code change, and using Plan Mode.

## Prerequisites

Make sure you've completed the following:

- Installed the [Salesforce Extension Pack](https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode) in VS Code.
- Opened a Salesforce DX project (your workspace must contain an `sfdx-project.json` file).
- Set a Salesforce org as your default org.
- Using the latest version of Agentforce Vibes.

See [Get Started with Agentforce Vibes](https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-get-started.md) for full installation steps.

## Step 1: Ask the Agent a Question

Start with a read-only task to get familiar with how the agent responds.

1. Click the **Agentforce Vibes** icon in the VS Code activity bar to open the panel.
2. In the chat input, type a question about your org or project. For example:

   > `What sObjects are in this org and which ones have the most fields?`

3. Press **Enter**.

The agent queries your connected org's metadata and returns a response in the chat. You see it reason through the answer in real time as the response streams in.

**What just happened:** Agentforce Vibes used the Salesforce DX Model Context Protocol (MCP) server to look up your org's schema. It didn't guess—it read real metadata from your connected org.

## Step 2: Make a Code Change

Give the agent a task that produces output you can review.

**tip:** Before running larger tasks, create a checkpoint from the **Toolkit** tab to roll back if the output isn't what you expected.

1. In the chat input, describe a small, concrete piece of work. For example:

   > `Create an Apex trigger on the Account object that sets the Description field to "Updated by trigger" before insert. Include a test class.`

2. Press **Enter**.

The agent generates the Apex trigger and test class. When it makes file changes, a diff view appears inline in the chat so you can see exactly what changed before accepting.

1. Review the diff. If the output looks right, accept the changes. For guidance on what to verify before accepting, see [Trust and Verification](https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-trust.md).

**What just happened:** The agent created files directly in your workspace. It used your org's metadata to reference real API names rather than placeholder values.

## Step 3: Try Plan Mode

Plan Mode lets you see and approve a structured plan before the agent makes any changes. Use it when a task spans multiple files or has dependencies you want to verify first.

1. Click **Plan Mode** in the bottom bar of the Agentforce Vibes panel to switch modes.
2. Describe a multi-step task. For example:

   > `Build an LWC component that displays a list of open Cases for the current user, with an Apex controller and a Jest test.`

3. Press **Enter**.

The agent returns a structured plan with Goals, Non-Goals, an Approach, and numbered tasks. Read through it and iterate in conversation if anything looks off — ask it to change the approach, add a step, or remove something.

4. When the plan looks right, click **Approve Plan**.

The agent executes the plan in sequence. Agentforce Vibes creates a checkpoint before any files change.

**What just happened:** You reviewed the full approach before committing to execution. This approach is the right pattern for any multi-file feature where execution order matters.

## What to Do Next

You've covered the three core interactions in Agentforce Vibes. From here:

- **Add context** — use `@` to pull specific files, workspace problems, or terminal output into your next prompt. See [Add Context](https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-add-context.md).
- **Create a Rule** — encode a coding convention the agent should always follow. See [Rules](https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-rules.md).
- **Explore Skills** — enable built-in Platform skills for Apex, Lightning Web Components (LWC), and Flow generation. See [Skills](https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-skills.md).

## See Also

- [Trust and Verification](https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-trust.md)
- [Workflow Patterns](https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-workflow-patterns.md)