anomalyco / anomalyco/opencode

[Bug] Desktop: all session tabs show the same avatar letter instead of per-project icons

Open
#44,666 1 comment 0 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Aug 24, 2026.

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

Description

Description

In OpenCode Desktop on Windows, every open session tab shows the same avatar — a letter icon with "C" — regardless of which project the session belongs to. With multiple projects open in parallel, the tab bar gives no visual way to tell sessions apart; the only differentiator left is the (truncated) tab title.

Per-project avatars in the tab bar are clearly intended: each tab renders a project avatar (session-tab-avatar.tsx, custom icon with an initial-letter fallback). In my case the differentiation is not happening.

Expected behavior

Each session tab shows its own project's icon, or when no custom icon is set, a distinct initial/color derived from that session's actual project — so tabs from different projects are visually distinguishable at a glance.

Observed behavior

All session tabs show an identical "C" letter avatar, independent of the underlying project.

Possible directions (from the source layout)
  • The avatar falls back to displayName(project) initials — if all tabs resolve to the same project object (identity collision), they will legitimately render identically
  • Or the shared/global project row's icon data leaks into per-project lookups, as reported for the sidebar in #39488
  • Related identity bugs that could produce this: #44101 (clones of the same repo get the wrong project identity), #40094 (path-prefix collision opens the wrong project)
Environment
  • App: OpenCode Desktop 1.18.21
  • OS: Microsoft Windows 11 Education, 25H2, build 26200.8875

Happy to provide a screenshot of the tab bar or debug output about which project IDs my open sessions resolve to, if useful.

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.