Desktop 1.18.7: renderer crashes with 'AutoScroller plugin depends on Scroller plugin' when opening Settings

[QYworld]

Description

OpenCode Desktop 1.18.7 throws a fatal renderer error and the window turns into an error page whenever I open the Settings view (or any screen that has a sortable/drag-and-drop list). The error shown is:

Error: AutoScroller plugin depends on Scroller plugin
    at PluginRegistry.register
    at set plugins
    ...
    at loadEnd

Looks like a drag-and-drop plugin ordering bug in the bundled renderer: the AutoScroller plugin expects the Scroller plugin to already be registered, but the default plugin set used by these sortable lists doesn't include Scroller, so it throws as soon as the view mounts.

Plugins

Only the default bundled otty-integration plugin in ~/.config/opencode/plugins. No custom plugins.

OpenCode version

Desktop 1.18.7 (the opencode CLI at 1.18.7 is unaffected — only the Electron renderer crashes).

Steps to reproduce

1. Install OpenCode Desktop 1.18.7 on macOS (Apple Silicon).
2. Open the app and have at least one server configured (local or remote HTTP — the bug is not related to the server itself, it just needs a sortable list in the UI to render).
3. Open Settings (Cmd+,).
4. The renderer immediately throws AutoScroller plugin depends on Scroller plugin and the window shows the error page.

Screenshot and/or share link

(Error text is the one pasted in the Description above.)

Operating System

macOS (Apple Silicon, Hardened Runtime)

Terminal

Desktop app (Electron), not a terminal.

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• The issue does not use one of the required issue templates (Bug Report, Feature Request, or Question). Please resubmit using the Bug Report template with the required fields filled in.
• The description appears to be AI-generated: it contains an unusually detailed minified-bundle analysis (exact line numbers, variable names, 4 call sites) that a typical user would not produce from simply observing a crash. AI-generated walls of text are not acceptable per our contributing guidelines. Please describe what you actually observed, your environment, and how to reproduce — in your own words.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[QYworld]

Closing — I'll resubmit a concise, template-based bug report separately. Sorry for the noise.

[github-actions]

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.