{"id":133,"date":"2026-08-06T15:24:29","date_gmt":"2026-08-06T05:24:29","guid":{"rendered":"https:\/\/web.bird.digital\/wingmind-ai\/audit-log-and-rollbacks\/"},"modified":"2026-08-25T10:23:41","modified_gmt":"2026-08-25T00:23:41","slug":"audit-log-and-rollbacks","status":"publish","type":"page","link":"https:\/\/web.bird.digital\/wingmind-ai\/audit-log-and-rollbacks\/","title":{"rendered":"Audit Log & Rollbacks"},"content":{"rendered":"\n
\n

AI Audit Log: safety, snapshots, and rollback<\/h1>\n\n\n\n

WingMind AI records every AI-driven mutation in a durable AI Audit Log<\/strong> so administrators can inspect what changed, when, and by whom \u2014 and launch a guided rollback when needed. This sits alongside live safety controls that try to prevent unwanted changes in the first place.<\/p>\n<\/div>\n\n\n\n

\n

Complete Accountability & Peace of Mind<\/h2>\n\n\n\n

Every time WingMind AI changes your site, it leaves a paper trail. The AI Audit Log captures who made the change, what tool ran, and before-and-after snapshots of the affected content \u2014 with credentials stripped out and entries kept for 90 days. Destructive actions require your explicit approval before they execute, and Ask Mode lets you inspect freely with zero write access. When something needs reversing, open the log, review the snapshots, and launch a one-click Rollback with Agent<\/strong> that restores the prior state and marks the entry complete.<\/p>\n<\/div>\n\n\n\n

\n
\n

How the safety layers fit together<\/h2>\n\n\n\n

WingMind AI uses a multi-layered defense model to ensure complete control and site safety from prompt to execution:<\/p>\n\n\n\n

    \n
  • Agent modes:<\/strong> Ask Mode blocks all site writes; Agent and Site Editor modes allow authorized changes.<\/li>\n\n\n\n
  • Destructive confirmation:<\/strong> Prompts you to explicitly approve high-impact actions before they execute.<\/li>\n\n\n\n
  • Capability checks:<\/strong> Native WordPress permissions are enforced on every server tool.<\/li>\n\n\n\n
  • AI Audit Log:<\/strong> Creates a durable before-and-after snapshot of every modification.<\/li>\n<\/ul>\n\n\n\n

    Note: Read-only operations (such as inspecting posts or listing users) are never logged \u2014 only actions that modify your site.<\/em><\/p>\n<\/div>\n\n\n\n

    \n

    Safety tools (prevention)<\/h2>\n\n\n\n

    1. Ask Mode \u2014 write protection<\/h3>\n\n\n\n

    In Ask Mode<\/strong>, write tools are removed from the model\u2019s tool list and blocked at execution time. The agent can inspect the site but cannot change anything. This is the safest mode for exploration and Q&A.<\/p>\n\n\n\n

    2. Destructive action confirmation<\/h3>\n\n\n\n

    Before high-impact tools run, WingMind AI shows a Confirm destructive action<\/strong> modal with the tool name and arguments. If you cancel, the tool does not run and nothing is logged as applied.<\/p>\n\n\n\n

    Examples of actions that require confirmation:<\/p>\n\n\n\n

      \n
    • Deleting posts, terms, media, users, menus, templates, plugins<\/li>\n\n\n\n
    • Switching themes, updating global styles, changing site settings<\/li>\n\n\n\n
    • Installing or activating plugins<\/li>\n\n\n\n
    • Creating users, restoring revisions<\/li>\n\n\n\n
    • Most WooCommerce and Gravity Forms delete operations<\/li>\n<\/ul>\n\n\n\n

      Some tools use status-gated<\/strong> confirmation \u2014 for example, delete_post<\/code> only prompts when the post is published or scheduled, not when it\u2019s already a draft.<\/p>\n\n\n\n

      3. In-turn Undo (block editor sidebar only)<\/h3>\n\n\n\n

      While using the block editor sidebar<\/strong>, WingMind AI records reversible steps during each agent turn. An Undo<\/strong> button appears after edits, letting you revert all document changes from that turn immediately \u2014 without opening the audit log.<\/p>\n\n\n\n

      This is a fast, local safety net. The fullscreen agent does not offer the same in-turn undo; it relies on the durable audit log and rollback flow instead.<\/p>\n<\/div>\n\n\n\n

      \n

      Snapshot tracking (what gets recorded)<\/h2>\n\n\n\n

      Every site modification creates a record in the audit log, storing essential details like who made the change, what was modified, sanitized arguments, and full before-and-after state snapshots.<\/p>\n\n\n\n

      What snapshots contain<\/h3>\n\n\n\n