Automatically use color to distinguish terminals
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing related issue #478, discussion #442, and the linked GNOME design issue for prior approaches to identifying hosts and changing terminal colors. Done should mean a tab automatically selects a distinct palette when logging into a different container or remote host, without requiring manual color changes.
Written by the indexing model from the issue text.
Description
Discord username (optional)
scaon. display name is abron.
Describe the solution you'd like?
I'd love it if my terminal's palette automatically switched whenever I log into a new container or remote host.
Here's a mockup:
https://github.com/warpdotdev/Warp/assets/1776/e65a9586-3ae4-4c4c-ace2-a7530ce561a0
Is your feature request related to a problem? Please describe.
I'm often surrounded by identical-looking terminal windows. Even though they look the same, they all connect to different containers and remote hosts. It gets confusing and can lead to accidents.
Additional context
I explored one possible implementation for a different terminal here: https://gitlab.gnome.org/Teams/Design/whiteboards/-/issues/233
Summary: when Warp changes a tab's title (usually in response to the prompt sending "user@host"), it could also set the tab's color scheme based on the hostname. 'bronson@fedorawould be blue,bronson@colo` would be scary red.
I think something like this would cure me of typing commands into the wrong terminal!
Related Features
This would be like https://github.com/warpdotdev/Warp/issues/478, but automatic.
And people mentioned something similar in https://github.com/warpdotdev/Warp/discussions/442
How important is this feature to you?
3
Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1
None
- Dominant language
- Rust
- Stars
- 65.1k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
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 warpdotdev/warp
-
area:agent area:window-tabs-panes enhancement needs-info os:mac repro:high triaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
warpdotdev/warp#15768 · 3 comments · 1 reaction ·
-
bug factory-auto-implement factory:revops-factory os:mac ready-to-implement repro:high triaged warp:auto-triage-review
Difficulty 1/5 Under an hour Newbie friendliness 90/100
warpdotdev/warp#15697 · 2 comments ·
-
area:editor-notebooks bug repro:high triaged warp:auto-triage-review warp:tracking
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
warpdotdev/warp#13949 · 3 comments ·
-
markdown_parser: unclosed `<u>` markers pair via the emphasis algorithm and delete surrounding text Openarea:editor-notebooks bug ready-to-implement repro:high triaged warp:auto-triage-review
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
warpdotdev/warp#12863 · 2 comments ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
warpdotdev/warp#11969 · 2 comments ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100