René's URL Explorer Experiment


Title: Add support for new `meta.public` flag · Issue #9 · wp-cli/ability-command · GitHub

Open Graph Title: Add support for new `meta.public` flag · Issue #9 · wp-cli/ability-command

X Title: Add support for new `meta.public` flag · Issue #9 · wp-cli/ability-command

Description: WordPress Core ticket #65568 introduces in version 7.1 meta.public as the high-level client-exposure setting, with channel-specific settings taking precedence. In 7.1 WP Core resolves the cascade before get_meta_item() returns, so show_i...

Open Graph Description: WordPress Core ticket #65568 introduces in version 7.1 meta.public as the high-level client-exposure setting, with channel-specific settings taking precedence. In 7.1 WP Core resolves the cascade b...

X Description: WordPress Core ticket #65568 introduces in version 7.1 meta.public as the high-level client-exposure setting, with channel-specific settings taking precedence. In 7.1 WP Core resolves the cascade b...

Opengraph URL: https://github.com/wp-cli/ability-command/issues/9

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add support for new `meta.public` flag","articleBody":"[WordPress Core ticket #65568](https://core.trac.wordpress.org/ticket/65568) introduces in version 7.1 `meta.public` as the high-level client-exposure setting, with channel-specific settings taking precedence.\n\nIn 7.1 WP Core resolves the cascade before `get_meta_item()` returns, so `show_in_rest` already reports effective REST exposure and the command stays correct as is. The gap is that `meta.public` itself is invisible. There is no `public` field and no way to tell whether REST exposure came from the high-level flag or the channel flag, which matters as soon as an operator needs to change it. On 6.9 and 7.0 the flag is inert in WP Core, so an ability written against 7.1 produces identical CLI output on every supported version while its actual reachability differs.\n\n## Affected surface\n\nExposure shows up in three documented places today. [`wp ability list`](https://developer.wordpress.org/cli/commands/ability/list/) offers `show_in_rest` as an optional field and a `--show-in-rest=\u003cbool>` filter. [`wp ability get`](https://developer.wordpress.org/cli/commands/ability/get/) includes it among the default fields, so it prints on every call. The [parent `wp ability` page](https://developer.wordpress.org/cli/commands/ability/) also carries an example that names the field explicitly.\n\nThose pages are generated from the inline command documentation, so the reference updates land in the same PR as the code.\n\n[`run`](https://developer.wordpress.org/cli/commands/ability/run/), [`exists`](https://developer.wordpress.org/cli/commands/ability/exists/), [`can-run`](https://developer.wordpress.org/cli/commands/ability/can-run/), and [`validate`](https://developer.wordpress.org/cli/commands/ability/validate/) expose nothing about REST or client channels and should stay that way. `can-run` answers a permission question, which is separate from client exposure.\n\n\n## Scope\n\nAdd `public` as an optional field on `list` and a default field on `get`, ordered before `show_in_rest`. Add a `--public=\u003cbool>` filter to `list`.\n\nCore resolves `meta.public` into the channel flags at registration, so `--show-in-rest` keeps working against effective exposure without extra logic here. Nothing in this package should reimplement the precedence rules.\n\n`wp ability list` keeps listing every registered ability regardless of exposure. WP-CLI runs with full trust and its job is to report what is registered, including abilities deliberately hidden from REST and MCP. These flags are display and filter concerns here, not access control.\n\n## Open questions\n\n1. Should `public` render tri-state (`1`/`0`/empty) the way `readonly` and friends already do through `format_annotation()`? Empty would mean the ability never declared the flag. Note that `show_in_rest` cannot carry the same distinction anymore, since Core collapses declared and inherited into one resolved value before the command reads it.\n2. `meta.public` only exists in 7.1. On 6.9 and 7.0 the field renders whatever the ability declared while REST exposure does not follow it, which is the confusing case. A `WP_CLI::debug()` note on those versions may be worth it.\n3. Worth adding a raw `meta` field to `wp ability get`, mirroring the one `wp ability category get` already has? It is the only way to see channel-specific settings like `meta.mcp.public`.\n\n## References\n\nSlack thread starting from [this message](https://wordpress.slack.com/archives/C08TJ8BPULS/p1784806800996839?thread_ts=1783365523.986029&cid=C08TJ8BPULS). Related PR in MCP Adapter showing how this hits plugins built on the Abilities API: [WordPress/mcp-adapter#254](https://github.com/WordPress/mcp-adapter/pull/254), which also documents a flag resolution ordering trap.","author":{"url":"https://github.com/gziolo","@type":"Person","name":"gziolo"},"datePublished":"2026-07-24T08:16:45Z","url":"https://github.com/wp-cli/ability-command/issues/9"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:4aadc076-7a48-c0ef-128d-aa6d3b6744a6
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idEB1C:14467D:6E22AD:9AE0E9:6AFB678D
html-safe-nonce12e178254f4df0820e8088526cfdc72b42fec470d3f5fd24a6e20bb8f48366a6
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFQjFDOjE0NDY3RDo2RTIyQUQ6OUFFMEU5OjZBRkI2NzhEIiwidmlzaXRvcl9pZCI6IjgyOTEzNzE0MzY4NjIwMzk5NDkiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmac478dd6c88f53e806b11ee171c075d5b69e7691bf2cc11e1de34ae39a96d127d1
hovercard-subject-tagissue:4966612145
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/wp-cli/ability-command/9/issue_layout
twitter:imagehttps://opengraph.githubassets.com/10dbd6e8d6870e5fb62c2044567d8c70ea89957ec63c419f5f093210d780fa3c/wp-cli/ability-command/issues/9
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/10dbd6e8d6870e5fb62c2044567d8c70ea89957ec63c419f5f093210d780fa3c/wp-cli/ability-command/issues/9
og:image:altWordPress Core ticket #65568 introduces in version 7.1 meta.public as the high-level client-exposure setting, with channel-specific settings taking precedence. In 7.1 WP Core resolves the cascade b...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamegziolo
hostnamegithub.com
expected-hostnamegithub.com
Noneea33d13c96d0ff66bd8fa906b193d2213536b78cb06b0c50a4632c58b1418f94
turbo-cache-controlno-preview
go-importgithub.com/wp-cli/ability-command git https://github.com/wp-cli/ability-command.git
octolytics-dimension-user_id1570774
octolytics-dimension-user_loginwp-cli
octolytics-dimension-repository_id1113185972
octolytics-dimension-repository_nwowp-cli/ability-command
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id1113185972
octolytics-dimension-repository_network_root_nwowp-cli/ability-command
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release59ef97164c52cf59bd10558ddec9c4f482763988
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/wp-cli/ability-command/issues/9#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fwp-cli%2Fability-command%2Fissues%2F9
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fwp-cli%2Fability-command%2Fissues%2F9
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=wp-cli%2Fability-command
Reloadhttps://github.com/wp-cli/ability-command/issues/9
Reloadhttps://github.com/wp-cli/ability-command/issues/9
Reloadhttps://github.com/wp-cli/ability-command/issues/9
wp-clihttps://github.com/wp-cli
ability-commandhttps://github.com/wp-cli/ability-command
Codehttps://github.com/wp-cli/ability-command
Issueshttps://github.com/wp-cli/ability-command/issues
Pull requestshttps://github.com/wp-cli/ability-command/pulls
Actionshttps://github.com/wp-cli/ability-command/actions
Security and qualityhttps://github.com/wp-cli/ability-command/security
Insightshttps://github.com/wp-cli/ability-command/pulse
https://github.com/wp-cli/ability-command
New issuehttps://github.com/login?return_to=https://github.com/wp-cli/ability-command/issues/9
New issuehttps://github.com/login?return_to=https://github.com/wp-cli/ability-command/issues/9
#10https://github.com/wp-cli/ability-command/pull/10
Add support for new meta.public flaghttps://github.com/wp-cli/ability-command/issues/9#top
#10https://github.com/wp-cli/ability-command/pull/10
enhancementNew feature or requesthttps://github.com/wp-cli/ability-command/issues?q=state%3Aopen%20label%3A%22enhancement%22
scope:distributionRelated to distributionhttps://github.com/wp-cli/ability-command/issues?q=state%3Aopen%20label%3A%22scope%3Adistribution%22
1.0.3https://github.com/wp-cli/ability-command/milestone/4
https://github.com/gziolo
gziolohttps://github.com/gziolo
on Jul 24, 2026https://github.com/wp-cli/ability-command/issues/9#issue-4966612145
WordPress Core ticket #65568https://core.trac.wordpress.org/ticket/65568
wp ability listhttps://developer.wordpress.org/cli/commands/ability/list/
wp ability gethttps://developer.wordpress.org/cli/commands/ability/get/
parent wp ability pagehttps://developer.wordpress.org/cli/commands/ability/
runhttps://developer.wordpress.org/cli/commands/ability/run/
existshttps://developer.wordpress.org/cli/commands/ability/exists/
can-runhttps://developer.wordpress.org/cli/commands/ability/can-run/
validatehttps://developer.wordpress.org/cli/commands/ability/validate/
this messagehttps://wordpress.slack.com/archives/C08TJ8BPULS/p1784806800996839?thread_ts=1783365523.986029&cid=C08TJ8BPULS
WordPress/mcp-adapter#254https://github.com/WordPress/mcp-adapter/pull/254
github-actionshttps://github.com/apps/github-actions
enhancementNew feature or requesthttps://github.com/wp-cli/ability-command/issues?q=state%3Aopen%20label%3A%22enhancement%22
scope:distributionRelated to distributionhttps://github.com/wp-cli/ability-command/issues?q=state%3Aopen%20label%3A%22scope%3Adistribution%22
state:unconfirmedhttps://github.com/wp-cli/ability-command/issues?q=state%3Aopen%20label%3A%22state%3Aunconfirmed%22
on Jul 24, 2026https://github.com/wp-cli/ability-command/issues/9#event-28425570799
swissspidyhttps://github.com/swissspidy
1.0.2https://github.com/wp-cli/ability-command/milestone/3
on Jul 24, 2026https://github.com/wp-cli/ability-command/issues/9#event-28426411008
swissspidyhttps://github.com/swissspidy
1.0.2https://github.com/wp-cli/ability-command/milestone/3
1.0.3https://github.com/wp-cli/ability-command/milestone/4
on Aug 4, 2026https://github.com/wp-cli/ability-command/issues/9#event-28945450663
swissspidyhttps://github.com/swissspidy
state:unconfirmedhttps://github.com/wp-cli/ability-command/issues?q=state%3Aopen%20label%3A%22state%3Aunconfirmed%22
on Aug 5, 2026https://github.com/wp-cli/ability-command/issues/9#event-29005778921
swissspidyhttps://github.com/swissspidy
on Aug 9, 2026https://github.com/wp-cli/ability-command/issues/9#event-29180893606
Add support for the `meta.public` flaghttps://github.com/wp-cli/ability-command/commit/b6922bab1d25430caa4afb5381eeb6e352afe919
b6922bahttps://github.com/wp-cli/ability-command/commit/b6922bab1d25430caa4afb5381eeb6e352afe919
swissspidyhttps://github.com/swissspidy
completedhttps://github.com/wp-cli/ability-command/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
#10https://github.com/wp-cli/ability-command/pull/10
on Aug 9, 2026https://github.com/wp-cli/ability-command/issues/9#event-29186446901
Sign up for freehttps://github.com/signup?return_to=https://github.com/wp-cli/ability-command/issues/9
Sign in to commenthttps://github.com/login?return_to=https://github.com/wp-cli/ability-command/issues/9
enhancementNew feature or requesthttps://github.com/wp-cli/ability-command/issues?q=state%3Aopen%20label%3A%22enhancement%22
scope:distributionRelated to distributionhttps://github.com/wp-cli/ability-command/issues?q=state%3Aopen%20label%3A%22scope%3Adistribution%22
1.0.3https://github.com/wp-cli/ability-command/milestone/4
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.