Core Abilities: Export initialization promise as ready#77254
Merged
westonruter merged 2 commits intotrunkfrom Apr 15, 2026
Merged
Core Abilities: Export initialization promise as ready#77254westonruter merged 2 commits intotrunkfrom
ready#77254westonruter merged 2 commits intotrunkfrom
Conversation
Consumers of `@wordpress/core-abilities` had no way to know when the server-side categories and abilities had finished loading into the client store, since `initialize()` was called fire-and-forget. Export the returned promise as `ready` so callers can `await` it before calling `getAbilities()` or `executeAbility()`. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add a usage example showing how to `await` the exported `ready` promise before calling `getAbilities()` or `executeAbility()`, since initialization is asynchronous (categories and abilities are fetched from the REST API on import). Related to #77253. Related to #76349. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
westonruter
added
[Package] Abilities
|
Size Change: +15 B (0%) Total Size: 7.74 MB 📦 View Changed
ℹ️ View Unchanged
|
|
Flaky tests detected in 37ae845. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/24307676022
|
jorgefilipecosta
approved these changes
Apr 15, 2026
Member
jorgefilipecosta
left a comment
jorgefilipecosta
left a comment
There was a problem hiding this comment.
Thank you for finding this issue and proposing a solution, this solution looks good to me 👍
github-actions
bot
removed
the
Backport to WP 7.0 Beta/RC
gutenbergplugin
pushed a commit
that referenced
this pull request
Apr 15, 2026
* Core Abilities: Export initialization promise as `ready` Consumers of `@wordpress/core-abilities` had no way to know when the server-side categories and abilities had finished loading into the client store, since `initialize()` was called fire-and-forget. Export the returned promise as `ready` so callers can `await` it before calling `getAbilities()` or `executeAbility()`. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Core Abilities: Document `ready` promise in README Add a usage example showing how to `await` the exported `ready` promise before calling `getAbilities()` or `executeAbility()`, since initialization is asynchronous (categories and abilities are fetched from the REST API on import). Related to #77253. Related to #76349. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
github-actions
bot
added
the
Backported to WP Core
|
I just cherry-picked this PR to the wp/7.0 branch to get it included in the next release: aa9c7e4 |
westonruter
added a commit
to westonruter/wp-ai-experiments
that referenced
this pull request
Apr 17, 2026
`@wordpress/abilities`' `executeAbility` looks up abilities in a client-side store. PHP-registered abilities only land there once `@wordpress/core-abilities` has fetched `/wp-abilities/v1/abilities` and registered each one. Without awaiting that initialization, the agent's first `execute_ability(...)` call failed with "Ability not found" and the model retried. Import `@wordpress/core-abilities` once at module load and await its exported `ready` promise (added in WordPress/gutenberg#77254) before delegating to `executeAbility`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Closes #77253
Why?
REST API calls to fetch the Abilities API endpoints must currently finish before modules may interact with
getAbilities()orexecuteAbility().How?
This exports the
Promisereturn value from theinitializefunction asreadyso that modules can await on that to resolve before attempting to access abilities.Testing Instructions
Add a plugin that does the following:
You should see a list of the abilities successfully logged along with the site info.
Use of AI Tools
Claude Sonnet 4.6 was used to propose a solution and implement the fix.