Selected text is unreadable (black on black) on light themes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by tracing how selection colors are applied to session transcript text in assistant markdown, code blocks, and user messages, then check the built-in opencode light theme in the test renderer. Compare selected text contrast in light and dark themes and reproduce the black selection bar in Ghostty if available. Done means selected text remains readable in all three transcript areas on light themes while dark theme selection still works.
Written by the indexing model from the issue text.
Description
Description
Selecting text in the session transcript on a light theme is unreadable: the selection paints black text on a black background. This happens in assistant markdown, code blocks and user messages. The dark theme is fine.
Selected text has no background of its own (the surrounding block's color is transparent for the text cells), so OpenTUI's default inverse selection turns the foreground black on the ink color. In a test renderer on the built-in opencode light theme (no custom theme), selected text in a user message and in assistant markdown has a contrast ratio of 1.21:1 (dark theme: 18.1:1).
Also seen live in Ghostty with a custom light theme: dragging over text shows a solid black bar and the text cannot be read.
Plugins
none
OpenCode version
dev (6a5973d263)
Steps to reproduce
- Use a light theme (
theme.mode: "light"). - Open a session with at least one user message and one assistant reply.
- Drag over text in either one.
Screenshot
I can attach a recording if useful.
Operating System
macOS
Terminal
Ghostty
- Dominant language
- TypeScript
- Stars
- 215k
- Forks
- 28.9k
- Avg merge
- 4h 21m
- Merged PRs (30d)
- 476
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 anomalyco/opencode
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anomalyco/opencode#58247 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/opencode#58216 · 1 comment ·
Maintainers usually reply within 1 day
-
Opencde Github Actions Bot Cannot InstallPossibly taken @zzz-creator claimed this today. Openreproduced
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anomalyco/opencode#57911 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
anomalyco/opencode#57855 · 1 comment ·
Maintainers usually reply within 1 day
-
opencode.tools adds the execute / session_move hint even when Code Mode is deniedPossibly taken @Yun-0000 claimed this 2 days ago. Openreproduced
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
anomalyco/opencode#57711 · 1 comment ·
Maintainers usually reply within 1 day
All issues in anomalyco/opencode
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
source-cooperative/docs.source.coop#41 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Nimblesite/SharpLsp#468 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
solidjs-community/solid-primitives#1082 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day