I have seen conflicting details about Vibes - adspeak indicates that you can import/open agents in Vibes yet the reality seems to be that Vibes can only access agents that originated with Vibes coding. Which of these is actually true?
1 answer
Great question — Agentforce Vibes IDE has some important compatibility nuances worth clarifying.
Current behavior (as of early 2026)
- Vibes IDE is designed primarily to work with agents that were built or scaffolded within Vibes itself. Agents created fully in Agent Builder (via Setup) are not always directly importable into Vibes without additional steps.
- You can open an existing agent's metadata in Vibes if you pull the agent source via VS Code and the Salesforce CLI (sf project retrieve start), then open that workspace in Vibes. However, the visual design surface in Vibes works best with agents it generated or scaffolded.
- The "import existing agent" capability was listed as a roadmap item; check the Agentforce Vibes IDE release notes for the latest availability.
Recommended approach
- For agents you built in Agent Builder, use the CLI to retrieve and inspect source, then open in Vibes for code-first editing.
- Post questions or vote on the feature in the IdeaExchange to track "import from Agent Builder" support.
In short: the marketing language around "import" refers to importing agent source code from your org via CLI, not a GUI import of an Agent Builder agent into the Vibes visual designer.
