Installation is two clicks. The work that matters is connecting to the right org, letting the metadata index finish, and committing a `.vibes.json` so the whole team gets the same agent behavior. The chat is ready to use the moment indexing finishes, but the team-shared config is what makes the extension pay off across more than one developer.
- Install from the VS Code Marketplace
Open the Extensions view in VS Code, search "Agentforce Vibes", and install. Restart VS Code to load the command palette entries and sidebar panel.
- Authenticate against the target org
Open the Agentforce Vibes sidebar. Click Connect Org. Pick Web Server (interactive) or JWT (CI-friendly) or pick an existing sfdx alias if you have Salesforce CLI already configured. Accept the OAuth consent in the browser.
- Let the metadata indexer finish before chatting
The first index runs in the background and shows progress in the status bar. Chat will work without it but suggestions will be ungrounded. Wait the 2 to 10 minutes for the index to complete before judging suggestion quality.
- Create a project-level .vibes.json
At the project root, create `.vibes.json` with apiVersion, lint rules, and a list of test classes to always run. Commit it. Teammates get the same agent behavior without reconfiguring per machine.
- Try a small change end to end
Pick a real but low-risk task ("add a getter on Contact controller that returns last login"). Use the chat to describe the change, accept the diff, ask the agent to write tests, run the tests inline, commit.
- Configure refusal patterns for sensitive paths
Open the extension settings and add file globs or branch patterns the agent should refuse. Production-named branches and any regulated module paths belong in this list before broad team rollout.
- Schedule a weekly cache refresh
Metadata changes (new custom fields, new objects) need an index refresh to surface in completions. Set the cache refresh schedule in settings to daily or weekly depending on how often the team adds metadata.
The Salesforce org the extension authenticates against. Drives which metadata grounds the suggestions.
Project-level pin for API version, lint rules, and required test classes. Shared across the team via source control.
File globs or branch patterns the agent will not read or write to. The compliance lever for sensitive code paths.
Whether prompt and response content is sent to Salesforce for service improvement. Default is off; explicit opt-in only.
How often the local metadata cache re-indexes against the connected org. Daily or weekly is typical.
- Chatting before the metadata index finishes produces ungrounded suggestions that reference hallucinated fields. Wait for the index status bar to clear before judging quality.
- Multi-org developers who forget to switch active org get suggestions grounded against the wrong org's metadata. The active org indicator is always visible in the status bar; check it before any non-trivial change.
- The .vibes.json applies to every developer on the project. A bad change here silently changes everyone's agent behavior on next pull. Treat the file as production config.
- Telemetry is opt-in for prompt content but always-on for usage counts. Privacy-strict environments should confirm what is sent at the SOC 2 review level before broad rollout.
- The extension and the standalone IDE share an authentication store. Connecting to a new org in one re-authenticates the other; this is intentional but occasionally surprising.