WordPress.org
Get WordPress

Make WordPress Core

Changes between Initial Version and Version 13 of Ticket #64657


Ignore:
Timestamp:
07/01/2026 04:34:26 PM (5 weeks ago)
Author:
jorgefilipecosta
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #64657

    • Property Keywords abilities has-patch added
    • Property Component AI → Abilities API
    • Property Type defect (bug) → enhancement
    • Property Version trunk
    • Property Milestone Future Release → 7.1
    • Property Owner set to jorgefilipecosta
    • Property Status new → assigned
    • Property Summary Add `core/get-user` ability → Add `core/read-users` ability

  • Ticket #64657 – Description

    initial v13  
    11
    2 Introduce a new Abilities API ability, `core/get-user`, to retrieve profile data for a specific user by `id`, `username`, or `email`.
     2Introduce a new Abilities API ability, `core/read-users`, to retrieve profile data for a specific user or a collection of users.
    33
    44Core currently has `core/get-user-info` for the current authenticated user only (and not exposed in REST). Agent/workflows use cases need to be able to look up any user when permissions allow it.
    55
    6 == Proposed behavior ==
    7 * Register `core/get-user` in the `user` ability category.
    8 * Input schema:
    9   * Require one of: `id` (integer), `username` (string), or `email` (string).
    10   * Optional: `include_capabilities` (boolean, default `false`).
    11 * Output schema includes:
    12   * `id`, `username`, `email`, `display_name`, `first_name`, `last_name`, `nickname`, `description`, `url`, `link`, `slug`, `registered_date`, `roles`, `locale`, `avatar_urls`.
    13   * Optional `capabilities` when `include_capabilities` is true.
    14 * Permission model:
    15   * User must be logged in.
    16   * Users can view their own record.
    17   * Viewing other users requires `list_users`.
    18 * Expose the ability in REST (`show_in_rest` true).
    19 * Return `user_not_found` error when no matching user exists.
    20 
    21 == Notes / follow-ups ==
    22 * This ticket scopes the initial profile payload.
    23 * Follow-up can extend response data (for example, registered user meta with schema).
    246
    257
    … …  
    279* https://github.com/WordPress/wordpress-develop/pull/10775
    2810* https://github.com/WordPress/ai/issues/40
     11* https://github.com/WordPress/ai/pull/774