Features / WordPress site operations

Follow each change. See what actually ran.

Give WordPress work an explicit target, status and event history. Review queued changes, inspect completed steps and find the sites that still need attention after a partial failure.

The workflow on screen

Open the events behind a completed change

This demo shows two builder edits for the same site, with separate statuses and event logs. Expand an operation to inspect its recorded execution instead of relying only on a chat reply.

Recovery options depend on the operation and the evidence saved for it. A queued action or a required checkpoint is not proof of completion or recovery.

Open the events behind a completed change. Real IrmaWP interface with fictional demo data.
Real screenshot · Dark mode · Fictional demo data · November 16, 2026. Open the full demo screenshot in a new tab
In practice

How you use it

01

See what is queued

A pending instruction is not a completed change. Review queued and running operations without treating the assistant's explanation as the final result.

02

Inspect a failure

Open the operation's events to see where execution stopped. Across several sites, check the per-site outcomes before retrying work.

03

Respect the site's rules

Authorization, connection capabilities and execution policies still apply. A workflow may require approval or staging before it can run.

Before you connect

What to know

Does every operation have rollback?
No. Recovery depends on the operation and available artifacts or backups. Review the workflow's recovery options before a high-risk change.
Is this an unrestricted remote shell?
No. Connector operations are limited to registered abilities. Arbitrary server-level commands require SSH and the appropriate authorization.

Start with your own sites.

Connect a small portfolio, check the tools you need, and choose the plan that fits your team's work.