Yesterday I've tried using Agentforce Vibes for a metadata change. It seems to have improved a lot since the last time I experimented it.
The task was to create new list views from existing ones on Account, Lead, Contact, Campaign, and Opportunity, add an "ABC_" prefix, add a record type criteria and change labels to follow a pattern.
This time Agentforce Vibes broke the work into a few steps and validated intent before execution.
It correctly avoided changing API names (fullName), only labels.
It hesitated a bit before finding list views outside the Opportunity folder but it did find and applied the change correctly after confirmation.
There was one instance though that it failed to add object prefixes in list view filters (RECORDTYPE vs CAMPAIGN.RECORDTYPE) but it was a minor issue.
Agentforce Vibes does honor the AGENTS.MD standard so it looks possible to add something to prevent minor mistakes such as that one.
It created the list views all in one go. Imagine having to clone each list view in each object manually and repeat the steps for the adjustments.
Agentforce Vibes is now looking like a big time saver!
