Web: existing profiles are not eligible for the layout transition toggle

[dleopold]

Description

Description

Existing OpenCode Web profiles do not receive layoutTransitionEligible, so the layout transition control is hidden during the current grace period.

Eligibility is currently initialized only through desktop onboarding:

ts
settings.general.setOldLayoutEligible(existingInstall)

The web app does not run that onboarding path, even when the browser already has persisted settings.v3 state or a recorded app version. As a result, existing web users cannot access the already-implemented transition control.

This is the web eligibility portion of #37546. That issue also covers missing workspace/worktree functionality in the new layout, which is a separate problem.

Related context: #37012 requests retaining the legacy layout permanently. This report is narrower and does not request changing the existing sunset policy.

Expected behavior

Existing web profiles should be classified as eligible and see the existing layout transition control before the configured sunset.

Blank web profiles should remain ineligible and start on the new layout without the control.

Steps to reproduce

1. Open OpenCode Web using a browser profile with existing OpenCode settings.
2. Upgrade into the current new-layout transition release.
3. Open Settings → General.
4. Observe that the layout transition control is absent.

The profile has persisted settings.v3 and/or app-version.v1 state, but layoutTransitionEligible is never initialized because web does not run the desktop onboarding path.

OpenCode version

Web client 1.18.3, OpenCode CLI/server 1.18.4; also reproducible on the current dev branch

Proposed scope

Classify previously unclassified web profiles once persisted settings and launch state are ready:

• Profiles with existing settings.v3 state or a recorded app version are eligible.
• Blank web profiles are explicitly ineligible.
• The result is persisted in the existing layoutTransitionEligible field.
• Desktop eligibility behavior remains unchanged.
• The existing layout sunset remains unchanged.

Related issues

• Web: no way to revert the new layout, and the new layout is missing workspaces/worktrees #37546 — Reports the missing web escape hatch alongside missing workspace/worktree support in the new layout.
• [FEATURE] : keep legacy layout option #37012 — Requests retaining the legacy layout permanently; this issue does not propose that policy change.

Operating System

Ubuntu 26.04 LTS

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Web: no way to revert the new layout, and the new layout is missing workspaces/worktrees #37546: Covers the same root cause — layoutTransitionEligible never being set for Web users, leaving the layout revert toggle permanently hidden. The root cause section of that issue identifies this exact gap and even provides the same console workaround.

[dleopold]

This issue might be a duplicate of existing issues. Please check:

• Web: no way to revert the new layout, and the new layout is missing workspaces/worktrees #37546: Covers the same root cause — layoutTransitionEligible never being set for Web users, leaving the layout revert toggle permanently hidden. The root cause section of that issue identifies this exact gap and even provides the same console workaround.

This new issue intentionally narrows the second root cause described in #37546.

#37546 also tracks missing workspace/worktree support in the new layout. Closing it from a PR that only restores the web layout-transition escape hatch would leave that separate problem unresolved.

The focused issue allows #38117 to use an accurate Fixes reference while keeping #37546 open for workspace parity.

[markuest]

i can confirm this regression. fixing this will allow me to update to the newest version while using the old layout.

[dleopold]

A temporary solution for openncode web users to switch to the old layout is to run this in the browser devtools console:

(() => {
  const key = "settings.v3";
  const settings = JSON.parse(localStorage.getItem(key) || "{}");
  settings.general ??= {};
  settings.general.layoutTransitionEligible = true;
  settings.general.newLayoutDesigns = false;
  localStorage.setItem(key, JSON.stringify(settings));
  location.reload();
})();