Track changes and suggestions
The Suggestions panel in the editor's right sidebar is where you decide on proposed edits. It holds two kinds, and they are gated differently:
What it holds | Where it comes from | Which plans |
|---|---|---|
Staged drafts | A pipeline drafted the edit for you, most often from a watched code change | Every plan, including Free |
Tracked changes | A person edited the topic with suggest mode on | Team and Business |
Open the panel from the Suggestions tab in the right sidebar. The tab's badge counts tracked changes in the current topic. Staged drafts are counted inside the panel, on the Staged drafts heading, so open the tab to see whether any are waiting.
Review a staged draft
A staged draft is an edit Topicary prepared for you. The usual path is a merged pull request in a watched repository: the Prioritize what to write next worklist raises a Code change item, you choose Draft update, and the proposed edits are staged in the topic and the editor opens on them.
Open the topic. Staged drafts appear at the top of the Suggestions panel under the Staged drafts heading, with a count. Coming straight from Draft update opens the panel for you and flashes the drafted change once the rows load.
Read the provenance chip on each row. A code-watch draft reads From Demand · PR #N and links to the pull request; when the pull request cannot be resolved it degrades to From Demand · code change.
Read the diff line: the original text struck through, the proposed text after it. Both are clipped to 160 characters.
Click the diff line to jump to the affected text in the topic.
Choose Accept or Reject.
Accept applies the edit to the topic straight away and auto-save persists it. A confirmation line appears for 8 seconds reading "Applied to the topic" followed by the origin, so you can see which demand item changed your text.
Reject is reversible. The draft is kept with a rejected status, a reviewer, and a timestamp, which is the audit trail. A bar appears for 8 seconds reading "Draft rejected — kept, not deleted", with an Undo button. When that rejection leaves the demand item with nothing accepted and nothing still pending, the bar also says the item returns to the worklist.
Once no draft from a demand item is still pending, the item leaves your queue, and the editor's demand banner and the worklist both update. Which way it goes depends on your decisions: accept at least one draft and the item is closed as done, reject every one and it returns to the worklist as outstanding work.
Bulk Accept all and Reject all never touch staged drafts. Decide each one on its own row.
If the topic changed after the draft was prepared, the panel says so on the row instead of doing nothing. Which message you see depends on what you did:
What you did | Message on the row |
|---|---|
Clicked the diff line to jump | "The original text no longer matches the content — it may have been edited." |
Clicked Accept | "The original text no longer matches the content — edit manually instead." |
Arrived from Draft update, and the drafted passage could not be found | "Could not locate this change — the topic changed since it was drafted." |
Make the edit by hand in each of these cases.
When the panel looks empty
The panel loads staged drafts from the server, so it distinguishes three states rather than assuming "empty":
What you see | What it means |
|---|---|
"Loading staged drafts…" | The list is still loading. Wait before concluding there is nothing to review. |
"Could not load staged drafts." with Try again | The load failed. Retry; anything already listed may be incomplete. |
No drafts to review | The load finished and found nothing staged. This is the empty state below the Team plans, where the panel exists only for staged drafts. |
No suggestions yet or Suggesting is on | The Team-plan empty states, with a button to turn suggesting on or off. |
Turn on suggest mode
This feature requires the Team capability tier (the Team or Business ). During the beta, every project is on the free Solo tier, so this feature is locked by default: go to Settings ▸ Billing and request Team access to unlock it.
Suggest mode records your edits as proposed changes instead of applying them. Insertions appear in green, deletions in red strikethrough, and a reviewer accepts or rejects each one.
Open a topic in the editor.
Click the Suggest mode button (pen icon) in the editor toolbar, or press Cmd+Shift+M (Ctrl+Shift+M on Windows and Linux).
Edit as usual. A banner reads "Suggest mode: edits are tracked as suggestions, not applied directly."
Turn suggest mode off to return to normal editing.
AI editing is blocked while suggest mode is on. The Sparkles (inline AI) button is disabled with the tooltip "Turn off suggest mode to use AI editing," because block-level AI replacements cannot be tracked as individual suggestions. Check style and terminology quick fixes are refused for the same reason. Turn suggest mode off to apply either.
Suggestion appearance
Change type | Appearance |
|---|---|
Insertion | Green highlighted text |
Deletion | Red text with strikethrough |
Each tracked change is tagged with the author's name and a timestamp.
Review tracked changes
Below the staged drafts, the panel lists every pending tracked change in the current topic:
Accept: applies the change to the document. The insertion is kept, or the deletion is carried out.
Reject: discards the change. The insertion is removed, or the deleted text is restored.
Click a change to jump to its position in the editor.
Accepting or rejecting a tracked change edits the document there and then, so no record of it survives. Only staged drafts keep a rejected row and offer the timed Undo.
Bulk actions
Use the bulk action buttons above the tracked-change list to resolve them all at once:
Accept all: applies every pending tracked change.
Reject all: discards every pending tracked change.
Both act on tracked changes only. Staged drafts keep their own per-row Accept and Reject.
Multi-author grouping
When several authors have contributed tracked changes, the panel groups them by author with initials avatars and label headers, so you can review one contributor at a time.
Email notifications
When somebody else creates a suggestion on a topic you created, Topicary emails you so you know there are pending changes to review. This requires email service configuration for your project.
Use suggest mode for editorial reviews where you want to see exactly what changed before committing. For exploratory co-authoring, Real-time collaboration may be a better fit.
Suggest mode works independently of real-time collaboration. You can use suggest mode whether collaboration is enabled or not. Tracked changes live in the topic content and are visible to anyone who opens it. Staged drafts are stored separately from the content, which is why rejecting one keeps a record.
See also
Prioritize what to write next: the Demand worklist that stages drafts from code changes
Real-time collaboration: simultaneous editing without tracked changes
Topic branches: work on a separate copy of a topic and merge later
Create a review session: gather feedback from external reviewers
Content statuses: workflow states for managing content readiness