anomalyco / anomalyco/opencode

[FEATURE]: Semantic Chat Message Colors

Open
#49,340 0 comments 0 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Sep 16, 2026.

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

I would like better chat color customization in the OpenCode desktop GUI.

Currently, user messages, progress updates, tool output, and the final assistant response do not have sufficiently separate theme colors. This makes it difficult to quickly identify where a new instruction begins and where the actual final answer is shown.

Desired behavior:

  • User messages should have their own theme color.
  • The final assistant answer should have a different theme color.
  • Progress updates such as “I’m checking...”, tool output, and status messages should not be styled like the final answer.
  • The final answer should be detected using the completed assistant message and its last text part, for example when finish: "stop".
  • The colors should provide sufficient contrast for white text.

Technical suggestion:

  • Add a dedicated attribute for user messages, such as data-user-message.
  • Add a dedicated attribute for the final assistant answer, such as data-final-answer="true".
  • Add separate theme tokens, for example:
    • message-user-background
    • message-assistant-final-background
  • Detect the final answer in the UI code based on the message state instead of relying only on a fragile CSS selector such as :last-child.
  • Support loading custom GUI themes from a user theme directory or from opencode.json.
  • Custom themes should remain available after OpenCode updates without requiring users to modify the bundled app.asar file.

Example:

{
  "messageUserBackground": "#254b32",
  "messageAssistantFinalBackground": "#3d477a"
}

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.