Snapshots and rollback: the safety net
Every write performed by WP Agent Bridge is preceded by a snapshot. Every error is reversible. This is the fundamental principle of the plugin: never write without having saved.
How it works
Before each write, the plugin captures the state of the affected row in six WordPress core tables: posts, postmeta, options, terms, term_taxonomy, term_relationships. This snapshot is stored locally and associated with an operation_id.
Rollback
If a write breaks the site (500 error, blank page, PHP fatal), the plugin detects the problem via loopback verification and automatically restores the snapshot. The agent can also request a manual rollback via wpab/rollback-operation with the operation_id.
Scope
Six tables, no more. Extension tables (WooCommerce HPOS, payment tables) are not covered. This is a design choice: rollback is reliable because it’s limited to the WordPress core.
The ceiling
The number of accumulated snapshots is limited. The recommended ceiling is 700. An alert is issued at 500. Beyond 1000, a known defect (fix planned in 1.9.1) may cause partial restoration without warning.
Conclusion
Snapshots and rollback are the safety net that allows an AI agent to work autonomously. If the agent makes a mistake, the site is restored. If the site breaks, the operation is canceled. This is the difference between safe automation and dangerous automation.
Leave a Reply