Agent Log: a site can now silence a writer it does not care about.
Reported from a staging site: every WP-CLI run logged Elementor rewriting its
own Default Kit settings — three rows in a twelve-row log.
The obvious fix would have been to skip saves with no field diff. There is no
such save: update_metadata() refuses an identical write before any hook
fires, comparing the stored value with === and returning false. So anything
that reaches this module did alter the row, and those entries are true.
They are simply uninteresting, and only the site can say which of its writers
are. The object type is not the criterion either — filtering
elementor_library would fix one plugin's habit, leave the pattern open for
every other plugin that writes settings on load, and hide a genuine edit to an
Elementor template.
add_filter( 'dpt_agent_log_record', function ( $record, $entry ) {
return ( 'elementor_library' === $entry['object_subtype'] ) ? false : $record;
}, 10, 2 );
It runs when the request ends, so the entry carries the channel and the name
of the application password that made the change. And on a network it runs
inside the site the change happened on, so a callback may read that site's own
options to decide.
Nothing is filtered by default. What is absent from this log is meant to
mean it did not happen over an API.
The same filter is in the standalone plugin as
digitizer_ai_agent_log_record. This module stands down whenever that plugin
is active, so only one of them ever runs.
Design note: docs/superpowers/specs/2026-09-02-agent-log-noise-filter-design.md.
1810 assertions pass.