Block editor
These abilities ship in WPPilot Free and register on every install where the plugin is enabled.
At a glance
Block editor registers 11 abilities: 5 that only read, 1 that write, and 5 marked destructive. That split is the practical answer to how much of this module can run unattended. Reads cost nothing and are safe to repeat, so discovery is the part to be generous with; the writes are where review belongs, and the destructive calls stop for an explicit confirmation every single time regardless of which profile is active.
What this module is for
Use WPPilot Pro's typed theme bridge to inspect the active block theme, Theme JSON, and Full Site Editing templates, with reviewable queued changes.
Before you rely on it: Theme-file templates and theme.json remain read-only through the generic bridge. Finalize queued database-backed template changes in the Site Editor and review representative routes and breakpoints.
Typical workflows
- Inventory templates and identify whether each comes from the database or theme files
- Inspect Theme JSON and registered settings before planning a design-system change
- Queue a database-backed template edit for native Site Editor review
The WordPress Block Themes integration page covers the same module from the workflow side, with the capability map and the questions worth asking before a first write.
Availability on your site
The Block editor module ships in WPPilot Free, so it registers on every install where the plugin is active. No licence check and no dependency detection stand between the agent and these 11 abilities. What the connected agent can actually call is then narrowed twice more: by the safety profile active on the site, and by the WordPress capabilities of the user behind the credential. A read that succeeds for an administrator can be absent entirely for an editor.
Every write these abilities perform is recorded in the change ledger, and destructive calls can be routed through the approval queue so a person signs off before anything is applied. A successful tool result means the operation returned, not that the front end, the cache, and every dependent template are correct: that still needs a look.
Reads
Available in every safety profile, including Read Only. Inspection costs nothing and is not rate limited.
| Ability | What it does |
|---|---|
wppilot/gutenberg-get-contentGet Gutenberg Content | Reads the live saved Gutenberg post_content for one target and returns a compact parsed block tree. This also reports the Block Editor Queue runtime plus curl SSE/poll URLs so agents can ask the user to open the queue page before queueing static/native block changes. This does not read queued pending block_spec data; if a non-terminal Gutenberg queue item exists for the target, pending_gutenberg_change summarizes it separately. |
wppilot/gutenberg-get-finalization-urlGet Gutenberg Finalization URL | Returns the generic Block Editor Queue admin page URL for one ready or failed Gutenberg batch, plus the current finalizer runtime status and curl SSE/poll URLs. If the page is open and can finalize the batch, prefer watching the status URL instead of asking the user to do anything. |
wppilot/gutenberg-get-finalizer-runtimeGet Block Editor Queue Runtime | Reports whether the WPPilot Block Editor Queue admin page is open and heartbeating, including token-gated SSE and poll URLs that agents can watch with curl. Call this at the start of Gutenberg work: if the runtime is offline, ask the user to open the returned generic Block Editor Queue page URL and keep it open while static/native Gutenberg changes are queued and finalized. |
wppilot/gutenberg-get-pending-batchGet Gutenberg Pending Batch | Returns compact status, target summaries, validation errors, Block Editor Queue runtime status, and curl SSE/poll URLs for one pending batch. |
wppilot/gutenberg-list-pending-batchesList Gutenberg Pending Batches | Lists compact queue state grouped by Gutenberg batch for agent recovery, plus the current Block Editor Queue runtime status and curl SSE/poll URLs. Full block specs are not returned. |
Writes
Gated by the active profile and your WordPress capabilities. Rate limited to 120 per minute per credential.
| Ability | What it does |
|---|---|
wppilot/gutenberg-create-pending-batchCreate Gutenberg Pending Batch | Creates an empty draft Gutenberg pending batch and reports the Block Editor Queue runtime with curl SSE/poll URLs. Draft batches are recoverable but not finalizable; after adding target changes, call gutenberg-enable-batch-finalization. If the runtime is offline, ask the user to open the generic Block Editor Queue page and keep it open while you work. |
Destructive
Marked destructive in the source, so each call needs an explicit confirmation flag, every time.
| Ability | What it does |
|---|---|
wppilot/gutenberg-add-pending-changeAdd Gutenberg Pending Change | Adds one replace-content target change to a draft Gutenberg pending batch, or auto-creates a draft batch when batch_id is omitted. Static/native blocks are finalized in a hidden editor iframe so registered third-party blocks can be serialized by their editor JavaScript. Queued changes are not live until gutenberg-enable-batch-finalization marks the batch ready and an open Block Editor Queue page completes it. |
wppilot/gutenberg-delete-pending-batchDelete Gutenberg Pending Batch | Cancels a draft, ready, running, prepared, failed, or conflicted Gutenberg pending batch and its non-finalized items without touching target content. |
wppilot/gutenberg-delete-pending-changeDelete Gutenberg Pending Change | Cancels one Gutenberg pending item without touching target content. The MVP batch page does not expose per-item cancellation, but agents can use this ability for recovery. |
wppilot/gutenberg-enable-batch-finalizationEnable Gutenberg Batch Finalization | Marks a draft Gutenberg pending batch ready after all target changes are queued. If the Block Editor Queue page is open, it can pick up the batch automatically; otherwise the response tells the agent to ask the user to open the generic Block Editor Queue page. The response also includes token-gated SSE and poll URLs agents can watch with curl. Browser-serialized items are staged first; queued changes are still not live until the whole batch commits and reports finalized. |
wppilot/gutenberg-write-contentWrite Gutenberg Content | Directly writes Gutenberg post_content only when every supplied block is a registered WPPilot-owned dynamic-only block. Native/static Gutenberg blocks require browser JS finalization; queue them with gutenberg-add-pending-change, then call gutenberg-enable-batch-finalization and send the finalization link to the user. |