Read Simple History with AI

What we learned testing it

Behavior the ability descriptions do not mention.

• Simple History's AI access is experimental: it is on only while the Enable experimental features box in Simple History's settings (General) is ticked, which also turns on its other experimental features. Through WPVibe the AI can tick it for you (tested), and the recipes ask first.
• All six abilities only read the log: Simple History registers no ability that changes it, and WPVibe does not run Simple History's own WP-CLI commands (tested). The recipes tell the AI to read only.
• Each call returns at most 100 events and there is no next page, so on a busy site the AI asks one day at a time. Recent events and failed logins list a date range among their inputs; search and one user's activity do not, but accepted one in our test.
• Events in a row of the same kind on the same thing are collapsed into one row with a count, and the row shows only the newest one: two people editing one page back to back show as one row under the last editor. All failed logins in a row share one row too, whatever username each used. Search lists events one by one (seen in our test).
• Event times are UTC; date ranges are whole days in your site's time zone.
• If your AI assistant connects to the site with your account, the posts and pages it edits are logged under your name, like your own. Settings it changes through WP-CLI in WPVibe may not be logged at all: Simple History logs settings changes made in WordPress's settings screens, its settings REST route or real WP-CLI.
• The activity totals need an administrator account. In them, deleted means deleted for good and trashed posts count in the content total only; the plugins total also counts deletions, deactivations and notices that an update is available.
• The log starts when Simple History was installed and keeps 30 days by default (60 for sites that installed it before version 5.25.0).