-
Notifications
You must be signed in to change notification settings - Fork 613
Description
Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
For a long time I have a launch configuration that I use, but ever since version v0.2026.01.28.08.14.stable_04 my launch config no longer works (unsure about the exact version - I mean there are so many - but it must be an issue with a very recent version). It's no longer listed when I open up the Launch Configuration Palette.
I haven't changed my launch config in a while, so I'm pretty sure this is a regression.
After fiddling around I have found the issue:
Previously I had this: color: Green. this no longer works it seems, I now have to use this: color: green (note the value for the 'color' property no longer starts with a capital).
Perhaps I'm not aware of some documentation update (or whatever), but I wanted to share my findings in any case.
To reproduce
this launch config fails (it doesn't even show up in the Launch Config Palette)
name: Default Launch
active_window_index: 0
windows:
- active_tab_index: 0
tabs:
- title: Test
layout:
cwd: /Users/<USERNAME>/
color: Greenwhen changing the color value to lowercase, the launch config shows up again.
name: Default Launch
active_window_index: 0
windows:
- active_tab_index: 0
tabs:
- title: Test
layout:
cwd: /Users/<USERNAME>/
color: greenExpected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
Select an OS
Operating system and version
macOS 26.1
Shell Version
GNU bash, version 3.2.57(1)-release (arm64-apple-darwin25) (--> not the default zsh)
Current Warp version
v0.2026.01.28.08.14.stable_04
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None