A site connected to WPVibe running Advanced Custom Fields 6.8 or newer (tested on 6.8.10, the free version) on WordPress 6.9 or newer, with ACF's AI abilities turned on (this recipe does it). A post type registered in ACF with AI access on.

The prompt

My WordPress site uses ACF with its AI abilities turned on. On my [post type] entry [title or URL], change [field] to [new value] [and any other changes].

1. Find the entry with the post type's acf/ query ability and search=[title] (run discover_abilities for its exact name: the key with underscores turned into hyphens, plus s). It lists published entries only; for any other status, use GET /wp/v2/[post type REST base]?status=draft,pending,future,private&search=[title]. If more than one entry matches, list them with title, status and ID and ask me which one. Read the entry with the acf/view- ability.
2. Show me the entry's title, ID and status, then each field you will change, with its current value and the new one. Check each new value fits its field: a number for a number field, one of the choices for a select field. Wait for my yes, and remind me that a published entry changes on the live site as soon as it saves.
3. Run the acf/update- ability with the entry's id and, inside acf, only the fields that change. Do not send fields that stay the same, and do not change the title, content or status unless I asked.
4. Read the entry back with the acf/view- ability and confirm every field, changed and unchanged, has the value it should.

Already connected?

Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:

Run the “Update ACF Field Values on an Entry with AI” recipe from the WPVibe cookbook on my connected site.

Prices go up, check-in times change, a speaker swaps sessions. Each change is one field on one entry, but it means finding the entry, scrolling to the field group, and hoping nothing else on the screen got bumped before you click Update.

Tell the AI what changed. It finds the entry, reads its current values with ACF’s own view ability, and shows you each field it will change with the old and new value. It checks the new value fits the field, saves only the fields that change, and reads the entry back to confirm the rest are untouched.

If the entry is published, the change is live as soon as it saves, so read the before and after before you say yes. ACF’s query ability lists published entries only; the recipe looks up drafts and other statuses through the REST API instead.

Outcome

The fields you approved are changed on the entry, and every other field is confirmed unchanged.