Fix: ensure tools are configured before editor renders on note switch

[7eliassen]

Problem:

Occasionally, when switching between notes, some editor.js blocks may not be displayed correctly.

Root Cause:

*toolsUserConfigLoaded and isEditorReady already true when the function is just called*

This issue occurs because the toolsUserConfigLoaded and isEditorReady flags are not properly reset. As a result, the editor may render before the tools are fully configured, causing certain blocks to fail to display.

What done:

• Added logic to reset toolsUserConfigLoaded and isEditorReady before calling loadToolsScripts, ensuring that the editor waits for the tools to be properly configured before rendering.
• Destroy the editor reliably on unmount to prevent bug (screenshot bellow) when the previous editor instance wasn't cleaned up.

• Added a load counter to discard stale async results and prevent race conditions during rapid note switching.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
codex-ui	Ready	Preview	Aug 4, 2026 6:57pm

[Copilot]

Pull request overview

This PR addresses an intermittent Editor.js rendering issue when switching between notes by ensuring the editor does not render until tool scripts/configuration have been rebuilt for the newly selected note.

Changes:

• Reset isEditorReady and toolsUserConfigLoaded before re-loading tool scripts on noteAndUserTools changes.
• Ensure the editor component remounts only after tools are configured, preventing blocks from rendering with stale/missing tool configuration.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.