Add Option to Display SubShell Above/inline of Warp Prompt

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust, shell
Domain
cli

Research direction

The issue does not name any files, tests, or implementation entry points. Start by locating Warp's prompt rendering and subshell handling, then clarify the display format and how the active subshell context is identified; done means the prompt visibly distinguishes subshell contexts without requiring extra commands.

Written by the indexing model from the issue text.

Description

area:shell-terminal enhancement triaged
Discord username (optional)

No response

Describe the solution you'd like?

Warp Team,

I would love to have the option to display in my prompt that I am in a SubShell so that I can see what context I am currently using in the given SubShell. This would be especially helpful for those of us who are popping SubShells with specific commands, i.e. when creating a subshell through AWS-Vault to assume roles, or if someone is operating in a network namespace.

A few options I had for display could be:

(SubShell) $ username@warp ~

(SubShell: <command to get subshell>)
$ username@warp ~

This would be extremely helpful to me because I constantly am changing subshells throughout my workday to access various cloud resources, and it can be confusing without running additional command(s) to remember which context I would be in at that given time

Thanks Team!

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

No response

Additional context

No response

How important is this feature to you?

4

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

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
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.