anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 02:36:57 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Queued message indicator uses theme accent instead of sender mode color #8906

New Issue
Closed
opened 2026-02-16 18:11:08 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:11:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @mcostasilva on GitHub (Feb 9, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

Description

In the TUI session view, queued user messages are styled with the global accent color instead of the color associated with the mode that sent the message.
This makes queued messages look disconnected from their sender context, especially in sessions where different mode have distinct colors.

Current behavior

  • Queued message left border uses the accent color.
  • QUEUED badge background uses the accent color.
  • Sender/mode color is not reflected while the message is queued.

Expected behavior

  • Queued messages should keep the sender/mode color consistently.
  • Both the left border and QUEUED badge should use the sender color.
  • Badge text should remain readable across themes.

Why this matters

Color is currently used as an identity cue for mode/agent. Switching queued messages to accent breaks that cue and makes scanability worse in mixed-mode sessions.

Plugins

No response

OpenCode version

1.1.53

Steps to reproduce

  1. Open a session in the TUI.
  2. Send messages from a mode with a recognizable non-accent color.
  3. Create/observe a queued message state.
  4. Notice queued styling uses accent instead of mode color.

Screenshot and/or share link

Image

Operating System

macOS 26.2

Terminal

Ghostty

Originally created by @mcostasilva on GitHub (Feb 9, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description ### Description In the TUI session view, queued user messages are styled with the global accent color instead of the color associated with the mode that sent the message. This makes queued messages look disconnected from their sender context, especially in sessions where different mode have distinct colors. ### Current behavior - Queued message left border uses the accent color. - QUEUED badge background uses the accent color. - Sender/mode color is not reflected while the message is queued. ### Expected behavior - Queued messages should keep the sender/mode color consistently. - Both the left border and QUEUED badge should use the sender color. - Badge text should remain readable across themes. ### Why this matters Color is currently used as an identity cue for mode/agent. Switching queued messages to accent breaks that cue and makes scanability worse in mixed-mode sessions. ### Plugins _No response_ ### OpenCode version 1.1.53 ### Steps to reproduce 1. Open a session in the TUI. 2. Send messages from a mode with a recognizable non-accent color. 3. Create/observe a queued message state. 4. Notice queued styling uses accent instead of mode color. ### Screenshot and/or share link <img width="324" height="290" alt="Image" src="https://github.com/user-attachments/assets/068a4ec8-e90e-4fb3-9b3d-981bfa69212d" /> ### Operating System macOS 26.2 ### Terminal Ghostty
yindo added the opentuibug labels 2026-02-16 18:11:08 -05:00
yindo closed this issue 2026-02-16 18:11:08 -05:00
yindo commented 2026-02-16 18:11:08 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 9, 2026):

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

  • #12707: feat(app): queued message controls with send now in prompt

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 9, 2026): This issue might be a duplicate of existing issues. Please check: - #12707: feat(app): queued message controls with send now in prompt Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug opentui
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8906
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?