When multiple people edit a Word document at the same time, each collaborator sees colored cursors and selection highlights. With Microsoft Copilot integrated into Word, the real-time co-authoring cursor behavior changes in specific ways that can confuse users. The main issue is that Copilot-generated content can cause cursor jumps, delayed sync, or overlapping edits that are hard to track. This article explains exactly how Copilot cursors behave during real-time co-authoring, why these behaviors happen, and how to manage them effectively.
Key Takeaways: Copilot Cursor Behavior in Co-Authoring
- Copilot insertion cursor: A dashed blue line appears where Copilot inserts text; it does not belong to any human collaborator.
- Auto-save and version history: Copilot drafts create a separate version entry; you can restore the pre-Copilot state without losing other co-authors’ changes.
- Conflict resolution in real-time: Word uses last-write-wins logic; if two people accept different Copilot suggestions at the same time, one set of changes is silently discarded.
How Copilot Cursors Differ from Human Collaborator Cursors
In standard real-time co-authoring, each human editor has a colored cursor with a name badge. Copilot does not have a persistent cursor because it is not a live collaborator. Instead, Copilot inserts text in one of three cursor modes:
First, when you invoke Copilot through the Draft or Rewrite command, Word places a temporary insertion point at the location where Copilot will generate content. This insertion point is marked with a dashed blue line that lasts until Copilot finishes generating the text. During generation, the dashed line pulses, indicating that the document is being modified by Copilot. Other co-authors see this dashed line on their screens, but they cannot interact with it.
Second, if you use Copilot to rewrite a selection, the cursor jumps to the beginning of the rewritten section. The rewritten text replaces the original selection instantly on your screen, but other co-authors may see the original text for a few seconds until the change syncs. This delay is caused by the auto-save interval, which is typically 2 to 5 seconds.
Third, when Copilot generates a table or list, the cursor moves to the first cell or first list item. The cursor does not stay inside the Copilot-generated content after generation completes. This behavior prevents accidental edits inside the generated block.
Steps to Manage Copilot Cursor Behavior During Co-Authoring
Follow these steps to control how Copilot cursors appear and behave when multiple people are editing the same document.
- Turn off real-time typing for sensitive edits
Open the document. Go to File > Options > General. Under Real-time typing and presence, uncheck Show real-time typing. This hides all human cursors but does not affect Copilot insertion. Copilot’s dashed blue line still appears. Use this setting when you want to prevent co-authors from seeing Copilot’s work-in-progress. - Use Suggest mode instead of Insert mode
When you ask Copilot to draft content, type “/suggest” after your prompt. For example, “Draft a project summary /suggest.” Copilot inserts the text as a suggestion with a light gray background. The suggestion does not become part of the document until a human co-author clicks Accept. No cursor jump occurs because the suggestion is overlaid, not inserted inline. - Resolve conflicting Copilot changes with version history
If two co-authors run Copilot simultaneously and the document becomes corrupted or shows duplicate content, go to File > Info > Version History. Select the version just before the conflicting Copilot runs. Click Restore. This removes both Copilot changes. Then ask one co-author to run Copilot again while the other waits. - Disable Copilot auto-invocation in shared documents
In the Copilot pane, click the three dots menu and select Settings. Under Auto-invocation, uncheck Enable auto-invocation in shared documents. This prevents Copilot from automatically suggesting rewrites when multiple people are editing. Cursor jumps caused by auto-invocation stop completely. - Use the Sync button to force cursor alignment
If your cursor appears in a different location than what other co-authors see, click the Sync button in the top-right corner of the Word window. This forces a full state sync between all co-authors. The button is labeled with a circular arrow icon. After clicking, all cursors and Copilot insertion points refresh within 2 seconds.
If Copilot Cursor Behavior Still Causes Problems
Copilot cursor jumps to the top of the document during drafting
This happens when Copilot encounters a paragraph that cannot be edited, such as a locked section or a table with merged cells. The cursor moves to the nearest editable location, which is often the document start. To fix this, unlock the section by going to Review > Restrict Editing and removing all editing restrictions. Then rerun the Copilot command.
Other co-authors see the Copilot dashed line after generation completes
The dashed blue line should disappear within 5 seconds after Copilot finishes. If it persists, one co-author has an unsaved local change that conflicts with the Copilot insertion. Ask all co-authors to press Ctrl+S to force an immediate auto-save. The dashed line disappears after the save.
Copilot overwrites text that a co-author is currently typing
Word uses last-write-wins conflict resolution. If Copilot inserts text at the exact location where a human is typing, the human’s text is replaced. To prevent this, use the Suggest mode described in step 2. Alternatively, ask co-authors to type in a different section of the document while Copilot is generating.
Copilot Cursor vs Human Cursor: Key Differences
| Item | Copilot Cursor | Human Cursor |
|---|---|---|
| Appearance | Dashed blue line, no name badge | Solid colored line with user name badge |
| Duration | Visible only during generation, disappears after 5 seconds | Persistent while the user is active in the document |
| Interaction by others | Cannot be clicked or followed | Can be clicked via presence icons |
| Sync delay | Up to 5 seconds after generation | Near-instant (less than 1 second) |
| Conflict handling | Overwrites if last write wins | Prompts merge dialog if conflict detected |
You can now control Copilot cursor behavior during real-time co-authoring by using Suggest mode, disabling auto-invocation, and forcing sync with the Sync button. Next time you co-author a Word document with Copilot, test the Suggest mode first to avoid unwanted overwrites. For advanced control, combine real-time typing off with version history restoration to undo conflicting Copilot changes without affecting other co-authors’ work.