Copilot CLI colors don't respect terminal theme in Warp
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by reproducing the issue in Copilot CLI 1.0.84-6 with macOS appearance set to light and Warp using the Fancy Dracula theme. Compare the behavior with Copilot 1.0.84-5 and the default Mac terminal, then trace the /theme and terminal-color handling. Done means dark Warp themes remain readable regardless of the OS appearance setting.
Written by the indexing model from the issue text.
Description
Describe the bug
In Warp terminal (Mac), Copilot CLI changes text colors based on the system light/dark mode setting, regardless of the terminal color theme. This means if you have light mode set at the OS level, but use a dark theme in Warp the text colors assume a light background and are unreadable on the dark background. There does not seem to be a way to force dark mode through the /theme settings.
Affected version
GitHub Copilot CLI 1.0.84-6
Steps to reproduce the behavior
- Set the Mac OS-level appearance to light mode.
- Choose a dark theme in the Warp terminal settings.
- Start Copilot.
Results:
Copilot launches in the correct (dark) theme, then switches to light mode colors. The text is difficult (in some cases impossible) to read.
Expected behavior
Copilot CLI should use a text theme appropriate to the terminal color theme, not the OS color theme.
If the terminal is set to a dark theme, use a dark text color theme regardless of the OS setting.
Additional context
Mac OS 15.7.9
Warp v0.2026.09.09.08.26.stable_02
Warp theme "Fancy Dracula"
GitHub Copilot CLI 1.0.84-6
Workarounds:
- Changing the system-level appearance to dark causes Copilot to switch to the proper colors
- Changing Warp to use a light theme makes the text readable again
- Using the default Mac terminal seems to work as expected.
- Reverting to Copilot v1.0.84-5 works as expected.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/copilot-cli
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/copilot-cli#4932 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/copilot-cli#4909 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/copilot-cli#4906 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4848 ·
-
area:agents area:mcp
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4729 ·
All issues in github/copilot-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#156 ·
-
Priority/High ready-for-agent Severity/Major Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
comp/cli P3 type/docs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
NousResearch/hermes-agent#119756 · 1 comment ·
-
comp: build/pipeline type: bug version: current (v17+)
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
angular/angularfire#3766 ·
-
out-of-date
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
CachyOS/CachyOS-PKGBUILDS#1903 ·