| 开发者 | dudaster |
|---|---|
| 更新时间 | 2026年11月5日 05:39 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
clautron folder to the /wp-content/plugins/ directory.Clautron uses the WordPress AI Client (built into WordPress 7.0+). The provider is configured at the WordPress level: go to your WordPress AI settings to choose and configure a provider. No API keys are stored by this plugin.
Only the natural language prompts you type in the AI Assistant are sent to your AI provider, via the WordPress AI Client. Clautron does not directly connect to any external AI service; all communication is handled by WordPress core. No WordPress content, posts, users, or site data is transmitted.
Primitives are the small, reusable building blocks Clautron composes things from: custom post types, meta fields, admin columns, scheduled tasks, and more. A capability is what you actually get: a specific piece of functionality (a redirect, an admin column, a WooCommerce rule) built from one or more primitives, that you can activate or deactivate as one unit. Some capabilities also carry a manifest (a declared version, requirements, and effects) that lets external tools install, inspect, update, and deactivate them without capability-specific code.
Yes. Clautron creates its own database tables (prefixed with wp_clautron_) to store blueprints, conversation history, scheduled jobs, workflow state, capability install state, and execution logs. All data is removed if you uninstall the plugin.
Clautron's own screens are only available to administrators (manage_options capability). Clautron adds nothing to the frontend by itself: visitors only see changes from capabilities you activate, such as a consent banner, a redirect or security headers.
false return type, valid only since PHP 8.2, which fataled on activation despite the plugin declaring Requires PHP 8.1.wp_clautron_capabilities table tracking each capability's installed version and status separately from its blueprint. This enables comparing installed vs. available version and reinstalling a deactivated capability without losing its edit history.