"No Results Found" on Launch Configuration Palette

[dev-xo]

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 included the logs (optional, but helps expedite the bug fix). Log gathering intructions

Describe the bug

Hello folks, since the latest updates (at least been a few days), I'm not able to load the Configuration Palettes that reside in launch_configurations (.warp) on Mac OS X.

I used to be able to days ago, and I tested a few possible cases, like deleting the folder that gets automatically created, closing Warp and trying to launch those configurations again, etc. None of those work.

Interestingly, after creating a configuration, and trying to load it in the same terminal (without closing it), we are able to load those.

• The moment we reset Warp, those simply get ignored, although the folder exists.

To reproduce

• 1. Open Launch Configuration Palette (depending on the system, there might be a combination of buttons or others).
• 2. Search for "Launch Configuration Palette".
• 3. Select one configuration file and press Enter (considering you have already created one, will skip the step, as you all already know how that works).

Expected behavior

Selected configuration should be applied, opening the created tabs, the color of those, or anything else that we might be able to set up and save.

Screenshots, videos, and logs

Operating system (OS)

macOS

Operating system and version

Sonoma 14.3

Shell Version

GNU bash, version 3.2.57(1)-release

Current Warp version

v0.2025.04.02.08.11.stable_03

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

No idea, but at least a week ago from now (Apr 6 2025)

Additional context

As I commented, saving and loading that configuration without exiting Warp works as expected. The issue is the moment we close Warp (either force exit or exit) and try to load that stored configuration.

The folder exists (.warp/launch_configurations), and the .yaml too.

Does this block you from using Warp daily?

No

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

[C0W0]

The team is aware of the issue and is working on a fix. As a workaround for now, you can try creating a new launch config to manually trigger a data fetch, which should bring back all your previous launch configs.

[dev-xo]

I think this might be fixed with the new versions (I could be wrong), as I'm able to load the saved configurations from Configuration Palette.

Will try it a few more times in the following days, and if that's the case, I might close this.

[C0W0]

I think this might be fixed with the new versions (I could be wrong), as I'm able to load the saved configurations from Configuration Palette.

Will try it a few more times in the following days, and if that's the case, I might close this.

The fix has been implemented in Stable Release v0.2025.04.09.08.11, which went out yesterday.

[dev-xo]

Closing this then @C0W0! Thanks for noticing!