- fix(app): web manifest error, OAuth error visibility, and Windows custom-elements typings #6425

Open
opened 2026-02-16 18:04:11 -05:00 by yindo · 1 comment
Owner

Originally created by @Observer-GGboy on GitHub (Jan 16, 2026).

Originally assigned to: @thdxr on GitHub.

Description

Summary

  • The web UI serves an invalid site.webmanifest, which causes a manifest parse error in the browser console.
  • OAuth provider connect flow hides callback failures, making it hard to diagnose connection issues.
  • On Windows, app/enterprise custom-elements.d.ts files are placeholders, which breaks type tooling.

Steps to Reproduce

  1. Open web UI and inspect console → manifest parse error appears.
  2. Attempt provider OAuth connect with a failing callback → no user-visible error.
  3. On Windows, open app/enterprise packages in TS tooling → custom-elements typings missing.

Expected

  • Valid web manifest served.
  • OAuth errors surfaced to the user with useful diagnostics.
  • Real custom-elements typings available on Windows.

Environment

  • Windows 10/11
  • opencode dev branch

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @Observer-GGboy on GitHub (Jan 16, 2026). Originally assigned to: @thdxr on GitHub. ### Description Summary - The web UI serves an invalid `site.webmanifest`, which causes a manifest parse error in the browser console. - OAuth provider connect flow hides callback failures, making it hard to diagnose connection issues. - On Windows, app/enterprise `custom-elements.d.ts` files are placeholders, which breaks type tooling. Steps to Reproduce 1) Open web UI and inspect console → manifest parse error appears. 2) Attempt provider OAuth connect with a failing callback → no user-visible error. 3) On Windows, open app/enterprise packages in TS tooling → custom-elements typings missing. Expected - Valid web manifest served. - OAuth errors surfaced to the user with useful diagnostics. - Real custom-elements typings available on Windows. Environment - Windows 10/11 - opencode dev branch ### Plugins _No response_ ### OpenCode version _No response_ ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the windowsbugweb labels 2026-02-16 18:04:11 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 16, 2026):

This issue combines three distinct improvements. I found a related issue that may be worth reviewing:

  • #8297: Plugin installation failures are silent, causing OAuth options to disappear

While #8297 addresses a different aspect (silent plugin installation), it's also related to OAuth error visibility and may provide useful context for the OAuth error visibility improvements mentioned in this issue.

@github-actions[bot] commented on GitHub (Jan 16, 2026): This issue combines three distinct improvements. I found a related issue that may be worth reviewing: - #8297: Plugin installation failures are silent, causing OAuth options to disappear While #8297 addresses a different aspect (silent plugin installation), it's also related to OAuth error visibility and may provide useful context for the OAuth error visibility improvements mentioned in this issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6425