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 5, 2026 12:58pm

[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.

[7eliassen]

Some changes have been made due to a discovered bug.

A bug was discovered related to double rendering of the editor when switching to another note:

When NoteId changed, noteAndUserTools was recalculated due to the isDraftResolver() call. This triggered an editor render with the old content. Shortly after, noteAndUserTools was recalculated again due to changes in options.noteTools, and the correct note was displayed.

Fix:

• Removed the isDraftResolver() method
• Drafts now define noteTools as an empty array
• Added an authentication check to properly handle the userTools value