| 开发者 | tlloancy |
|---|---|
| 更新时间 | 2026年9月7日 02:55 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp_ai_client_prompt() / wp_ai_client_after_generate_result). When a generation finishes through that API, the plugin writes a row in a table on your database. If a post is saved in the same request, or if exactly one generation is waiting for you, the post is stamped (origin, model, time).
The journal stores metadata only: caller plugin, model, provider, context, token counts when available. Prompt and completion text are never stored.
An optional visitor-facing note can appear on posts the plugin stamped as generated or assisted. Unstamped posts stay silent.
What it does
wp_ai_client_after_generate_result (WordPress 7.0+)ai_helm_retention_days)wp_ai_client_prompt() exists. On older versions the journal stays empty; you can still set origin by hand in the editor.
tlloancy-source-stamp folder to /wp-content/plugins/.wp_ai_client_prompt(), then check the journal.No. It records AI Client use. Legal assessment stays with the site operator.
The plugin queues runs per user for 15 minutes and auto-stamps only if exactly one run is waiting. Two queued generations: no automatic stamp (wrong metadata is worse than a gap). Cron and logged-out calls are same-request only. Source Stamp → Test calls the AI Client directly: Generate, then Create draft in a second request. The editor box remains the manual fallback.
No. The journal lives in your database. There is no account and no phone-home.
No. Only metadata (time, caller, model, tokens, post ID).
No.