anomalyco / anomalyco/opencode

Unpackaged desktop app shares the installed Dev taskbar identity

Open
#46,473 0 comments 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Aug 31, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

The unpackaged Electron app and an installed Dev build both use ai.opencode.desktop.dev as their Windows AppUserModelID. This lets Windows associate the installed application with an unpackaged Electron shortcut or pin. If that development target later disappears, the taskbar can resolve the group through the stale target and display the generic document icon instead of the packaged application icon.

This was reproduced on a downstream Windows build that preserves the same packaged/unpackaged identity relationship as current upstream dev. The collision originates from the AppUserModelID setup introduced in #23368; that PR correctly added an explicit identity, but the unpackaged fallback currently reuses the installed Dev identity.

The unpackaged process should use a distinct AppUserModelID while retaining the existing Dev user-data directory.

Plugins

N/A

OpenCode version

dev at 04284921ac

Steps to reproduce
  1. Build and install the Windows Dev desktop application.
  2. Launch the unpackaged Electron desktop application.
  3. Confirm that both processes use ai.opencode.desktop.dev as AppUserModelID.
  4. Leave a shortcut or pin for the unpackaged Electron target, then remove or move that target.
  5. Launch the installed Dev application and observe that Windows can show the stale or generic taskbar identity instead of the packaged icon.
Screenshot and/or share link

N/A

Operating System

Windows 11

Terminal

Windows Terminal

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.