Abilities API: Implement server-side registry with REST API endpoints - #9410

Closed
gziolo wants to merge 31 commits into
WordPress:trunkfrom
gziolo:try/abilities-api
Closed

Abilities API: Implement server-side registry with REST API endpoints#9410
gziolo wants to merge 31 commits into
WordPress:trunkfrom
gziolo:try/abilities-api

Conversation

@gziolo

@gziologziolo commented Aug 8, 2025•
edited
Loading

Copy link
Copy Markdown
Member

Trac ticket: https://core.trac.wordpress.org/ticket/64098

Part of Building Blocks for WordPress AI.

The Abilities API transforms WordPress from a collection of isolated functions into a unified, discoverable system. By creating a central registry of capabilities, it allows AI agents, automation tools, and developers to understand and interact with everything WordPress can do – from CLI commands and REST API endpoints to custom logic and plugin functions.

Full proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Handbook page at https://make.wordpress.org/ai/handbook/projects/abilities-api/.
Documentation in https://github.com/WordPress/abilities-api/tree/trunk/docs.
Developed in https://github.com/WordPress/abilities-api.
Composer package: https://packagist.org/packages/wordpress/abilities-api.

This PR contains six incremental commits added at different times after syncing directly from https://github.com/WordPress/abilities-api without any modifications. The last update is from October 14th (9906821) and equals the state in the v0.3.0-rc release available for the Composer package.

TODO

Follow-ups

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@gziologziolo self-assigned this Aug 8, 2025
@gziologziolo mentioned this pull request Aug 8, 2025
Merged
@github-actions

github-actionsBot commented Aug 8, 2025

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@gziolo

gziolo commented Aug 13, 2025

Copy link
Copy Markdown
MemberAuthor

The changes landed in the Abilitis API plugin with WordPress/abilities-api#3.

@gziologziolo mentioned this pull request Aug 14, 2025
Closed
9 tasks
@gziolo
gzioloforce-pushed the try/abilities-api branch 2 times, most recently from f2a5ae1 to f825e40CompareAugust 18, 2025 10:33
@gziologziolo mentioned this pull request Aug 18, 2025
Merged
@gziologziolo mentioned this pull request Aug 26, 2025
Merged
@gziologziolo mentioned this pull request Aug 27, 2025
Merged
@gziologziolo mentioned this pull request Sep 8, 2025
Merged
@gziolo
gzioloforce-pushed the try/abilities-api branch 2 times, most recently from 0c1ee5e to 9e2c2ffCompareSeptember 29, 2025 12:52
@gziologziolo mentioned this pull request Sep 29, 2025
Merged
@gziolo
gzioloforce-pushed the try/abilities-api branch 2 times, most recently from 3bc83b6 to 8362bcbCompareOctober 1, 2025 07:54
@gziologziolo mentioned this pull request Oct 10, 2025
Merged
@gziolo
gzioloforce-pushed the try/abilities-api branch 2 times, most recently from df786b2 to d7b4f3dCompareOctober 14, 2025 14:14
@gziologziolo mentioned this pull request Oct 14, 2025
Merged
@gziolo

gziolo commented Oct 15, 2025•
edited
Loading

Copy link
Copy Markdown
MemberAuthor

Two weeks ago, I synced changes from v0.2.0 in Abilities API repository with fd7412b.

Yesterday, I synced changes from v0.3.0-rc in Abilities API repository with 9906821.

@gziologziolo changed the title Abilities API: Implement server-side registryAbilities API: Implement server-side registry with REST API endpointsOct 15, 2025
@gziolo
gzioloforce-pushed the try/abilities-api branch 2 times, most recently from f9a8f24 to d35222fCompareOctober 15, 2025 20:28
gzioloand others added 9 commits October 21, 2025 14:37
@gziolo
Fix bug in the permission check for ability in REST API run controller
1e54797
@gziolo
Improve handling for init hooks related to abilities and their catego…
57d8eda
…ries
@gziolo@aaronjorbin
Apply suggestions from code review
6cb5d7c
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@aaronjorbin
Update src/wp-includes/abilities-api/class-wp-ability.php
7f68dd9
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@TimothyBJacobs
Apply suggestions from code review
b36ea85
Co-authored-by: Timothy Jacobs <timothy@ironbounddesigns.com>
@gziolo
Rename REST routes and controllers
e124094
@gziolo
Enforce init hook before using ability related registries
1dec6a7
@gziolo
Increase testing code coverage for required init action check in ab…
2dbde17
…ility categories registry
@gziolo
Promote validate_input to public method and refactor usage
bcc6ff9
@gziolo
gzioloforce-pushed the try/abilities-api branch 2 times, most recently from 9939e36 to 3d2c27aCompareOctober 21, 2025 12:50
pento pushed a commit that referenced this pull request Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
cd95bd2
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in #9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
git-svn-id: https://develop.svn.wordpress.org/trunk@61032 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions

github-actionsBot commented Oct 21, 2025

Copy link
Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 61032
GitHub commit: cd95bd2

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

markjaquith pushed a commit to WordPress/WordPress that referenced this pull request Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
d3fe16a
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: http://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot pushed a commit to gilzow/wordpress-performance that referenced this pull request Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
e10f2f1
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: https://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@gziologziolo mentioned this pull request Oct 21, 2025
Closed
@gziolo

gziolo commented Oct 21, 2025

Copy link
Copy Markdown
MemberAuthor

I opened a follow up with the missing REST API controller for Ability Categories:

@gziolo
gziolo deleted the try/abilities-api branch October 22, 2025 14:01
This was referenced Oct 23, 2025
Open
Closed
Merged
pento pushed a commit that referenced this pull request Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
f4a36c7
This was discussed in #9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in #10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
git-svn-id: https://develop.svn.wordpress.org/trunk@61067 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith pushed a commit to markjaquith/WordPress that referenced this pull request Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
d0c71b7
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: http://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot pushed a commit to platformsh/wordpress-performance that referenced this pull request Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
8716c27
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: https://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@jonathanbossengerjonathanbossenger mentioned this pull request Oct 30, 2025
Closed
@gziologziolo mentioned this pull request Nov 4, 2025
Closed
@chubes4chubes4 mentioned this pull request Jul 16, 2026
Closed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@westonruterwestonruterwestonruter left review comments
@aaronjorbinaaronjorbinaaronjorbin left review comments
@TimothyBJacobsTimothyBJacobsTimothyBJacobs requested changes
@felixarntzfelixarntzAwaiting requested review from felixarntz
+2 more reviewers
@JasonTheAdamsJasonTheAdamsJasonTheAdams left review comments
@justlevinejustlevinejustlevine left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

@gziologziolo

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

8 participants

@gziolo@aaronjorbin@JasonTheAdams@justlevine@karmatosed@TimothyBJacobs@westonruter@felixarntz
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
Abilities API: Implement server-side registry with REST API endpoints - #9410
Closed
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Closed
Abilities API: Implement server-side registry with REST API endpoints#9410
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Conversation
@gziolo
@gziologziolo
commented
Aug 8, 2025•

edited

Loading

Copy link


Copy Markdown

Member
Trac ticket: https://core.trac.wordpress.org/ticket/64098
Part of Building Blocks for WordPress AI.
The Abilities API transforms WordPress from a collection of isolated functions into a unified, discoverable system. By creating a central registry of capabilities, it allows AI agents, automation tools, and developers to understand and interact with everything WordPress can do – from CLI commands and REST API endpoints to custom logic and plugin functions.
Full proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.

Handbook page at https://make.wordpress.org/ai/handbook/projects/abilities-api/.

Documentation in https://github.com/WordPress/abilities-api/tree/trunk/docs.

Developed in https://github.com/WordPress/abilities-api.

Composer package: https://packagist.org/packages/wordpress/abilities-api.
This PR contains six incremental commits added at different times after syncing directly from https://github.com/WordPress/abilities-api without any modifications. The last update is from October 14th (9906821) and equals the state in the v0.3.0-rc release available for the Composer package.
TODO
Follow-ups
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.
@gziologziolo
self-assigned this
Aug 8, 2025
@gziologziolo
mentioned this pull request
Aug 8, 2025
 Merged

@github-actions
github-actionsBot
commented
Aug 8, 2025

Copy link


Copy Markdown

Test using WordPress Playground
The changes in this pull request can previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.
Some things to be aware of
  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    
it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.
Test this pull request with WordPress Playground.
@gziolo
gziolo
commented
Aug 13, 2025

Copy link


Copy Markdown

MemberAuthor
The changes landed in the Abilitis API plugin with WordPress/abilities-api#3.
@gziologziolo
mentioned this pull request
Aug 14, 2025

Closed

9 tasks
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f2a5ae1 to
f825e40CompareAugust 18, 2025 10:33
@gziologziolo
mentioned this pull request
Aug 18, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 26, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 27, 2025
 Merged

@gziologziolo
mentioned this pull request
Sep 8, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
0c1ee5e to
9e2c2ffCompareSeptember 29, 2025 12:52
@gziologziolo
mentioned this pull request
Sep 29, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
3bc83b6 to
8362bcbCompareOctober 1, 2025 07:54
@gziologziolo
mentioned this pull request
Oct 10, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
df786b2 to
d7b4f3dCompareOctober 14, 2025 14:14
@gziologziolo
mentioned this pull request
Oct 14, 2025
 Merged

@gziolo
gziolo
commented
Oct 15, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
Two weeks ago, I synced changes from v0.2.0 in Abilities API repository with fd7412b.
Yesterday, I synced changes from v0.3.0-rc in Abilities API repository with 9906821.
@gziologziolo
changed the title
Abilities API: Implement server-side registryAbilities API: Implement server-side registry with REST API endpointsOct 15, 2025
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f9a8f24 to
d35222fCompareOctober 15, 2025 20:28
gzioloand others
added 9 commits
October 21, 2025 14:37
@gziolo
Fix bug in the permission check for ability in REST API run controller
1e54797
@gziolo
Improve handling for init hooks related to abilities and their catego…
57d8eda
…ries
@gziolo@aaronjorbin
Apply suggestions from code review
6cb5d7c
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@aaronjorbin
Update src/wp-includes/abilities-api/class-wp-ability.php
7f68dd9
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@TimothyBJacobs
Apply suggestions from code review
b36ea85
Co-authored-by: Timothy Jacobs <timothy@ironbounddesigns.com>
@gziolo
Rename REST routes and controllers
e124094
@gziolo
Enforce init hook before using ability related registries
1dec6a7
@gziolo
Increase testing code coverage for required init action check in ab…
2dbde17
…ility categories registry
@gziolo
Promote validate_input to public method and refactor usage
bcc6ff9
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
9939e36 to
3d2c27aCompareOctober 21, 2025 12:50
pento pushed a commit
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
cd95bd2
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in #9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
git-svn-id: https://develop.svn.wordpress.org/trunk@61032 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions
github-actionsBot
commented
Oct 21, 2025

Copy link


Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.
SVN changeset: 61032

GitHub commit: cd95bd2
This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.
markjaquith pushed a commit
to WordPress/WordPress
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
d3fe16a
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: http://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to gilzow/wordpress-performance
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
e10f2f1
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: https://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@gziologziolo
mentioned this pull request
Oct 21, 2025
 Closed

@gziolo
gziolo
commented
Oct 21, 2025

Copy link


Copy Markdown

MemberAuthor
I opened a follow up with the missing REST API controller for Ability Categories:
@gziolo
gziolo
deleted the

try/abilities-api

branch
October 22, 2025 14:01

This was referenced Oct 23, 2025
 Open


Closed

 Merged

pento pushed a commit
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
f4a36c7
This was discussed in #9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in #10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
git-svn-id: https://develop.svn.wordpress.org/trunk@61067 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
d0c71b7
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: http://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to platformsh/wordpress-performance
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
8716c27
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: https://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@jonathanbossengerjonathanbossenger
mentioned this pull request
Oct 30, 2025

Closed

@gziologziolo
mentioned this pull request
Nov 4, 2025
 Closed

@chubes4chubes4
mentioned this pull request
Jul 16, 2026
 Closed

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@westonruterwestonruterwestonruter left review comments
@aaronjorbinaaronjorbinaaronjorbin left review comments
@TimothyBJacobsTimothyBJacobsTimothyBJacobs requested changes
@felixarntzfelixarntzAwaiting requested review from felixarntz

+2 more reviewers

@JasonTheAdamsJasonTheAdamsJasonTheAdams left review comments
@justlevinejustlevinejustlevine left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

@gziologziolo

Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

8 participants

@gziolo@aaronjorbin@JasonTheAdams@justlevine@karmatosed@TimothyBJacobs@westonruter@felixarntz

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Abilities API: Implement server-side registry with REST API endpoints - #9410
Closed
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Closed
Abilities API: Implement server-side registry with REST API endpoints#9410
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Conversation
@gziolo
@gziologziolo
commented
Aug 8, 2025•

edited

Loading

Copy link


Copy Markdown

Member
Trac ticket: https://core.trac.wordpress.org/ticket/64098
Part of Building Blocks for WordPress AI.
The Abilities API transforms WordPress from a collection of isolated functions into a unified, discoverable system. By creating a central registry of capabilities, it allows AI agents, automation tools, and developers to understand and interact with everything WordPress can do – from CLI commands and REST API endpoints to custom logic and plugin functions.
Full proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.

Handbook page at https://make.wordpress.org/ai/handbook/projects/abilities-api/.

Documentation in https://github.com/WordPress/abilities-api/tree/trunk/docs.

Developed in https://github.com/WordPress/abilities-api.

Composer package: https://packagist.org/packages/wordpress/abilities-api.
This PR contains six incremental commits added at different times after syncing directly from https://github.com/WordPress/abilities-api without any modifications. The last update is from October 14th (9906821) and equals the state in the v0.3.0-rc release available for the Composer package.
TODO
Follow-ups
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.
@gziologziolo
self-assigned this
Aug 8, 2025
@gziologziolo
mentioned this pull request
Aug 8, 2025
 Merged

@github-actions
github-actionsBot
commented
Aug 8, 2025

Copy link


Copy Markdown

Test using WordPress Playground
The changes in this pull request can previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.
Some things to be aware of
  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    
it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.
Test this pull request with WordPress Playground.
@gziolo
gziolo
commented
Aug 13, 2025

Copy link


Copy Markdown

MemberAuthor
The changes landed in the Abilitis API plugin with WordPress/abilities-api#3.
@gziologziolo
mentioned this pull request
Aug 14, 2025

Closed

9 tasks
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f2a5ae1 to
f825e40CompareAugust 18, 2025 10:33
@gziologziolo
mentioned this pull request
Aug 18, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 26, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 27, 2025
 Merged

@gziologziolo
mentioned this pull request
Sep 8, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
0c1ee5e to
9e2c2ffCompareSeptember 29, 2025 12:52
@gziologziolo
mentioned this pull request
Sep 29, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
3bc83b6 to
8362bcbCompareOctober 1, 2025 07:54
@gziologziolo
mentioned this pull request
Oct 10, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
df786b2 to
d7b4f3dCompareOctober 14, 2025 14:14
@gziologziolo
mentioned this pull request
Oct 14, 2025
 Merged

@gziolo
gziolo
commented
Oct 15, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
Two weeks ago, I synced changes from v0.2.0 in Abilities API repository with fd7412b.
Yesterday, I synced changes from v0.3.0-rc in Abilities API repository with 9906821.
@gziologziolo
changed the title
Abilities API: Implement server-side registryAbilities API: Implement server-side registry with REST API endpointsOct 15, 2025
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f9a8f24 to
d35222fCompareOctober 15, 2025 20:28
gzioloand others
added 9 commits
October 21, 2025 14:37
@gziolo
Fix bug in the permission check for ability in REST API run controller
1e54797
@gziolo
Improve handling for init hooks related to abilities and their catego…
57d8eda
…ries
@gziolo@aaronjorbin
Apply suggestions from code review
6cb5d7c
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@aaronjorbin
Update src/wp-includes/abilities-api/class-wp-ability.php
7f68dd9
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@TimothyBJacobs
Apply suggestions from code review
b36ea85
Co-authored-by: Timothy Jacobs <timothy@ironbounddesigns.com>
@gziolo
Rename REST routes and controllers
e124094
@gziolo
Enforce init hook before using ability related registries
1dec6a7
@gziolo
Increase testing code coverage for required init action check in ab…
2dbde17
…ility categories registry
@gziolo
Promote validate_input to public method and refactor usage
bcc6ff9
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
9939e36 to
3d2c27aCompareOctober 21, 2025 12:50
pento pushed a commit
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
cd95bd2
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in #9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
git-svn-id: https://develop.svn.wordpress.org/trunk@61032 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions
github-actionsBot
commented
Oct 21, 2025

Copy link


Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.
SVN changeset: 61032

GitHub commit: cd95bd2
This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.
markjaquith pushed a commit
to WordPress/WordPress
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
d3fe16a
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: http://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to gilzow/wordpress-performance
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
e10f2f1
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: https://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@gziologziolo
mentioned this pull request
Oct 21, 2025
 Closed

@gziolo
gziolo
commented
Oct 21, 2025

Copy link


Copy Markdown

MemberAuthor
I opened a follow up with the missing REST API controller for Ability Categories:
@gziolo
gziolo
deleted the

try/abilities-api

branch
October 22, 2025 14:01

This was referenced Oct 23, 2025
 Open


Closed

 Merged

pento pushed a commit
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
f4a36c7
This was discussed in #9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in #10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
git-svn-id: https://develop.svn.wordpress.org/trunk@61067 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
d0c71b7
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: http://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to platformsh/wordpress-performance
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
8716c27
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: https://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@jonathanbossengerjonathanbossenger
mentioned this pull request
Oct 30, 2025

Closed

@gziologziolo
mentioned this pull request
Nov 4, 2025
 Closed

@chubes4chubes4
mentioned this pull request
Jul 16, 2026
 Closed

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@westonruterwestonruterwestonruter left review comments
@aaronjorbinaaronjorbinaaronjorbin left review comments
@TimothyBJacobsTimothyBJacobsTimothyBJacobs requested changes
@felixarntzfelixarntzAwaiting requested review from felixarntz

+2 more reviewers

@JasonTheAdamsJasonTheAdamsJasonTheAdams left review comments
@justlevinejustlevinejustlevine left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

@gziologziolo

Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

8 participants

@gziolo@aaronjorbin@JasonTheAdams@justlevine@karmatosed@TimothyBJacobs@westonruter@felixarntz

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Abilities API: Implement server-side registry with REST API endpoints - #9410
Closed
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Closed
Abilities API: Implement server-side registry with REST API endpoints#9410
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Conversation
@gziolo
@gziologziolo
commented
Aug 8, 2025•

edited

Loading

Copy link


Copy Markdown

Member
Trac ticket: https://core.trac.wordpress.org/ticket/64098
Part of Building Blocks for WordPress AI.
The Abilities API transforms WordPress from a collection of isolated functions into a unified, discoverable system. By creating a central registry of capabilities, it allows AI agents, automation tools, and developers to understand and interact with everything WordPress can do – from CLI commands and REST API endpoints to custom logic and plugin functions.
Full proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.

Handbook page at https://make.wordpress.org/ai/handbook/projects/abilities-api/.

Documentation in https://github.com/WordPress/abilities-api/tree/trunk/docs.

Developed in https://github.com/WordPress/abilities-api.

Composer package: https://packagist.org/packages/wordpress/abilities-api.
This PR contains six incremental commits added at different times after syncing directly from https://github.com/WordPress/abilities-api without any modifications. The last update is from October 14th (9906821) and equals the state in the v0.3.0-rc release available for the Composer package.
TODO
Follow-ups
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.
@gziologziolo
self-assigned this
Aug 8, 2025
@gziologziolo
mentioned this pull request
Aug 8, 2025
 Merged

@github-actions
github-actionsBot
commented
Aug 8, 2025

Copy link


Copy Markdown

Test using WordPress Playground
The changes in this pull request can previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.
Some things to be aware of
  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    
it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.
Test this pull request with WordPress Playground.
@gziolo
gziolo
commented
Aug 13, 2025

Copy link


Copy Markdown

MemberAuthor
The changes landed in the Abilitis API plugin with WordPress/abilities-api#3.
@gziologziolo
mentioned this pull request
Aug 14, 2025

Closed

9 tasks
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f2a5ae1 to
f825e40CompareAugust 18, 2025 10:33
@gziologziolo
mentioned this pull request
Aug 18, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 26, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 27, 2025
 Merged

@gziologziolo
mentioned this pull request
Sep 8, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
0c1ee5e to
9e2c2ffCompareSeptember 29, 2025 12:52
@gziologziolo
mentioned this pull request
Sep 29, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
3bc83b6 to
8362bcbCompareOctober 1, 2025 07:54
@gziologziolo
mentioned this pull request
Oct 10, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
df786b2 to
d7b4f3dCompareOctober 14, 2025 14:14
@gziologziolo
mentioned this pull request
Oct 14, 2025
 Merged

@gziolo
gziolo
commented
Oct 15, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
Two weeks ago, I synced changes from v0.2.0 in Abilities API repository with fd7412b.
Yesterday, I synced changes from v0.3.0-rc in Abilities API repository with 9906821.
@gziologziolo
changed the title
Abilities API: Implement server-side registryAbilities API: Implement server-side registry with REST API endpointsOct 15, 2025
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f9a8f24 to
d35222fCompareOctober 15, 2025 20:28
gzioloand others
added 9 commits
October 21, 2025 14:37
@gziolo
Fix bug in the permission check for ability in REST API run controller
1e54797
@gziolo
Improve handling for init hooks related to abilities and their catego…
57d8eda
…ries
@gziolo@aaronjorbin
Apply suggestions from code review
6cb5d7c
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@aaronjorbin
Update src/wp-includes/abilities-api/class-wp-ability.php
7f68dd9
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@TimothyBJacobs
Apply suggestions from code review
b36ea85
Co-authored-by: Timothy Jacobs <timothy@ironbounddesigns.com>
@gziolo
Rename REST routes and controllers
e124094
@gziolo
Enforce init hook before using ability related registries
1dec6a7
@gziolo
Increase testing code coverage for required init action check in ab…
2dbde17
…ility categories registry
@gziolo
Promote validate_input to public method and refactor usage
bcc6ff9
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
9939e36 to
3d2c27aCompareOctober 21, 2025 12:50
pento pushed a commit
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
cd95bd2
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in #9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
git-svn-id: https://develop.svn.wordpress.org/trunk@61032 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions
github-actionsBot
commented
Oct 21, 2025

Copy link


Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.
SVN changeset: 61032

GitHub commit: cd95bd2
This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.
markjaquith pushed a commit
to WordPress/WordPress
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
d3fe16a
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: http://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to gilzow/wordpress-performance
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
e10f2f1
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: https://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@gziologziolo
mentioned this pull request
Oct 21, 2025
 Closed

@gziolo
gziolo
commented
Oct 21, 2025

Copy link


Copy Markdown

MemberAuthor
I opened a follow up with the missing REST API controller for Ability Categories:
@gziolo
gziolo
deleted the

try/abilities-api

branch
October 22, 2025 14:01

This was referenced Oct 23, 2025
 Open


Closed

 Merged

pento pushed a commit
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
f4a36c7
This was discussed in #9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in #10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
git-svn-id: https://develop.svn.wordpress.org/trunk@61067 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
d0c71b7
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: http://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to platformsh/wordpress-performance
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
8716c27
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: https://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@jonathanbossengerjonathanbossenger
mentioned this pull request
Oct 30, 2025

Closed

@gziologziolo
mentioned this pull request
Nov 4, 2025
 Closed

@chubes4chubes4
mentioned this pull request
Jul 16, 2026
 Closed

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@westonruterwestonruterwestonruter left review comments
@aaronjorbinaaronjorbinaaronjorbin left review comments
@TimothyBJacobsTimothyBJacobsTimothyBJacobs requested changes
@felixarntzfelixarntzAwaiting requested review from felixarntz

+2 more reviewers

@JasonTheAdamsJasonTheAdamsJasonTheAdams left review comments
@justlevinejustlevinejustlevine left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

@gziologziolo

Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

8 participants

@gziolo@aaronjorbin@JasonTheAdams@justlevine@karmatosed@TimothyBJacobs@westonruter@felixarntz

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
Abilities API: Implement server-side registry with REST API endpoints - #9410
Closed
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Closed
Abilities API: Implement server-side registry with REST API endpoints#9410
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Conversation
@gziolo
@gziologziolo
commented
Aug 8, 2025•

edited

Loading

Copy link


Copy Markdown

Member
Trac ticket: https://core.trac.wordpress.org/ticket/64098
Part of Building Blocks for WordPress AI.
The Abilities API transforms WordPress from a collection of isolated functions into a unified, discoverable system. By creating a central registry of capabilities, it allows AI agents, automation tools, and developers to understand and interact with everything WordPress can do – from CLI commands and REST API endpoints to custom logic and plugin functions.
Full proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.

Handbook page at https://make.wordpress.org/ai/handbook/projects/abilities-api/.

Documentation in https://github.com/WordPress/abilities-api/tree/trunk/docs.

Developed in https://github.com/WordPress/abilities-api.

Composer package: https://packagist.org/packages/wordpress/abilities-api.
This PR contains six incremental commits added at different times after syncing directly from https://github.com/WordPress/abilities-api without any modifications. The last update is from October 14th (9906821) and equals the state in the v0.3.0-rc release available for the Composer package.
TODO
Follow-ups
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.
@gziologziolo
self-assigned this
Aug 8, 2025
@gziologziolo
mentioned this pull request
Aug 8, 2025
 Merged

@github-actions
github-actionsBot
commented
Aug 8, 2025

Copy link


Copy Markdown

Test using WordPress Playground
The changes in this pull request can previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.
Some things to be aware of
  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    
it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.
Test this pull request with WordPress Playground.
@gziolo
gziolo
commented
Aug 13, 2025

Copy link


Copy Markdown

MemberAuthor
The changes landed in the Abilitis API plugin with WordPress/abilities-api#3.
@gziologziolo
mentioned this pull request
Aug 14, 2025

Closed

9 tasks
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f2a5ae1 to
f825e40CompareAugust 18, 2025 10:33
@gziologziolo
mentioned this pull request
Aug 18, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 26, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 27, 2025
 Merged

@gziologziolo
mentioned this pull request
Sep 8, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
0c1ee5e to
9e2c2ffCompareSeptember 29, 2025 12:52
@gziologziolo
mentioned this pull request
Sep 29, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
3bc83b6 to
8362bcbCompareOctober 1, 2025 07:54
@gziologziolo
mentioned this pull request
Oct 10, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
df786b2 to
d7b4f3dCompareOctober 14, 2025 14:14
@gziologziolo
mentioned this pull request
Oct 14, 2025
 Merged

@gziolo
gziolo
commented
Oct 15, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
Two weeks ago, I synced changes from v0.2.0 in Abilities API repository with fd7412b.
Yesterday, I synced changes from v0.3.0-rc in Abilities API repository with 9906821.
@gziologziolo
changed the title
Abilities API: Implement server-side registryAbilities API: Implement server-side registry with REST API endpointsOct 15, 2025
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f9a8f24 to
d35222fCompareOctober 15, 2025 20:28
gzioloand others
added 9 commits
October 21, 2025 14:37
@gziolo
Fix bug in the permission check for ability in REST API run controller
1e54797
@gziolo
Improve handling for init hooks related to abilities and their catego…
57d8eda
…ries
@gziolo@aaronjorbin
Apply suggestions from code review
6cb5d7c
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@aaronjorbin
Update src/wp-includes/abilities-api/class-wp-ability.php
7f68dd9
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@TimothyBJacobs
Apply suggestions from code review
b36ea85
Co-authored-by: Timothy Jacobs <timothy@ironbounddesigns.com>
@gziolo
Rename REST routes and controllers
e124094
@gziolo
Enforce init hook before using ability related registries
1dec6a7
@gziolo
Increase testing code coverage for required init action check in ab…
2dbde17
…ility categories registry
@gziolo
Promote validate_input to public method and refactor usage
bcc6ff9
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
9939e36 to
3d2c27aCompareOctober 21, 2025 12:50
pento pushed a commit
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
cd95bd2
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in #9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
git-svn-id: https://develop.svn.wordpress.org/trunk@61032 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions
github-actionsBot
commented
Oct 21, 2025

Copy link


Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.
SVN changeset: 61032

GitHub commit: cd95bd2
This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.
markjaquith pushed a commit
to WordPress/WordPress
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
d3fe16a
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: http://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to gilzow/wordpress-performance
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
e10f2f1
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: https://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@gziologziolo
mentioned this pull request
Oct 21, 2025
 Closed

@gziolo
gziolo
commented
Oct 21, 2025

Copy link


Copy Markdown

MemberAuthor
I opened a follow up with the missing REST API controller for Ability Categories:
@gziolo
gziolo
deleted the

try/abilities-api

branch
October 22, 2025 14:01

This was referenced Oct 23, 2025
 Open


Closed

 Merged

pento pushed a commit
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
f4a36c7
This was discussed in #9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in #10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
git-svn-id: https://develop.svn.wordpress.org/trunk@61067 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
d0c71b7
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: http://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to platformsh/wordpress-performance
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
8716c27
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: https://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@jonathanbossengerjonathanbossenger
mentioned this pull request
Oct 30, 2025

Closed

@gziologziolo
mentioned this pull request
Nov 4, 2025
 Closed

@chubes4chubes4
mentioned this pull request
Jul 16, 2026
 Closed

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@westonruterwestonruterwestonruter left review comments
@aaronjorbinaaronjorbinaaronjorbin left review comments
@TimothyBJacobsTimothyBJacobsTimothyBJacobs requested changes
@felixarntzfelixarntzAwaiting requested review from felixarntz

+2 more reviewers

@JasonTheAdamsJasonTheAdamsJasonTheAdams left review comments
@justlevinejustlevinejustlevine left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

@gziologziolo

Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

8 participants

@gziolo@aaronjorbin@JasonTheAdams@justlevine@karmatosed@TimothyBJacobs@westonruter@felixarntz

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Abilities API: Implement server-side registry with REST API endpoints - #9410
Closed
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Closed
Abilities API: Implement server-side registry with REST API endpoints#9410
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Conversation
@gziolo
@gziologziolo
commented
Aug 8, 2025•

edited

Loading

Copy link


Copy Markdown

Member
Trac ticket: https://core.trac.wordpress.org/ticket/64098
Part of Building Blocks for WordPress AI.
The Abilities API transforms WordPress from a collection of isolated functions into a unified, discoverable system. By creating a central registry of capabilities, it allows AI agents, automation tools, and developers to understand and interact with everything WordPress can do – from CLI commands and REST API endpoints to custom logic and plugin functions.
Full proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.

Handbook page at https://make.wordpress.org/ai/handbook/projects/abilities-api/.

Documentation in https://github.com/WordPress/abilities-api/tree/trunk/docs.

Developed in https://github.com/WordPress/abilities-api.

Composer package: https://packagist.org/packages/wordpress/abilities-api.
This PR contains six incremental commits added at different times after syncing directly from https://github.com/WordPress/abilities-api without any modifications. The last update is from October 14th (9906821) and equals the state in the v0.3.0-rc release available for the Composer package.
TODO
Follow-ups
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.
@gziologziolo
self-assigned this
Aug 8, 2025
@gziologziolo
mentioned this pull request
Aug 8, 2025
 Merged

@github-actions
github-actionsBot
commented
Aug 8, 2025

Copy link


Copy Markdown

Test using WordPress Playground
The changes in this pull request can previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.
Some things to be aware of
  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    
it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.
Test this pull request with WordPress Playground.
@gziolo
gziolo
commented
Aug 13, 2025

Copy link


Copy Markdown

MemberAuthor
The changes landed in the Abilitis API plugin with WordPress/abilities-api#3.
@gziologziolo
mentioned this pull request
Aug 14, 2025

Closed

9 tasks
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f2a5ae1 to
f825e40CompareAugust 18, 2025 10:33
@gziologziolo
mentioned this pull request
Aug 18, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 26, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 27, 2025
 Merged

@gziologziolo
mentioned this pull request
Sep 8, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
0c1ee5e to
9e2c2ffCompareSeptember 29, 2025 12:52
@gziologziolo
mentioned this pull request
Sep 29, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
3bc83b6 to
8362bcbCompareOctober 1, 2025 07:54
@gziologziolo
mentioned this pull request
Oct 10, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
df786b2 to
d7b4f3dCompareOctober 14, 2025 14:14
@gziologziolo
mentioned this pull request
Oct 14, 2025
 Merged

@gziolo
gziolo
commented
Oct 15, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
Two weeks ago, I synced changes from v0.2.0 in Abilities API repository with fd7412b.
Yesterday, I synced changes from v0.3.0-rc in Abilities API repository with 9906821.
@gziologziolo
changed the title
Abilities API: Implement server-side registryAbilities API: Implement server-side registry with REST API endpointsOct 15, 2025
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f9a8f24 to
d35222fCompareOctober 15, 2025 20:28
gzioloand others
added 9 commits
October 21, 2025 14:37
@gziolo
Fix bug in the permission check for ability in REST API run controller
1e54797
@gziolo
Improve handling for init hooks related to abilities and their catego…
57d8eda
…ries
@gziolo@aaronjorbin
Apply suggestions from code review
6cb5d7c
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@aaronjorbin
Update src/wp-includes/abilities-api/class-wp-ability.php
7f68dd9
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@TimothyBJacobs
Apply suggestions from code review
b36ea85
Co-authored-by: Timothy Jacobs <timothy@ironbounddesigns.com>
@gziolo
Rename REST routes and controllers
e124094
@gziolo
Enforce init hook before using ability related registries
1dec6a7
@gziolo
Increase testing code coverage for required init action check in ab…
2dbde17
…ility categories registry
@gziolo
Promote validate_input to public method and refactor usage
bcc6ff9
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
9939e36 to
3d2c27aCompareOctober 21, 2025 12:50
pento pushed a commit
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
cd95bd2
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in #9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
git-svn-id: https://develop.svn.wordpress.org/trunk@61032 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions
github-actionsBot
commented
Oct 21, 2025

Copy link


Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.
SVN changeset: 61032

GitHub commit: cd95bd2
This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.
markjaquith pushed a commit
to WordPress/WordPress
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
d3fe16a
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: http://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to gilzow/wordpress-performance
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
e10f2f1
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: https://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@gziologziolo
mentioned this pull request
Oct 21, 2025
 Closed

@gziolo
gziolo
commented
Oct 21, 2025

Copy link


Copy Markdown

MemberAuthor
I opened a follow up with the missing REST API controller for Ability Categories:
@gziolo
gziolo
deleted the

try/abilities-api

branch
October 22, 2025 14:01

This was referenced Oct 23, 2025
 Open


Closed

 Merged

pento pushed a commit
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
f4a36c7
This was discussed in #9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in #10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
git-svn-id: https://develop.svn.wordpress.org/trunk@61067 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
d0c71b7
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: http://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to platformsh/wordpress-performance
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
8716c27
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: https://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@jonathanbossengerjonathanbossenger
mentioned this pull request
Oct 30, 2025

Closed

@gziologziolo
mentioned this pull request
Nov 4, 2025
 Closed

@chubes4chubes4
mentioned this pull request
Jul 16, 2026
 Closed

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@westonruterwestonruterwestonruter left review comments
@aaronjorbinaaronjorbinaaronjorbin left review comments
@TimothyBJacobsTimothyBJacobsTimothyBJacobs requested changes
@felixarntzfelixarntzAwaiting requested review from felixarntz

+2 more reviewers

@JasonTheAdamsJasonTheAdamsJasonTheAdams left review comments
@justlevinejustlevinejustlevine left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

@gziologziolo

Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

8 participants

@gziolo@aaronjorbin@JasonTheAdams@justlevine@karmatosed@TimothyBJacobs@westonruter@felixarntz

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Abilities API: Implement server-side registry with REST API endpoints - #9410
Closed
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Closed
Abilities API: Implement server-side registry with REST API endpoints#9410
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Conversation
@gziolo
@gziologziolo
commented
Aug 8, 2025•

edited

Loading

Copy link


Copy Markdown

Member
Trac ticket: https://core.trac.wordpress.org/ticket/64098
Part of Building Blocks for WordPress AI.
The Abilities API transforms WordPress from a collection of isolated functions into a unified, discoverable system. By creating a central registry of capabilities, it allows AI agents, automation tools, and developers to understand and interact with everything WordPress can do – from CLI commands and REST API endpoints to custom logic and plugin functions.
Full proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.

Handbook page at https://make.wordpress.org/ai/handbook/projects/abilities-api/.

Documentation in https://github.com/WordPress/abilities-api/tree/trunk/docs.

Developed in https://github.com/WordPress/abilities-api.

Composer package: https://packagist.org/packages/wordpress/abilities-api.
This PR contains six incremental commits added at different times after syncing directly from https://github.com/WordPress/abilities-api without any modifications. The last update is from October 14th (9906821) and equals the state in the v0.3.0-rc release available for the Composer package.
TODO
Follow-ups
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.
@gziologziolo
self-assigned this
Aug 8, 2025
@gziologziolo
mentioned this pull request
Aug 8, 2025
 Merged

@github-actions
github-actionsBot
commented
Aug 8, 2025

Copy link


Copy Markdown

Test using WordPress Playground
The changes in this pull request can previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.
Some things to be aware of
  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    
it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.
Test this pull request with WordPress Playground.
@gziolo
gziolo
commented
Aug 13, 2025

Copy link


Copy Markdown

MemberAuthor
The changes landed in the Abilitis API plugin with WordPress/abilities-api#3.
@gziologziolo
mentioned this pull request
Aug 14, 2025

Closed

9 tasks
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f2a5ae1 to
f825e40CompareAugust 18, 2025 10:33
@gziologziolo
mentioned this pull request
Aug 18, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 26, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 27, 2025
 Merged

@gziologziolo
mentioned this pull request
Sep 8, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
0c1ee5e to
9e2c2ffCompareSeptember 29, 2025 12:52
@gziologziolo
mentioned this pull request
Sep 29, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
3bc83b6 to
8362bcbCompareOctober 1, 2025 07:54
@gziologziolo
mentioned this pull request
Oct 10, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
df786b2 to
d7b4f3dCompareOctober 14, 2025 14:14
@gziologziolo
mentioned this pull request
Oct 14, 2025
 Merged

@gziolo
gziolo
commented
Oct 15, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
Two weeks ago, I synced changes from v0.2.0 in Abilities API repository with fd7412b.
Yesterday, I synced changes from v0.3.0-rc in Abilities API repository with 9906821.
@gziologziolo
changed the title
Abilities API: Implement server-side registryAbilities API: Implement server-side registry with REST API endpointsOct 15, 2025
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f9a8f24 to
d35222fCompareOctober 15, 2025 20:28
gzioloand others
added 9 commits
October 21, 2025 14:37
@gziolo
Fix bug in the permission check for ability in REST API run controller
1e54797
@gziolo
Improve handling for init hooks related to abilities and their catego…
57d8eda
…ries
@gziolo@aaronjorbin
Apply suggestions from code review
6cb5d7c
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@aaronjorbin
Update src/wp-includes/abilities-api/class-wp-ability.php
7f68dd9
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@TimothyBJacobs
Apply suggestions from code review
b36ea85
Co-authored-by: Timothy Jacobs <timothy@ironbounddesigns.com>
@gziolo
Rename REST routes and controllers
e124094
@gziolo
Enforce init hook before using ability related registries
1dec6a7
@gziolo
Increase testing code coverage for required init action check in ab…
2dbde17
…ility categories registry
@gziolo
Promote validate_input to public method and refactor usage
bcc6ff9
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
9939e36 to
3d2c27aCompareOctober 21, 2025 12:50
pento pushed a commit
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
cd95bd2
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in #9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
git-svn-id: https://develop.svn.wordpress.org/trunk@61032 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions
github-actionsBot
commented
Oct 21, 2025

Copy link


Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.
SVN changeset: 61032

GitHub commit: cd95bd2
This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.
markjaquith pushed a commit
to WordPress/WordPress
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
d3fe16a
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: http://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to gilzow/wordpress-performance
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
e10f2f1
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: https://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@gziologziolo
mentioned this pull request
Oct 21, 2025
 Closed

@gziolo
gziolo
commented
Oct 21, 2025

Copy link


Copy Markdown

MemberAuthor
I opened a follow up with the missing REST API controller for Ability Categories:
@gziolo
gziolo
deleted the

try/abilities-api

branch
October 22, 2025 14:01

This was referenced Oct 23, 2025
 Open


Closed

 Merged

pento pushed a commit
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
f4a36c7
This was discussed in #9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in #10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
git-svn-id: https://develop.svn.wordpress.org/trunk@61067 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
d0c71b7
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: http://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to platformsh/wordpress-performance
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
8716c27
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: https://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@jonathanbossengerjonathanbossenger
mentioned this pull request
Oct 30, 2025

Closed

@gziologziolo
mentioned this pull request
Nov 4, 2025
 Closed

@chubes4chubes4
mentioned this pull request
Jul 16, 2026
 Closed

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@westonruterwestonruterwestonruter left review comments
@aaronjorbinaaronjorbinaaronjorbin left review comments
@TimothyBJacobsTimothyBJacobsTimothyBJacobs requested changes
@felixarntzfelixarntzAwaiting requested review from felixarntz

+2 more reviewers

@JasonTheAdamsJasonTheAdamsJasonTheAdams left review comments
@justlevinejustlevinejustlevine left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

@gziologziolo

Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

8 participants

@gziolo@aaronjorbin@JasonTheAdams@justlevine@karmatosed@TimothyBJacobs@westonruter@felixarntz

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
Abilities API: Implement server-side registry with REST API endpoints - #9410
Closed
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Closed
Abilities API: Implement server-side registry with REST API endpoints#9410
gziolo wants to merge 31 commits into
WordPress:trunkfrom 
gziolo:try/abilities-api
Conversation
@gziolo
@gziologziolo
commented
Aug 8, 2025•

edited

Loading

Copy link


Copy Markdown

Member
Trac ticket: https://core.trac.wordpress.org/ticket/64098
Part of Building Blocks for WordPress AI.
The Abilities API transforms WordPress from a collection of isolated functions into a unified, discoverable system. By creating a central registry of capabilities, it allows AI agents, automation tools, and developers to understand and interact with everything WordPress can do – from CLI commands and REST API endpoints to custom logic and plugin functions.
Full proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.

Handbook page at https://make.wordpress.org/ai/handbook/projects/abilities-api/.

Documentation in https://github.com/WordPress/abilities-api/tree/trunk/docs.

Developed in https://github.com/WordPress/abilities-api.

Composer package: https://packagist.org/packages/wordpress/abilities-api.
This PR contains six incremental commits added at different times after syncing directly from https://github.com/WordPress/abilities-api without any modifications. The last update is from October 14th (9906821) and equals the state in the v0.3.0-rc release available for the Composer package.
TODO
Follow-ups
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.
@gziologziolo
self-assigned this
Aug 8, 2025
@gziologziolo
mentioned this pull request
Aug 8, 2025
 Merged

@github-actions
github-actionsBot
commented
Aug 8, 2025

Copy link


Copy Markdown

Test using WordPress Playground
The changes in this pull request can previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.
Some things to be aware of
  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    
it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.
Test this pull request with WordPress Playground.
@gziolo
gziolo
commented
Aug 13, 2025

Copy link


Copy Markdown

MemberAuthor
The changes landed in the Abilitis API plugin with WordPress/abilities-api#3.
@gziologziolo
mentioned this pull request
Aug 14, 2025

Closed

9 tasks
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f2a5ae1 to
f825e40CompareAugust 18, 2025 10:33
@gziologziolo
mentioned this pull request
Aug 18, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 26, 2025
 Merged

@gziologziolo
mentioned this pull request
Aug 27, 2025
 Merged

@gziologziolo
mentioned this pull request
Sep 8, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
0c1ee5e to
9e2c2ffCompareSeptember 29, 2025 12:52
@gziologziolo
mentioned this pull request
Sep 29, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
3bc83b6 to
8362bcbCompareOctober 1, 2025 07:54
@gziologziolo
mentioned this pull request
Oct 10, 2025
 Merged

@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
df786b2 to
d7b4f3dCompareOctober 14, 2025 14:14
@gziologziolo
mentioned this pull request
Oct 14, 2025
 Merged

@gziolo
gziolo
commented
Oct 15, 2025•

edited

Loading

Copy link


Copy Markdown

MemberAuthor
Two weeks ago, I synced changes from v0.2.0 in Abilities API repository with fd7412b.
Yesterday, I synced changes from v0.3.0-rc in Abilities API repository with 9906821.
@gziologziolo
changed the title
Abilities API: Implement server-side registryAbilities API: Implement server-side registry with REST API endpointsOct 15, 2025
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
f9a8f24 to
d35222fCompareOctober 15, 2025 20:28
gzioloand others
added 9 commits
October 21, 2025 14:37
@gziolo
Fix bug in the permission check for ability in REST API run controller
1e54797
@gziolo
Improve handling for init hooks related to abilities and their catego…
57d8eda
…ries
@gziolo@aaronjorbin
Apply suggestions from code review
6cb5d7c
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@aaronjorbin
Update src/wp-includes/abilities-api/class-wp-ability.php
7f68dd9
Co-authored-by: Aaron Jorbin <aaronjorbin@users.noreply.github.com>
@gziolo@TimothyBJacobs
Apply suggestions from code review
b36ea85
Co-authored-by: Timothy Jacobs <timothy@ironbounddesigns.com>
@gziolo
Rename REST routes and controllers
e124094
@gziolo
Enforce init hook before using ability related registries
1dec6a7
@gziolo
Increase testing code coverage for required init action check in ab…
2dbde17
…ility categories registry
@gziolo
Promote validate_input to public method and refactor usage
bcc6ff9
@gziolo
gzioloforce-pushed
the
try/abilities-api
branch
2 times, most recently
from
9939e36 to
3d2c27aCompareOctober 21, 2025 12:50
pento pushed a commit
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
cd95bd2
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in #9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
git-svn-id: https://develop.svn.wordpress.org/trunk@61032 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions
github-actionsBot
commented
Oct 21, 2025

Copy link


Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.
SVN changeset: 61032

GitHub commit: cd95bd2
This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.
markjaquith pushed a commit
to WordPress/WordPress
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
d3fe16a
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: http://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to gilzow/wordpress-performance
that referenced
this pull request
Oct 21, 2025
@gziolo
Abilities API: Introduce server-side registry and REST API endpoints
e10f2f1
Feature proposal at https://make.wordpress.org/ai/2025/07/17/abilities-api/.
Project developed in https://github.com/WordPress/abilities-api.
Introduces a new Abilities API that allows WordPress plugins and themes to register and execute custom abilities with built-in permission checking, input/output validation via JSON Schema, and REST API integration.
## Public Functions
### Ability Management
- `wp_register_ability( string $name, array $args ): ?WP_Ability` - Registers a new ability (must be called on `wp_abilities_api_init` hook)
- `wp_unregister_ability( string $name ): ?WP_Ability` - Unregisters an ability
- `wp_has_ability( string $name ): bool` - Checks if an ability is registered
- `wp_get_ability( string $name ): ?WP_Ability` - Retrieves a registered ability
- `wp_get_abilities(): array` - Retrieves all registered abilities
### Ability Category Management
- `wp_register_ability_category( string $slug, array $args ): ?WP_Ability_Category` - Registers an ability category (must be called on `wp_abilities_api_categories_init` hook)
- `wp_unregister_ability_category( string $slug ): ?WP_Ability_Category` - Unregisters an ability category
- `wp_has_ability_category( string $slug ): bool` - Checks if an ability category is registered
- `wp_get_ability_category( string $slug ): ?WP_Ability_Category` - Retrieves a registered ability category
- `wp_get_ability_categories(): array` - Retrieves all registered ability categories
## Public Classes
- `WP_Ability` - Encapsulates ability properties and methods (execute, check_permission, validate_input, etc.)
- `WP_Ability_Category` - Encapsulates ability category properties
- `WP_Abilities_Registry` - Manages ability registration and lookup (private, accessed via functions)
- `WP_Ability_Categories_Registry` - Manages ability category registration (private, accessed via functions)
- `WP_REST_Abilities_V1_List_Controller` - REST controller for listing abilities
- `WP_REST_Abilities_V1_Run_Controller` - REST controller for executing abilities
## REST API Endpoints
### Namespace: `wp-abilities/v1`
#### List Abilities
- `GET /wp-abilities/v1/abilities` - Retrieve all registered abilities
- Query parameters: `page`, `per_page`, `category`
#### Get Single Ability
- `GET /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)` - Retrieve a specific ability by name
#### Execute Ability
- `GET|POST|DELETE /wp-abilities/v1/abilities/(?P<name>[a-zA-Z0-9\-\/]+)/run` - Execute an ability
- Supports multiple HTTP methods based on ability annotations
- Validates input against ability's input schema
- Validates output against ability's output schema
- Performs permission checks via ability's permission callback
## Hooks
### Actions
- `wp_abilities_api_categories_init` - Fired when ability categories registry is initialized (register categories here)
- `wp_abilities_api_init` - Fired when abilities registry is initialized (register abilities here)
- `wp_before_execute_ability` - Fired before an ability gets executed, after input validation and permissions check
- `wp_after_execute_ability` - Fires immediately after an ability finished executing
### Filters
- `wp_register_ability_category_args` - Filters ability category arguments before registration
- `wp_register_ability_args` - Filters ability arguments before registration
Developed in WordPress/wordpress-develop#9410.
Props gziolo, jorbin, justlevine, westonruter, jason_the_adams, flixos90, karmatosed, timothyblynjacobs.
Fixes #64098.
Built from https://develop.svn.wordpress.org/trunk@61032
git-svn-id: https://core.svn.wordpress.org/trunk@60368 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@gziologziolo
mentioned this pull request
Oct 21, 2025
 Closed

@gziolo
gziolo
commented
Oct 21, 2025

Copy link


Copy Markdown

MemberAuthor
I opened a follow up with the missing REST API controller for Ability Categories:
@gziolo
gziolo
deleted the

try/abilities-api

branch
October 22, 2025 14:01

This was referenced Oct 23, 2025
 Open


Closed

 Merged

pento pushed a commit
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
f4a36c7
This was discussed in #9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in #10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
git-svn-id: https://develop.svn.wordpress.org/trunk@61067 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
d0c71b7
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: http://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actionsBot
pushed a commit
to platformsh/wordpress-performance
that referenced
this pull request
Oct 27, 2025
@gziolo
Abilities API: Improve inline documentation
8716c27
This was discussed in WordPress/wordpress-develop#9410 and decided to defer until after beta1.
Fleshing out the phpdocs for the extender functions in https://core.trac.wordpress.org/browser/trunk/src/wp-includes/abilities-api.php should make it easier for people working with the abilities API
Developed in WordPress/wordpress-develop#10412.
Follw-up [61032].
Props jorbin, gziolo, mukesh27, jason_the_adams, westonruter.
Fixes #64134.
Built from https://develop.svn.wordpress.org/trunk@61067
git-svn-id: https://core.svn.wordpress.org/trunk@60403 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@jonathanbossengerjonathanbossenger
mentioned this pull request
Oct 30, 2025

Closed

@gziologziolo
mentioned this pull request
Nov 4, 2025
 Closed

@chubes4chubes4
mentioned this pull request
Jul 16, 2026
 Closed

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@westonruterwestonruterwestonruter left review comments
@aaronjorbinaaronjorbinaaronjorbin left review comments
@TimothyBJacobsTimothyBJacobsTimothyBJacobs requested changes
@felixarntzfelixarntzAwaiting requested review from felixarntz

+2 more reviewers

@JasonTheAdamsJasonTheAdamsJasonTheAdams left review comments
@justlevinejustlevinejustlevine left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

@gziologziolo

Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

8 participants

@gziolo@aaronjorbin@JasonTheAdams@justlevine@karmatosed@TimothyBJacobs@westonruter@felixarntz