Manage Advanced Custom Fields with AI

What we learned testing it

Behavior the ability descriptions do not mention.

• ACF's abilities are off by default and there is no switch for them in wp-admin. They register only when the acf/settings/enable_acf_ai filter returns true, and then only for field groups, post types and taxonomies with Allow AI Access on in their ACF AI tab. A field group also needs Show in REST API. New field groups, post types and taxonomies start with Allow AI Access on. It is not a permission: the REST API, and ACF's update ability through it, write any field in a group with Show in REST API on, whatever its AI setting.
• The query, create, view, update and delete abilities exist only for post types and taxonomies registered in ACF. Fields on regular posts and pages, or on post types registered by code or another plugin, are read and written through the WordPress REST API instead (the acf object on each post), when the field group has Show in REST API on.
• Their names use the key with underscores turned into hyphens and an s added, so a taxonomy with the key amenity gets acf/amenitys and a post type with the key team_member gets acf/team-members. They are in the category wordpress-content-discovery, so a discover_abilities search filtered to ACF's own category does not show them.
• acf/register-field-group always creates a new group. Running it again with the same title makes a second group, and no ability edits or deletes a field group: change fields in ACF's field group editor.
• acf/field-groups lists the groups without their fields. The fields of a post type show up in the input schema of its create and update abilities, and in each entry's field values.
• The query ability lists published entries only and has no status filter. Read drafts with the view ability by ID, or through the REST API with status=draft.
• The create ability's input schema lists no taxonomy terms or excerpt. Set terms afterwards through the REST API.
• Updates keep the fields you leave out: send only the fields that change.
• Deleting an entry moves it to the trash. Deleting a term is permanent and fails unless force is true. WPVibe asks for your approval in the browser before either runs, unless you turned approvals off for the site or approved that ability for the session.
• acf/custom-post-types and acf/custom-taxonomies do not run through WPVibe yet, because their input schema only accepts no input at all. GET /wp/v2/types and /wp/v2/taxonomies list them, along with every other post type and taxonomy shown in the REST API.
• Field values do not appear on your pages on their own. Your theme, a block or a shortcode has to display them.