anomalyco / anomalyco/opencode

[FEATURE]: Add stronger visual styling controls for TUI session tabs

Open
#47,028 0 comments 0 reactions 1 assignee View on GitHub

@simonklee is already working on this.

Since Sep 3, 2026.

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

Description

Feature hasn't been suggested before.
  • I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request

Session tabs in the V2 TUI can visually blend into the conversation text, making the tab strip and selected tab difficult to identify at a glance. The current tabs.indicators setting switches between status icons and numbers, but numbers do not address the underlying issue: weak structural separation between navigation and chat content.

Please add styling controls that can make session tabs visually distinct without relying only on color. Useful options could include:

  • selected and inactive tab borders or separators
  • tab padding and spacing
  • a distinct tab-strip background
  • stronger active-tab emphasis
  • a dedicated TUI plugin slot for replacing or decorating the tab strip

This would improve scanability and accessibility for users whose terminals, themes, or visual needs make color-only differentiation insufficient.

The issue is consistently noticeable during normal use. Numbered indicators are not a suitable workaround because the problem is visual separation rather than identifying tabs by number.

Environment:

  • OpenCode: opencode2 v0.0.0-beta-18992
  • OS: Microsoft Windows 10.0.26200.9168
  • Terminal: TERM=xterm-256color; terminal application unavailable
  • Shell: C:\WINDOWS\system32\cmd.exe
  • Install/channel: beta
  • Active plugins: none found in configuration

Related but distinct: #42416 requests a per-session plugin indicator slot, and #38985 requests busy-status indicators. This request is specifically about the visual separation and styling of the tab strip itself.

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.