Subject: Window height locks to (near) full screen when opening the AI Assistant panel

Environment:

  • RapidWeaver Elements v3.0.14 (build 24590)
  • macOS Sequoia 15.7.9

Description:
When clicking the AI Assistant icon (sparkle icon, top-right of the secondary toolbar) to open the “Set up the AI assistant” panel, the entire editor window immediately snaps to near-full screen height. The window jumps upward and its height can no longer be reduced — only the width remains freely resizable. The top toolbar row shifts from ~82px to ~44px from the top of the screen the moment the panel opens.

Steps to reproduce:

  1. Open a project in Elements with the window at a normal, reduced height
  2. Click the AI Assistant icon (sparkle ✦) in the toolbar
  3. Observe the “Set up the AI assistant” panel appearing (prompting to configure an OpenAI or Anthropic API key)
  4. Observe: the window height immediately locks to near-full screen; dragging the top or bottom edge no longer has any effect

Expected behavior:
Opening the AI Assistant panel should not force a window resize. The window should remain at whatever height the user had set, with the panel content scrolling or adapting within the existing window bounds.

Actual behavior:
The window height becomes fixed at (near) full screen the moment the AI Assistant panel opens. Width can still be resized normally, but height cannot — it stays locked until the app is restarted.

Workaround found:
Restarting the app resets the window to a normal, resizable state (until the AI Assistant panel is opened again).

Additional notes:

  • This appears to be tied specifically to the AI Assistant panel’s minimum-height requirement, which seems to force a full window resize rather than adapting within the current window bounds.

  • Not a macOS Sequoia system-wide window tiling setting — no other apps are affected, and only this specific panel triggers it.

Hi @CyberFredje

Thanks for the heads up — and for the clear steps and video.

I’m looking into this one and will get it fixed up!

Cheers

@CyberFredje Mister @tpbradley has worked his late-night magic and the fix is in and shipped, check for updates :slight_smile: