Bug: Edited file by AI breaks MEO viewer rendering

[apoapostolov]

Bug Report

Issue: Since recent versions, edited files by an AI (before keeping changes) break the MEO viewer rendering to classic VS Code.

Steps to Reproduce:

1. Open a Markdown file with MEO viewer enabled
2. Use an AI tool to edit the file
3. Keep the changes (accept the edit)
4. The MEO viewer immediately switches to classic VS Code rendering

Expected Behavior: The MEO viewer should maintain Markdown rendering after accepting AI edits.

Actual Behavior: After AI edits, the file is rendered in classic VS Code instead of MEO.

Workaround: Only moving to another document and returning to the file resumes Markdown rendering via MEO.

Environment: Recent versions (this is a regression - it worked before)

Reproduction Note: This only occurs when the AI makes edits that are accepted/kept. The issue is specific to MEO viewer rendering after AI intervention.

[vadimmelnicuk]

@apoapostolov Thanks for the detailed report. Which tool are you using to make the AI edits?

[apoapostolov]

Copilot standard on VS Insider.

[vadimmelnicuk]

@apoapostolov this is actually expected behaviour for now. Copilot edits operate at a level that MEO's webview cannot access directly, so MEO hands off to the native editor while you review and resolve changes in the review panel. Once all changes are resolved i.e., kept/rejected and there are no more pending AI changes, it should switch back to MEO automatically. I understand that the automatic switch is not happening on your end. Let me investigate.

[apoapostolov]

Yes the automatic revert from VS standard to MEO is not happening.

[notRyuk]

Expected Behavior: The MEO viewer should maintain Markdown rendering after accepting AI edits.

Hey @vadimmelnicuk, Is this due to in editor edits? I dont see this happening with opencode whereas I can see it happening in antigravity's AI edits.

[sylque]

Maybe this other AI issue is related, so I'm posting it here:

Whenever the AI changes the document, the rendering is switched to text, then I see is this:

The document is actually modified by the AI, but it seems I need to reopen the file to see the changes.

[vadimmelnicuk]

@sylque Thanks for flagging this and sharing the screenshot. I've tightened the Copilot handoff in 0.1.19, so please give it a go and let me know if you still see this after updating.

[sylque]

I see no change in v0.1.19.

Here is the full experience with AI on my setup:

1. Context Recognition Issue

• Manual Attachment Required: Unlike other file formats, active .md files are not automatically recognized as the default context when initiating a new AI chat session. Users must manually attach the Markdown file each time.

2. Post-Generation Sync & UI Failures

After the AI processes a modification request, here is what occurs in the editor:

• Mode Switch: The view automatically toggles from Live to Source mode (not a problem in my opinion)
• State Desync: A red banner is displayed "Editor failed to update this document. Try reopening the file."
• Broken Diff View: No changes are rendered in the active editor window immediately following the AI's output. The diff system fails to highlight modifications.
• Broken Diff Navigation: While the floating navigation panel registers that changes exist, the navigation controls (arrows/jumps) are unresponsive.
• Persistence Paradox: Changes only appear after a manual file reload (close/reopen). Upon reopening, changes appear as "already accepted" (no highlights), yet they can be undone using the main Undo button.