Marking AI-generated suggestions

When CKEditor AI features create track changes suggestions, you can mark those suggestions as AI-generated so reviewers can tell them apart from manual edits. The same origin can also be surfaced later in revision history, so a reviewer can see which saved revisions involved AI. Both are opt-in display options that are turned off by default.

When CKEditor AI works together with Track Changes, its edits can be recorded as suggestions rather than applied directly to the content. Whenever a suggestion originates from AI, it is tagged so the editor can tell it apart from manual edits.

By default, an AI-generated suggestion looks exactly like a manual one. The display options below let you surface its origin in the suggestion annotation.

Use config.trackChanges.showAISource to control whether and how an AI-generated suggestion advertises its origin.

The 'pill' mode adds an “AI-generated” pill to the suggestion balloon and keeps the original author’s identity:

ClassicEditor
    .create( {
        /* ... */
        trackChanges: {
            showAISource: 'pill'
        }
    } )
    .then( /* ... */ )
    .catch( /* ... */ );

In the demo below, run a proofreading pass over the text. The AI corrections appear in the sidebar, each marked with an “AI-generated” pill while keeping the original author:

The 'author' mode replaces the author shown in the suggestion view (name and avatar) with a view-only AI identity. The original author is still stored in the suggestion data, so only the display changes:

ClassicEditor
    .create( {
        /* ... */
        trackChanges: {
            showAISource: 'author'
        }
    } )
    .then( /* ... */ )
    .catch( /* ... */ );

In the demo below, run a proofreading pass over the text. The AI corrections appear in the sidebar under a view-only “AI Assistant” identity instead of the document author:

When showAISource is set to 'author', the suggestion view uses a built-in “AI Assistant” identity. Customize it with config.trackChanges.aiAuthor:

ClassicEditor
    .create( {
        /* ... */
        trackChanges: {
            showAISource: 'author',
            aiAuthor: {
                name: 'Acme Assistant',
                avatar: 'https://example.com/ai-avatar.png'
            }
        }
    } )
    .then( /* ... */ )
    .catch( /* ... */ );

Both fields are optional: name defaults to AI Assistant, and when no avatar is provided, a default AI icon is shown.

Suggestion annotations only show the origin while a suggestion is still open. Once a suggestion is accepted, or when an AI feature writes to the document directly, the annotation is gone. Revision history keeps that information, so a reviewer can still tell which saved revisions involved AI.

Use config.revisionHistory.showAISource to turn the markers on.

ClassicEditor
    .create( {
        /* ... */
        revisionHistory: {
            showAISource: 'pill'
        }
    } )
    .then( /* ... */ )
    .catch( /* ... */ );

With 'pill', revision history marks the origin in two places:

• An “Includes AI suggestions” pill appears in the revisions list next to every revision that contains at least one change or suggestion created with the help of AI features.
• When comparing revisions, an individual AI-assisted change is described with a “using AI” note and a sparkle icon, for example “Suggested by Joe using AI”.

In the demo below, run a proofreading pass over the text. The AI corrections are applied as suggestions and saved as a revision. Open the revision history with the toolbar button to see the saved revision marked with the pill, and select it to see each change described as made using AI:

The accepted values are a subset of config.trackChanges.showAISource, so you can configure both features consistently:

ClassicEditor
    .create( {
        /* ... */
        trackChanges: {
            showAISource: 'pill'
        },
        revisionHistory: {
            showAISource: 'pill'
        }
    } )
    .then( /* ... */ )
    .catch( /* ... */ );

• Track changes – review, accept, and reject suggested changes, whether made by people or by AI.
• Revision history – browse saved revisions of the document and compare them.
• CKEditor AI – an overview of all AI features.
• Using CKEditor AI programmatically – drive AI features and apply their results from code.