You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
An ability to update a post's featured image and other non-content fields #1305
The "Audit content" demo finds posts with no featured image, but the workspace can't fix them: there's no ability to set _thumbnail_id, and #945 (core/edit-content) edits only the title, excerpt and content text. So the demo stops at the list.
Proposed: a write ability for a bounded set of fields:
the featured image, from an attachment ID the user can read;
perhaps categories and tags, and the excerpt.
It would check edit_post per post. In the workspace it would run through a proposal kind (#1304), so a person approves the exact change first. It's the write twin to #1302's has_featured_image filter, and would sit beside #945 rather than inside it.
AI assistance: Yes. Tool(s): Claude Code (Claude Opus 5.5). Used for: drafting this issue from the work in the linked PRs, which I checked.
I've reviewed the changes, understand them and can explain them under review.
Hi @whyisjake, I'd like to work on this one. Before I open a draft PR, a few questions to keep it aligned with #1302, #1304 and #945:
Scope for a first PR. Would you be OK with starting with the featured image only (set and remove), and leaving terms for a follow-up? I'd leave the excerpt out, since core/edit-content (Add core/edit-content ability for targeted post content edits #945) already covers it.
Name and location. Since this ability doesn't mirror anything in core, I was thinking of an ai/ name next to the existing ai/get-post-terms (for example ai/set-featured-image), so it isn't tied to the core/* move discussed in Proposal: Use wordpress-abilities as central ability provider #1289. Does that work, or should it go somewhere else?
Checks. My plan is:
edit_post on the post;
the post type supports thumbnail and is exposed through show_in_abilities;
the attachment exists, is an image (wp_attachment_is_image()), and the user can read_post it.
Removing would use delete_post_thumbnail(). Any other rules you want?
@jorgefilipecosta@ntsekouras is this something you'd rather get added in a core ability / abilities package or ok with sit being an ai plugin specific ability? My gut sense is "yes", but we could always start in the ai plugin and then move to the package if desired?
@jeffpaul This seems like a candidate for a core ability (editing post meta), so I'd like to see it in the abilities package, which has systems for managing the experimental -> core-bound -> in core lifecycle. For abilities defined in this plugin directly, I'd like to keep those down to only those that face plugin-provided domains/functionality (e.g. something like ai/generate-alt-text).
@jorgefilipecosta has been closer to the specific set of abilities we have, so I'd want his take on whether this should be it's own atomic ability (e.g. /update-feature-image), or part of a new, higher-level non-content ability (e.g. /edit-post-meta). That might need some discussion, but doesn't change the placement decision.
Activity
Deepak-Bhojwani commentedon Nov 7, 2026
Hi @whyisjake, I'd like to work on this one. Before I open a draft PR, a few questions to keep it aligned with #1302, #1304 and #945:
Scope for a first PR. Would you be OK with starting with the featured image only (set and remove), and leaving terms for a follow-up? I'd leave the excerpt out, since
core/edit-content(Add core/edit-content ability for targeted post content edits #945) already covers it.Name and location. Since this ability doesn't mirror anything in core, I was thinking of an
ai/name next to the existingai/get-post-terms(for exampleai/set-featured-image), so it isn't tied to thecore/*move discussed in Proposal: Usewordpress-abilitiesas central ability provider #1289. Does that work, or should it go somewhere else?Checks. My plan is:
edit_poston the post;thumbnailand is exposed throughshow_in_abilities;wp_attachment_is_image()), and the user canread_postit.Removing would use
delete_post_thumbnail(). Any other rules you want?Workspace integration. Should the first PR add only the ability, with its tests and annotations (not read-only, idempotent), and leave the proposal kind for after AI Workspace: a registry of proposal kinds as the way to add new kinds of change #1304 and Add the Global AI Workspace #1004 settle? Or would you rather both land together?
Happy to adjust based on your answers.
jeffpaul commentedon Nov 8, 2026
@jorgefilipecosta @ntsekouras is this something you'd rather get added in a core ability / abilities package or ok with sit being an ai plugin specific ability? My gut sense is "yes", but we could always start in the ai plugin and then move to the package if desired?
nikolas4175-godaddy commentedon Nov 10, 2026
@jeffpaul This seems like a candidate for a core ability (editing post meta), so I'd like to see it in the abilities package, which has systems for managing the experimental -> core-bound -> in core lifecycle. For abilities defined in this plugin directly, I'd like to keep those down to only those that face plugin-provided domains/functionality (e.g. something like
ai/generate-alt-text).@jorgefilipecosta has been closer to the specific set of abilities we have, so I'd want his take on whether this should be it's own atomic ability (e.g.
/update-feature-image), or part of a new, higher-level non-content ability (e.g./edit-post-meta). That might need some discussion, but doesn't change the placement decision.jeffpaul commentedon Nov 13, 2026
Flagging to @nikmclaughlin that this will be needed in the abilities package to benefit the AI Workspace effort.