Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Support per-element theming: distinct colors for user prompts vs. assistant responses

Aberta
#4,767 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
shell
Domínio
accessibility, cli, design

Direção de pesquisa

Nenhum arquivo, teste ou ponto de entrada é indicado. Comece localizando a configuração de tema existente e os caminhos de renderização dos prompts do usuário e das respostas do assistente; em seguida, analise as issues relacionadas #2830, #3591 e #2123 para determinar o escopo pretendido. A tarefa estará concluída quando houver uma forma acordada e ciente do tema para distinguir esses elementos, com o comportamento coberto por testes.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area:configuration area:theming-accessibility
Describe the feature or problem you'd like to solve

Copilot CLI's theme setting only applies a single global color palette ("default", "github", "dim", "high-contrast", "colorblind"). There is no way to assign a different color to submitted user prompts versus Copilot's own responses in the scrollback. This makes it hard to visually scan a long session and quickly locate "what did I ask?" among hundreds of lines of agent output (tool calls, reasoning, code blocks). Chat and email clients solve this with sent-vs-received color distinction; Copilot CLI currently has no equivalent, and a similar highlight that once existed was removed as a cosmetic fix rather than tuned (see #3591). Related open requests already tracked in this repo: #2830 (custom color themes), #3591 (restore removed prompt highlight), #2123 (fine-grained per-element theming), #2746, #2288, #1862.

Proposed solution

No response

Example prompts or workflows
  1. A user runs a long debugging session and wants to scroll back and instantly spot every message they personally typed, without reading every line of agent output in between.
  2. A user runs multiple Copilot CLI sessions side by side (e.g., one admin-configured session, one standard session) and wants each session's prompts/responses colored differently to avoid mixing them up visually.
  3. A user with attention/cognitive processing differences relies on visual chunking to parse conversational turns (WCAG 1.3.1 - Info and Relationships) and needs a built-in, theme-aware way to distinguish turns instead of relying on external terminal tricks.
  4. A team lead reviewing a shared/exported session log wants user prompts and assistant responses visually separated at a glance, the same way code review tools color additions vs. deletions.
  5. A user prefers the previous background-highlight behavior on user prompts (removed in a past release) and wants an opt-in toggle to restore it, e.g. { "userPromptHighlight": true }, without waiting for a full custom-theming system.
Image
Additional context

Proposed shape (illustrative only): a themeElements key in settings.json that overrides colors per role, falling back to the active theme preset when unset: { "theme": "github", "themeElements": { "userPrompt": { "foreground": "#E0D0FF", "background": "#1A0A2E" }, "assistantResponse": { "foreground": "#D0FFE0" } } } A minimal first step could be a single boolean toggle to restore the old prompt-highlight behavior, as proposed in #3591, before building a full custom-theming system like #2830 proposes. Happy to have this consolidated into #2830 or #3591 if maintainers prefer a single tracking issue — flagging here mainly to add another concrete use case and a possible incremental implementation path.

Linguagem predominante
Shell
Estrelas
11.2k
Forks
1.9k
Merge médio
14h 16min
PRs com merge (30d)
6

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/copilot-cli

Todas as issues de github/copilot-cli

Issues semelhantes

Mais issues de Shell/Bash

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.