Find the tools that keep erroring
Group the error rows in your Activity Log by tool and note, tell this plugin's errors from other plugins' and crashes, and see what to check next.
23 recipes in Maintenance.
Group the error rows in your Activity Log by tool and note, tell this plugin's errors from other plugins' and crashes, and see what to check next.
Summarize a normal week from your Activity Log so you know what to expect before choosing which 1.9.0 alerts to turn on.
Read the denied rows in your Activity Log, sort front-door refusals from tool denials, then open the admin filters to see the reason and the IP.
A read-only walkthrough that tries six reads once each and reports what a connection can see, what it is refused, and what it was never offered. Run it per site or per limited-access agent.
One read-only prompt that reads your site and writes the text for the Site Brief box, so you paste a ready draft instead of starting from a blank field.
A read-only prompt that splits your Activity Log into agent calls and human calls with is_agent_identity, and says when to switch to the admin filters.
Read the Activity Log to tell whether a failing agent was stopped before WordPress, refused at the front door, denied on a tool, or hit an error. Read-only.
One prompt that briefs you on the site basics and the full plugin list, which plugins are active, which are dormant, and what version each one is on. It reads and reports, nothing more.
Read one custom field across a set of posts, spot the messy values, and normalize the ones you approve. Only allowlisted scalar meta keys are in scope.
See exactly what changed between a post as it stands now and an older version of it, without touching either one.
Find leftover http links in your post and page bodies after an HTTPS switch and rewrite the ones you approve. Body content only, not options or the database.
Trim the stored revision history on the posts that carry the most, reviewed as a list you approve, with the live post left exactly as it is.
Fix the timezone, date and time format, and posts-per-page in one pass, with the current values shown and the change approved before it saves.
Read the plugin's own audit log back to confirm which abilities a session called, when, and whether each succeeded, then check details on the Activity Log tab.
Take over an unfamiliar site with one read-only prompt: users and roles, plugins, the active theme, post types, taxonomies, and content counts.
Count and list the old posts you want gone, confirm the exact set, then move them to the Trash in batches so every one of them stays recoverable.
A governance pattern: tell your agent to draft new content instead of publishing, and to show you the revision trail on anything it changes.
Change a phrase everywhere it shows up in your post and page content, with a read-only search you approve before a single literal replacement saves.
Before you migrate, find which page builders are installed and which posts carry their markup, so you know what will break when the builder is gone.
Combine two overlapping posts into a single stronger one, then trash the leftover, only after you approve the merged draft.
A read-only prompt that checks a set of posts against the ACF fields you treat as required and lists which ones still have gaps.
Record a rollback point per post, run a bulk content change in approved batches, then read the audit log of exactly what was written.
Read the plugin's own audit log and get a weekly summary of what the agent did, grouped by ability, status, and day. Run it as an admin.