An AI agent, a headless front end, a sync script and a cron job all reach WordPress the same way a person never does: over an API. When something on the site is not what you left it as, the question is not \"who changed this\" but \"did a person change this, or did something else\".<\/p>\n\n
This plugin answers that question and only that question. It records changes that arrived over the REST API, WP-Cron, WP-CLI or XML-RPC. A change made by a person clicking in wp-admin is not recorded - not filtered out afterwards, not stored and hidden, simply never written.<\/p>\n\n
General activity logs record everything, which means the automated change you are looking for is one line in a thousand made by your own team. This one starts from the other end. If you already run an activity log, this sits beside it and answers a different question.<\/p>\n\n
rest<\/code>, cron<\/code>, cli<\/code> or xmlrpc<\/code>.<\/li>\n- Which application password<\/strong> authenticated the request, by name, when there was one. Never a guess: when the name cannot be determined the field is empty rather than filled with a User-Agent or an IP that merely looks like an identity.<\/li>\n
- What changed<\/strong> - the object, and which fields were touched.<\/li>\n
- When<\/strong>, in UTC, shown in your site's timezone.<\/li>\n<\/ul>\n\n
What it does not record<\/h4>\n\n\n- Not the values.<\/strong> The names of the fields that changed, never their contents. A log of what your site contains is a second copy of your site.<\/li>\n
- Not people.<\/strong> A block editor save is a cookie-authenticated REST request, and it is recognised as a person and skipped. This is the plugin's central promise, and it is the case it was hardest to get right.<\/li>\n
- Not reads.<\/strong> Something polling the REST API would fill the table in a day and drown the writes that were the reason to look.<\/li>\n
- No IP addresses.<\/strong><\/li>\n<\/ul>\n\n
Reading the log<\/h4>\n\n
On its own admin screen, filtered by channel, object type and date range. Or over the REST API at digitizer-ai-agent-log\/v1\/activity<\/code>, which requires manage_options<\/code>. There is deliberately no route that deletes: a log that can be erased through the API is a log an attacker erases on the way out.<\/p>\n\nMultisite<\/h4>\n\n
Each site keeps its own log, in its own table, and a run that switches between sites files each change under the site it happened on.<\/p>\n\n\n
\n- Install and activate. The log table is created the first time the plugin runs.<\/li>\n
- Find the log under Agent Activity<\/strong> in the admin menu.<\/li>\n<\/ol>\n\n\n
\nDoes it slow the site down?<\/h3><\/dt>\nChanges are held in memory during the request and written once, at shutdown, and only when the request came in on a channel worth recording. A browser request writes nothing at all.<\/p><\/dd>\n
Does it send anything anywhere?<\/h3><\/dt>\nNo. Nothing leaves the site.<\/p><\/dd>\n
How large does the table get?<\/h3><\/dt>\nOld rows are pruned automatically, at most once an hour.<\/p><\/dd>\n
A plugin on my site rewrites its own settings and fills the log. Can I silence it?<\/h3><\/dt>\nYes, with a filter. Nothing is filtered out by default, because what is absent from this log is supposed to mean it did not happen over an API:<\/p>\n\n
add_filter( 'digitizer_ai_agent_log_record', function ( $record, $entry ) {\n if ( 'elementor_library' === $entry['object_subtype'] ) {\n return false;\n }\n return $record;\n}, 10, 2 );\n<\/code><\/pre>\n\nThe entry carries object_type<\/code>, object_subtype<\/code>, object_id<\/code>, object_name<\/code>, action<\/code>, fields<\/code>, blog_id<\/code>, channel<\/code>, app<\/code> and user_id<\/code>, so a rule can match on who made the change as well as what it touched. On a network the filter runs inside the site the change happened on, so a callback may read that site's own options to decide.<\/p>\n\nNote that such an entry is not a mistake: WordPress refuses an identical meta write before the plugin ever sees it, so a change that reaches the log did alter the row. It is simply a change you may not care about, and only your site can say which those are.<\/p><\/dd>\n
What happens when I uninstall it?<\/h3><\/dt>\nThe table is dropped and both of its options are deleted, on every site of a network. Nothing is left behind.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.1.0<\/h4>\n\n\n- A
digitizer_ai_agent_log_record<\/code> filter, applied to every entry once the channel and the application name are known, so a site can silence a writer it does not care about. Nothing is filtered by default.<\/li>\n<\/ul>\n\n1.0.1<\/h4>\n\n\n- The plugin page gets its screenshot. No functional change.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First release.<\/li>\n<\/ul>","raw_excerpt":"Records what automations changed on your site - REST API, WP-Cron, WP-CLI, XML-RPC. Changes people make in wp-admin are not recorded at all.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/362363","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=362363"}],"author":[{"embeddable":true,"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/benkalsky"}],"wp:attachment":[{"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=362363"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=362363"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=362363"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=362363"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=362363"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/hi.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=362363"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}