#Config: launch_config.yaml ignored

3 messages · Page 1 of 1 (latest)

fast gulchBOT
#

Hi @wooden marsh. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Based on the information provided in the knowledge sources, there could be a few reasons why your launch configuration is being ignored. Let me address some potential issues:

  1. File naming: Make sure your launch configuration file is named correctly with a .yaml extension. Some users have reported issues when the file had a .txt extension Launch search not finding any launch files (https://github.com/warpdotdev/Warp/issues/1827).

  2. File location: Ensure that your launch_config.yaml file is in the correct directory. For macOS, it should be in ~/.warp/launch_configurations/ Launch Configurations (https://docs.warp.dev/features/sessions/launch-configurations).

  3. YAML format: The YAML format can be sensitive to spacing and indentation. Make sure your YAML is properly formatted. You can use a YAML validator to check for any syntax errors Launch search not finding any launch files (https://github.com/warpdotdev/Warp/issues/1827).

  4. Configuration content: Ensure that your launch configuration includes all required fields. For example, a title for each tab is mandatory Discord support thread: warp://launch/ not working (https://discord.com/channels/851854972600451112/1276931684046078135).

  5. Restarting Warp: Some users have reported that new launch configurations are not detected until Warp is restarted Restart required for new launch configurations to be detected (https://github.com/warpdotdev/Warp/issues/1759).

  6. Commands format: Make sure your commands are properly formatted. They should include the - exec: prefix Adding launch configuration programmatically doesn't work (https://github.com/warpdotdev/Warp/issues/3780).

#

If you've checked all these points and are still having issues, it might be helpful to share your YAML file contents (with any sensitive information removed) for further troubleshooting. There have been some reported issues with launch configurations not appearing even when they're in the correct directory, which could indicate a bug in Warp Launch configuration issue (https://github.com/warpdotdev/Warp/issues/2282).

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: