Editing content with Aimogen inside the Gutenberg editor is direct: when you apply an AI edit, the selected content is replaced immediately. Aimogen itself does not maintain an internal undo system or AI-specific history.
However, reverting changes is possible through WordPress revisions, as long as revisions are enabled and available.
How Aimogen Editing Works #
When you apply an AI edit in Gutenberg:
- You select a block or the full content
- You provide instructions
- The AI generates modified content
- The content is written directly into the editor
Aimogen does not keep a separate copy of the previous content. Once written, the AI has no awareness of what existed before.
Reverting Changes: The Role of WordPress Revisions #
Although Aimogen does not provide its own revert mechanism, WordPress revisions do capture the change, provided that:
- Revisions are enabled on the site
- The post is saved (manually or via autosave)
- The post type supports revisions
In this case, you can revert the AI edit using the normal WordPress “Revisions” interface.
This is the only supported rollback method.
Important Clarification #
- Aimogen does not block or bypass WordPress revisions
- AI edits are treated like normal content edits
- If revisions are disabled, limited, or purged, reverting is not possible
- Aimogen cannot restore content on its own
Revert capability depends entirely on WordPress configuration.
Editing Scope Still Matters #
Even though revisions exist, scope control is still important:
- Editing a block replaces only that block
- Editing full content replaces the entire post body
- Only selected content is modified
Smaller edits reduce risk and make revision rollback more precise.
Recommended Safe Workflow #
To ensure you can always revert if needed:
- Make sure revisions are enabled
- Save the post before applying AI edits
- Work in Draft status when possible
- Apply AI edits in smaller chunks
- Avoid editing published content directly
This ensures WordPress captures clean revision points.
What Aimogen Does Not Do #
Aimogen does not:
- Create AI-specific snapshots
- Offer preview vs apply modes
- Store pre-edit content internally
- Provide a one-click AI undo
All safety comes from WordPress itself.
Why This Design Is Intentional #
Aimogen integrates directly into WordPress’ native editing model:
- No shadow documents
- No duplicate storage
- No performance overhead
- No hidden content states
This keeps behavior predictable and compatible with all editors and post types.
Summary #
- AI edits replace content immediately
- Aimogen has no internal undo system
- WordPress revisions allow reverting, if enabled
- If revisions are disabled, changes are permanent
- Safe editing depends on WordPress configuration and workflow
The key rule is simple: Aimogen writes content; WordPress protects it. As long as revisions are enabled, AI edits are no more dangerous than manual edits — but without revisions, they are final.
