Editing content with Aimogen in the Classic Editor follows the same core principles as Gutenberg, but applied to a single, continuous content field. There is no preview layer, no AI-specific undo, and no separate review screen. When you apply an AI edit, the content is written directly into the editor.
Any ability to revert changes depends entirely on WordPress revisions.
Where Aimogen Appears in the Classic Editor #
When editing a post or custom post type that uses the Classic Editor, Aimogen is available directly within the editor interface, typically as a panel or action button associated with the content editor.
You do not switch editors or open a separate screen. The AI operates directly on the Classic Editor content.
How Editing Works in the Classic Editor #
The Classic Editor treats content as a single body of text.
When you use Aimogen:
- You select text inside the editor, or choose to edit the full content
- You provide editing instructions
- The AI generates modified content
- The selected content is replaced immediately
There is no intermediate preview or staging step.
Selection Scope and Its Impact #
Because the Classic Editor is not block-based:
- Selecting text limits the edit to that selection
- Editing without a selection applies to the entire post content
Being precise with selection is important, especially for long articles. Full-content edits overwrite everything inside the editor.
No AI Undo or Review Mode #
Aimogen does not provide:
- a preview-before-apply step
- an AI undo button
- a diff or comparison view
- a protected draft copy
Once applied, the edit becomes the current version of the content.
Reverting Changes Using WordPress Revisions #
AI edits in the Classic Editor are treated exactly like manual edits by WordPress.
If:
- revisions are enabled
- the post type supports revisions
- the post is saved or autosaved
then the AI edit is captured as a revision, and you can revert using the standard WordPress Revisions interface.
If revisions are disabled or unavailable, the change cannot be undone.
Aimogen does not manage, limit, or override revision behavior.
Provider and Model Behavior #
The Classic Editor uses the same AI provider and model system as all other Aimogen features.
- A default model is used unless overridden
- Model selection affects only the current edit
- Global settings are not changed by editor usage
Editing tasks generally benefit from instruction-following, stable models rather than highly creative ones.
Formatting Considerations #
Because the Classic Editor works with raw HTML or visual editor content:
- Formatting is preserved as much as possible
- The AI may rewrite HTML-aware content depending on the prompt
- Inline styles, shortcodes, and embeds should be reviewed after edits
Always review formatting before publishing.
Recommended Safe Workflow #
To reduce risk when editing in the Classic Editor:
- Ensure revisions are enabled
- Save the post before applying AI edits
- Work in draft status when possible
- Edit selected text instead of full content
- Avoid large, multi-purpose prompts
This ensures cleaner revision history and easier rollback.
What Aimogen Does Not Do #
Aimogen does not:
- create AI snapshots
- protect original content
- auto-publish changes
- override Classic Editor behavior
- manage revision limits
It writes content directly and relies on WordPress for persistence and recovery.
Summary #
Editing content in the Classic Editor with Aimogen is immediate and direct. Applied AI edits replace the selected content without preview or AI undo. Reverting changes is possible through WordPress revisions, provided they are enabled. The Classic Editor workflow is powerful but requires care, especially when editing full content in one pass.
