Adding launch configuration programmatically doesn't work

Open
#3,780 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker-compose, rust, yaml, zsh
Domain
cli, desktop

Research direction

Start by tracing how ~/.warp/launch_configurations/local-env.yaml is loaded, comparing it with a launch configuration saved from inside Warp. Verify the configuration appears in the launch configurations tab and can be opened through Raycast and the URI scheme; the four tabs should then open as expected.

Written by the indexing model from the issue text.

Description

area:launch-configs bug ready-to-implement triaged
Discord username (optional)

techn0will

Describe the bug

I'm trying to write a tool to allow my team members to run the local environment for a project we're working on. The idea is we have a script to replace the LOCAL_ENV with the cwd absolute path name (yes, this works as expected), and copy the file into the ~/.warp/launch_configurations/local-env.yaml. However, I cannot see the new configuration file in the launch configurations tab, nor launch from raycast, nor use the uri scheme to open. This does work with a test launch config saved from inside the Warp app, in all use cases stated above. I was wondering if my configuration wasn't correct, or if this feature isn't supported yet?

To reproduce

Copy this into ~/.warp/launch_configurations/local-env.yaml

---
name: local-env launch configuration
windows:
  - tabs:
      - title: docker
        layout:
          cwd: __LOCAL_ENV__
          commands:
            - docker compose up

      - title: config-fairy
        layout:
          cwd: __LOCAL_ENV__
          commands:
            - task config-fairy:run

      - title: event-api
        layout:
          cwd: __LOCAL_ENV__
          commands:
            - task event-api:run

      - title: processors
        layout:
          cwd: __LOCAL_ENV__
          commands:
            - task processors:run

      - title: scrapers
        layout:
          cwd: __LOCAL_ENV__
          commands:
            - echo "to use the scrapers, run `task scrapers:run`"

Replace __LOCAL_ENV__ with an absolute path in your directory.

Expected behavior

4 new tab windows to open (I know the scripts won't work on your testing machines). At the moment none of them work.

Screenshots
CleanShot 2023-10-15 at 18 47 02@2x CleanShot 2023-10-15 at 18 47 17@2x
Operating system

MacOS

Operating system and version

13.0.1 (22A400)

Shell Version

zsh 5.8.1 (x86_64-apple-darwin22.0)

Current Warp version

v0.2023.10.10.08.06.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

N/A, the issue only applies to a Warp specific feature. (i.e. Warp AI, Workflows)

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.