anomalyco / anomalyco/opencode
[Desktop] v1.18.30: first-launch splash overlay never hides (white screen with pulsing logo, UI works underneath)
@Hona is already working on this.
Since Sep 11, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Environment
- OS: Windows 11 (x64), WSL2 host
- opencode desktop v1.18.30 (NSIS installer
opencode-desktop-win-x64.exe), Electron 42.3.3 / Chromium 148.0.7778.218 - Install path:
C:\Users\<user>\AppData\Local\Programs\@opencode-aidesktop
Symptom
On launch, the app shows a full-screen white/light overlay containing a single pulsing "O" logo (styled like the OPENCODE mark) that never disappears. The actual app UI is fully rendered and functional underneath (left sidebar, project list, top bar, settings) — accessible visually only via DevTools screenshots.
Reproduction
- Install and run the desktop app on a fresh profile.
- White screen with pulsing "O" appears and stays indefinitely.
Already ruled out
- Overlay persists across: app restarts,
--disable-gpu, page reload via DevTools (CDP), and deleting the profile dir (C:\Users\<user>\AppData\Roaming\ai.opencode.desktop). - Clicking the overlay does nothing; it is not a GPU/compositor issue (CDP screenshots render fine; the page compositor is live).
- The UI under the overlay is fully interactive.
Technical detail
The stuck element is a fixed full-viewport overlay:
DIV.fixed.inset-0.z-[9999].flex.flex-col.items-center.justify-center.bg-background-base
containing a single pulsing inline SVG (logo) with animation: pulse-opacity.
The real app content sits beneath it in the DOM and functions normally.
Sidecar server starts OK; renderer loads oc://renderer/index.html.
Renderer log line: [desktop-onboarding] first launch onboarding pending { pending: true }.
No console errors observed on load; Page.reload re-renders the same stuck splash (deterministic).
Expected behavior
The splash/onboarding overlay should hide once the app is ready (or onboarding completes) so the app is usable.
Impact
Desktop app is effectively unusable on this machine. (CLI opencode works fine.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.