Skip to content

[FEATURE]: Theme keys for per-role message text colors and grouped Q&A background in conversation history #20897

Closed as not planned

Description

@nice-michael-sretenovic

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

Summary

The current theme schema exposes no way to visually distinguish message types in the conversation history. All messages share the same text/markdownText color. When scrolling back through a long session it is difficult to quickly locate a specific request or a Q&A exchange.

Requested changes

1. Per-role text color keys

Add theme keys to independently color each message role in the history:

  • userMessageText -- color of the user's typed requests/prompts
  • assistantMessageText -- color of regular assistant responses

2. Grouped Q&A background

When the assistant asks a clarifying question and the user answers, that exchange should be visually grouped. Add theme keys:

  • qaGroupBackground -- background color applied to the entire assistant-question + user-answer block
  • qaGroupText -- (optional) text color override within that block

This makes it trivial to scroll back through history and instantly locate where a request was made or where a Q&A exchange happened.

Example theme usage

{
  "theme": {
    "userMessageText": "#A8D8A8",
    "assistantMessageText": "#D8D8D8",
    "qaGroupBackground": "#2A2A40",
    "qaGroupText": "#E8E8FF"
  }
}

Motivation

In long sessions with many tool calls and responses, it becomes hard to navigate the history. Distinct colors per role and a highlighted background for Q&A exchanges would make the history scannable at a glance.

The key distinction from a simple "two-color" approach is the grouped background for Q&A blocks, which is what gives you the fast-scroll landmark you're looking for.

Activity

  1. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on May 3, 2026
  2. github-actions commented on Jul 3, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions