Title: Digitizer AI Agent Log
Author: Ben Kalsky
Published: <strong>2 سپتامبر 2026</strong>
Last modified: 2 سپتامبر 2026

---

جستجوی افزونه‌ها

![](https://ps.w.org/digitizer-ai-agent-log/assets/banner-772x250.png?rev=3677679)

![](https://ps.w.org/digitizer-ai-agent-log/assets/icon-256x256.png?rev=3677679)

# Digitizer AI Agent Log

 توسط [Ben Kalsky](https://profiles.wordpress.org/benkalsky/)

[دانلود](https://downloads.wordpress.org/plugin/digitizer-ai-agent-log.1.1.0.zip)

 * [جزئیات](https://fa.wordpress.org/plugins/digitizer-ai-agent-log/#description)
 * [نقد و بررسی‌ها](https://fa.wordpress.org/plugins/digitizer-ai-agent-log/#reviews)
 *  [نصب](https://fa.wordpress.org/plugins/digitizer-ai-agent-log/#installation)
 * [توسعه](https://fa.wordpress.org/plugins/digitizer-ai-agent-log/#developers)

 [پشتیبانی](https://wordpress.org/support/plugin/digitizer-ai-agent-log/)

## توضیحات

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”.

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.

#### Why not a general activity log

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.

#### What it records

 * **The channel** – `rest`, `cron`, `cli` or `xmlrpc`.
 * **Which application password** 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.
 * **What changed** – the object, and which fields were touched.
 * **When**, in UTC, shown in your site’s timezone.

#### What it does not record

 * **Not the values.** The names of the fields that changed, never their contents.
   A log of what your site contains is a second copy of your site.
 * **Not people.** 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.
 * **Not reads.** Something polling the REST API would fill the table in a day and
   drown the writes that were the reason to look.
 * **No IP addresses.**

#### Reading the log

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`, which requires `manage_options`.
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.

#### Multisite

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.

## عکس‌های صفحه

[⌊The log: what each change arrived on, which application password authenticated
it, what it touched and which fields. The same entries are readable over the REST
API.⌉⌊The log: what each change arrived on, which application password authenticated
it, what it touched and which fields. The same entries are readable over the REST
API.⌉[

The log: what each change arrived on, which application password authenticated it,
what it touched and which fields. The same entries are readable over the REST API.

## نصب

 1. Install and activate. The log table is created the first time the plugin runs.
 2. Find the log under **Agent Activity** in the admin menu.

## سوالات متداول

### Does it slow the site down?

Changes 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.

### Does it send anything anywhere?

No. Nothing leaves the site.

### How large does the table get?

Old rows are pruned automatically, at most once an hour.

### A plugin on my site rewrites its own settings and fills the log. Can I silence it?

Yes, 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:

    ```
    add_filter( 'digitizer_ai_agent_log_record', function ( $record, $entry ) {
        if ( 'elementor_library' === $entry['object_subtype'] ) {
            return false;
        }
        return $record;
    }, 10, 2 );
    ```

The entry carries `object_type`, `object_subtype`, `object_id`, `object_name`, `
action`, `fields`, `blog_id`, `channel`, `app` and `user_id`, 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.

Note 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.

### What happens when I uninstall it?

The table is dropped and both of its options are deleted, on every site of a network.
Nothing is left behind.

## نقد و بررسی‌ها

نقد و بررسی‌ای برای این افزونه یافت نشد.

## توسعه دهندگان و همکاران

“Digitizer AI Agent Log” نرم افزار متن باز است. افراد زیر در این افزونه مشارکت کرده‌اند.

مشارکت کنندگان

 *   [ Ben Kalsky ](https://profiles.wordpress.org/benkalsky/)

[ترجمه “Digitizer AI Agent Log” به زبان شما.](https://translate.wordpress.org/projects/wp-plugins/digitizer-ai-agent-log)

### علاقه‌ مند به توسعه هستید؟

[کد را مرور کنید](https://plugins.trac.wordpress.org/browser/digitizer-ai-agent-log/)،
[مخزن SVN](https://plugins.svn.wordpress.org/digitizer-ai-agent-log/) را بررسی کنید،
یا از طریق [RSS](https://plugins.trac.wordpress.org/log/digitizer-ai-agent-log/?limit=100&mode=stop_on_copy&format=rss)
در [گزارش توسعه](https://plugins.trac.wordpress.org/log/digitizer-ai-agent-log/)
مشترک شوید.

## گزارش تغییرات

#### 1.1.0

 * A `digitizer_ai_agent_log_record` 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.

#### 1.0.1

 * The plugin page gets its screenshot. No functional change.

#### 1.0.0

 * First release.

## اطلاعات

 *  نگارش **1.1.0**
 *  آخرین به‌روزرسانی **3 روز پیش**
 *  نصب‌های فعال **کمتر از 10**
 *  نگارش وردپرس ** 5.5 یا بالاتر **
 *  آزمایش‌شده تا **7.1**
 *  نگارش PHP ** 7.2 یا بالاتر **
 *  زبان
 * [English (US)](https://wordpress.org/plugins/digitizer-ai-agent-log/)
 * برچسب
 * [Activity Log](https://fa.wordpress.org/plugins/tags/activity-log/)[AI](https://fa.wordpress.org/plugins/tags/ai/)
   [audit log](https://fa.wordpress.org/plugins/tags/audit-log/)[rest-api](https://fa.wordpress.org/plugins/tags/rest-api/)
   [wp-cli](https://fa.wordpress.org/plugins/tags/wp-cli/)
 *  [نمایش پیشرفته](https://fa.wordpress.org/plugins/digitizer-ai-agent-log/advanced/)

## امتیازها

هنوز هیچ نقدی ارسال نشده است.

[بررسی شما](https://wordpress.org/support/plugin/digitizer-ai-agent-log/reviews/#new-post)

[مشاهدهٔ همهٔ بررسی‌ها](https://wordpress.org/support/plugin/digitizer-ai-agent-log/reviews/)

## مشارکت کنندگان

 *   [ Ben Kalsky ](https://profiles.wordpress.org/benkalsky/)

## پشتیبانی

چیزی برای گفتن دارید؟ نیاز به کمک دارید؟

 [مشاهده انجمن پشتیبانی](https://wordpress.org/support/plugin/digitizer-ai-agent-log/)