v1.17.14 Desktop can't load main UI.

[iwecon]

Description

After upgrading to version 1.17.14 and disabling Use New Layout, I was unable to access the main UI after restarting OpenCode.

Error: Layout context must be used within a context provider
    at use (oc://renderer/assets/main-B1osgIPb.js:8300:25)
    at Object.init (oc://renderer/assets/main-B1osgIPb.js:78029:20)
    at provider (oc://renderer/assets/main-B1osgIPb.js:8270:28)
    at oc://renderer/assets/main-B1osgIPb.js:927:24
    at untrack (oc://renderer/assets/main-B1osgIPb.js:268:33)
    at createComponent (oc://renderer/assets/main-B1osgIPb.js:927:10)
    at DraftProviders (oc://renderer/assets/main-B1osgIPb.js:158783:10)
    at oc://renderer/assets/main-B1osgIPb.js:927:24
    at untrack (oc://renderer/assets/main-B1osgIPb.js:273:12)
    at createComponent (oc://renderer/assets/main-B1osgIPb.js:927:10)
    at get children (oc://renderer/assets/main-B1osgIPb.js:158613:34)
    at get children (oc://renderer/assets/main-B1osgIPb.js:86867:26)
    at get children (oc://renderer/assets/main-B1osgIPb.js:8292:28)
    at Object.fn (oc://renderer/assets/main-B1osgIPb.js:775:35)
    at runComputation (oc://renderer/assets/main-B1osgIPb.js:487:22)
    at updateComputation (oc://renderer/assets/main-B1osgIPb.js:470:3)
    at createMemo (oc://renderer/assets/main-B1osgIPb.js:119:3)
    at children (oc://renderer/assets/main-B1osgIPb.js:388:21)
    at oc://renderer/assets/main-B1osgIPb.js:775:14
    at untrack (oc://renderer/assets/main-B1osgIPb.js:273:12)
    at Object.fn (oc://renderer/assets/main-B1osgIPb.js:770:36)
    at runComputation (oc://renderer/assets/main-B1osgIPb.js:487:22)
    at updateComputation (oc://renderer/assets/main-B1osgIPb.js:470:3)
    at createRenderEffect (oc://renderer/assets/main-B1osgIPb.js:104:3)
    at provider (oc://renderer/assets/main-B1osgIPb.js:770:5)
    at oc://renderer/assets/main-B1osgIPb.js:927:24
    at untrack (oc://renderer/assets/main-B1osgIPb.js:273:12)
    at createComponent (oc://renderer/assets/main-B1osgIPb.js:927:10)
    at get children (oc://renderer/assets/main-B1osgIPb.js:8289:18)
    at Object.fn (oc://renderer/assets/main-B1osgIPb.js:1138:27)
    at runComputation (oc://renderer/assets/main-B1osgIPb.js:487:22)
    at updateComputation (oc://renderer/assets/main-B1osgIPb.js:470:3)
    at createMemo (oc://renderer/assets/main-B1osgIPb.js:119:3)
    at Show (oc://renderer/assets/main-B1osgIPb.js:1135:10)
    at oc://renderer/assets/main-B1osgIPb.js:927:24
    at untrack (oc://renderer/assets/main-B1osgIPb.js:268:33)
    at createComponent (oc://renderer/assets/main-B1osgIPb.js:927:10)
    at provider (oc://renderer/assets/main-B1osgIPb.js:8284:14)
    at oc://renderer/assets/main-B1osgIPb.js:927:24
    at untrack (oc://renderer/assets/main-B1osgIPb.js:273:12)
    at createComponent (oc://renderer/assets/main-B1osgIPb.js:927:10)
    at get children (oc://renderer/assets/main-B1osgIPb.js:86865:16)
    at get children (oc://renderer/assets/main-B1osgIPb.js:8292:28)
    at Object.fn (oc://renderer/assets/main-B1osgIPb.js:775:35)
    at runComputation (oc://renderer/assets/main-B1osgIPb.js:487:22)
    at updateComputation (oc://renderer/assets/main-B1osgIPb.js:470:3)
    at createMemo (oc://renderer/assets/main-B1osgIPb.js:119:3)
    at children (oc://renderer/assets/main-B1osgIPb.js:388:21)
    at oc://renderer/assets/main-B1osgIPb.js:775:14
    at untrack (oc://renderer/assets/main-B1osgIPb.js:273:12)

Plugins

No response

OpenCode version

1.17.14

Steps to reproduce

1. 1.17.13 keep open Use New Layout setting, and upgrade to 1.17.14;
2. then disable Use New Layout and quit, reopen OpenCode Desktop;
3. this problem keeps appearing, and I can't access the main UI.

Screenshot and/or share link

Operating System

macOS 27 Beta 2 & 3

Terminal

No response

[Jerry050512]

Root Cause Analysis

I hit the same bug on Windows (v1.17.14) and traced the root cause.

What happens

When newLayoutDesigns is enabled, the app creates draft tabs that are persisted in the window state file (opencode.window.<id>.dat). These draft tabs are rendered by DraftProviders, which depends on a Layout context provider that only exists in the new layout tree.

When you disable newLayoutDesigns and restart, the app loads the persisted draft tabs from the window state, but the old layout does not provide the Layout context — causing the DraftProviders component to throw:

Error: Layout context must be used within a context provider at Object.init (main-*.js:78035:20) at DraftProviders (main-*.js:158813:10)

The key issue is that tab state is layout-agnostic — it persists across layout switches, but the components that render those tabs are layout-specific and expect context providers that may not exist in the other layout.

Why reinstalling doesn't help

The window state (including draft tabs) is stored under %APPDATA%\ai.opencode.desktop\opencode.window.*.dat, which survives reinstallations.

Workaround

Clear the persisted tabs in the window state file. On Windows:

# Find your window state file
$datFile = C:\Users\Jerry\AppData\Roaming\ai.opencode.desktop\opencode.window.*.dat
# Reset tabs to empty
Set-Content -Path (Resolve-Path $datFile).Path -Value '{tabs:[],tabs.recent:{}}' -NoNewline

On macOS/Linux, the equivalent path is ~/.config/ai.opencode.desktop/ or check the userData path in debug logs.

Then restart the app. This clears the incompatible draft tab state while keeping all other settings intact.

Alternatively, re-enable newLayoutDesigns in default.dat:

$datFile = C:\Users\Jerry\AppData\Roaming\ai.opencode.desktop\default.dat
$json = Get-Content $datFile -Raw | ConvertFrom-Json
$settings = $json.'settings.v3' | ConvertFrom-Json
$settings.general.newLayoutDesigns = $true
$json.'settings.v3' = ($settings | ConvertTo-Json -Depth 10 -Compress)
$json | ConvertTo-Json -Depth 10 | Set-Content $datFile -NoNewline

Suggested Fix

The app should handle this gracefully. Two options:

1. Guard the Layout context usage: In DraftProviders, check if the Layout context exists before using it. If it doesn't (e.g., old layout), fall back to rendering without it or skip the draft tab.
2. Migrate tab state on layout switch: When newLayoutDesigns is toggled off, clear or convert any draft tabs that depend on the new layout's context providers. This could be done in the settings change handler.

Option 1 is more robust since it handles the general case of layout-specific context dependencies.

Notes

This comment is generated by OpenCode with GLM. Please carefully check the contents.

[iwecon]

Root Cause Analysis

I hit the same bug on Windows (v1.17.14) and traced the root cause.

What happens

When newLayoutDesigns is enabled, the app creates draft tabs that are persisted in the window state file (opencode.window.<id>.dat). These draft tabs are rendered by DraftProviders, which depends on a Layout context provider that only exists in the new layout tree.

When you disable newLayoutDesigns and restart, the app loads the persisted draft tabs from the window state, but the old layout does not provide the Layout context — causing the DraftProviders component to throw:

Error: Layout context must be used within a context provider at Object.init (main-*.js:78035:20) at DraftProviders (main-*.js:158813:10)

The key issue is that tab state is layout-agnostic — it persists across layout switches, but the components that render those tabs are layout-specific and expect context providers that may not exist in the other layout.

Why reinstalling doesn't help

The window state (including draft tabs) is stored under %APPDATA%\ai.opencode.desktop\opencode.window.*.dat, which survives reinstallations.

Workaround

Clear the persisted tabs in the window state file. On Windows:

Find your window state file

$datFile = C:\Users\Jerry\AppData\Roaming\ai.opencode.desktop\opencode.window.*.dat

Reset tabs to empty

Set-Content -Path (Resolve-Path $datFile).Path -Value '{tabs:[],tabs.recent:{}}' -NoNewline
On macOS/Linux, the equivalent path is ~/.config/ai.opencode.desktop/ or check the userData path in debug logs.

Then restart the app. This clears the incompatible draft tab state while keeping all other settings intact.

Alternatively, re-enable newLayoutDesigns in default.dat:

$datFile = C:\Users\Jerry\AppData\Roaming\ai.opencode.desktop\default.dat
$json = Get-Content $datFile -Raw | ConvertFrom-Json
$settings = $json.'settings.v3' | ConvertFrom-Json
$settings.general.newLayoutDesigns = $true
$json.'settings.v3' = ($settings | ConvertTo-Json -Depth 10 -Compress)
$json | ConvertTo-Json -Depth 10 | Set-Content $datFile -NoNewline

Suggested Fix

The app should handle this gracefully. Two options:

1. Guard the Layout context usage: In DraftProviders, check if the Layout context exists before using it. If it doesn't (e.g., old layout), fall back to rendering without it or skip the draft tab.
2. Migrate tab state on layout switch: When newLayoutDesigns is toggled off, clear or convert any draft tabs that depend on the new layout's context providers. This could be done in the settings change handler.

Option 1 is more robust since it handles the general case of layout-specific context dependencies.

Notes

This comment is generated by OpenCode with GLM. Please carefully check the contents.

I encountered an error for the first time after downgrading to version 1.17.13, then I restarted the application, and now it works normally.

[dani10gl]

Same root cause, but a stronger trigger: this also happens on a clean install of v1.17.15 with default settings — no upgrade, no toggling.

The app is unusable on first launch, out of the box.

Environment

• OpenCode Desktop 1.17.15 (Windows installer, fresh install — no prior OpenCode data)
• Windows 11 Pro 26200
• newLayoutDesigns: never set → falls back to newLayoutDesignsDefault = false (default)

Repro

1. Install 1.17.15 on a machine with no existing %APPDATA%\ai.opencode.desktop
2. Launch. First-launch onboarding runs and creates the default project.
3. Renderer dies immediately.

Logs

main.log is clean — the backend is fine, the sidecar comes up:

[08:51:33.307] awaiting server ready
[08:51:33.308] server ready { url: 'http://127.0.0.1:50815' }

onboarding.log:

[08:51:33.454] first launch onboarding completed { createDefaultProject: true, defaultProject: '...\New OpenCode Project' }

renderer.log — dies 37 ms after the onboarding draft starts:

[08:51:33.448] [desktop-onboarding] first launch onboarding evaluated
[08:51:33.455] [desktop-onboarding] starting first launch draft
[08:51:33.492] [error] fatal renderer error
  Error: Layout context must be used within a context provider
      at use (main-ClUtJP2v.js:8300:25)
      at Object.init (main-ClUtJP2v.js:78080:20)
      at provider (main-ClUtJP2v.js:8270:28)
      at DraftProviders (main-ClUtJP2v.js:158967:10)

Root cause (confirms @Jerry050512's analysis)

I unpacked app.asar and traced the bundle. LayoutProvider is mounted in exactly one place in the whole bundle — line 158896, inside ServerScopedProviders. Compare the two provider stacks:

Component	Chain
ServerScopedProviders (158890)	PermissionProvider → **LayoutProvider** → ModelsProvider → …
DraftServerScopedProviders (158949)	PermissionProvider → ModelsProvider

DraftServerScopedProviders is missing LayoutProvider, but DraftRoute (158745) still renders DraftProviders (158966) → FileProvider, whose init() calls useLayout() at 78080. FileProvider has gate: false, so init() runs eagerly and throws at 8300.

DraftRoute does not go through LegacyServerScopedShell (158911) or NewAppLayout (158931) — the only two components that mount ServerScopedProviders. So the draft route can never render, regardless of the newLayoutDesigns setting.

The newLayoutDesigns toggle isn't the cause — it's just one way to reach the draft route. First-launch onboarding is another, and it hits users with default settings on a clean install.

Other entry point: openProjectNewSession() (157247) calls tabs.newDraft(...) → navigates to /new-session?draftId=… → DraftRoute → same crash.

Workaround

Same as the one above — clear the persisted draft tab:

$f = Get-ChildItem "$env:APPDATA\ai.opencode.desktop\opencode.window.*.dat"
Set-Content $f.FullName -Value '{"tabs":"[]"}' -Encoding UTF8 -NoNewline

With no draft tab, DraftRoute's Show falls through to its fallback → Navigate("/") and the app loads normally. Since firstLaunchOnboardingComplete is already persisted by the crashed run, onboarding won't recreate the draft.

Suggested fix

Agreed that guarding is the more robust option, but the minimal fix looks like adding LayoutProvider to DraftServerScopedProviders so it matches ServerScopedProviders. Guarding useLayout() in FileProvider would only paper over a draft subtree that genuinely needs layout state (layout.tabs(...) is used at line 78083).

Separately: the first-launch onboarding path creating a draft tab means every clean 1.17.15 install crashes on first run, which may deserve its own severity/milestone.