Safety & security
Clautron generates configuration, not arbitrary code. The engine enforces hard limits no AI-generated blueprint can override.
What Clautron will not do
- Will not write or execute PHP. Blueprints are JSON. The engine compiles them by composing audited primitives — there is no
eval(), no template-to-PHP step, no shell-out. - Will not modify WordPress core options. Reserved options (
siteurl,home,blogname,admin_email, etc.) are read-only to all blueprints. - Will not change user capabilities or roles. The capabilities subsystem is untouchable.
- Will not register routes outside its namespace. All REST routes live under
/wp-json/clautron/v1/. - Will not access the filesystem outside
wp-content/uploads/clautron/.
Capability gating
Every Clautron admin screen requires manage_options (Administrator). Activating, editing, or deleting a feature, job, or report is restricted to administrators. AI Assistant access is restricted to administrators.
Dry-run mode
Every write action — update_post, delete_post, send_email, set_post_meta — supports dry-run mode. When enabled, the action logs what it would do without performing the change.
Use dry-run when:
- Testing a new job's first run before letting it loose on real data
- Verifying a bulk update query matches the right posts
- Reviewing what a publish gate would block
Enable dry-run in two places:
- Per-action — set
"dry_run": truein the blueprint's action config - Per-job — toggle "Dry run" on the job's settings panel before activating
Activity log
Every blueprint execution is logged to the activity log:
- Which feature/job/report ran
- When (timestamp + duration)
- Trigger context (which post, which user, etc.)
- Outcome — success, condition skipped, action error
- Dry-run flag if applicable
View logs at Clautron → Activity Log. Logs are retained for 30 days by default.
Data privacy
Only the natural language prompts you type in the AI Assistant are sent to your configured AI provider. Specifically not sent:
- Post content, titles, or any WordPress data
- User information, emails, or comments
- Site URL, plugin list, or environment details
- Existing blueprints (unless you paste one into the prompt yourself)
If you choose Ollama as your provider, no data leaves your server at all.