warpdotdev / warpdotdev/warp

Can I access shell variables in my warp launch config?

Open
#4,171 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:launch-configs enhancement triaged
Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Description

Discord username (optional)

No response

Describe the solution you'd like?

I would like to open a bunch of windows / run commands using environment variables instead of hardcoded paths. The hardcoded paths also make launch configurations difficult to share with a team.

Is your feature request related to a problem? Please describe.

No response

Additional context

No response

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

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.

Research direction

Start by locating Warp's launch configuration entry point and the code that handles configured windows and commands. Check whether environment-variable expansion already exists, then define how variables should be resolved and verify that shared configurations can replace hardcoded paths without changing existing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.