Add support for rprompt with Warp's custom prompt context chips

Open
#4,001 1 comment 19 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
cli

Research direction

Start by reviewing the linked Warp issue and comment, then identify the existing built-in prompt, rprompt, context-chip, and prompt-editor entry points. Define the scope for drag-and-drop chip placement and the behavior of chips in the rprompt; done means the requested configuration works consistently in the built-in prompt.

Written by the indexing model from the issue text.

Description

area:shell-terminal enhancement triaged
Describe the solution you'd like?
  • See https://github.com/warpdotdev/Warp/issues/2304#issuecomment-1869393351 - splitting this off into a new issue!
  • Introduce the ability to have a rprompt with Warp's built-in prompt
  • Introduce the ability to add context chips to this rprompt, via drag-and-drop with the Warp prompt editor
  • This would be very useful for long context chips such as the Git chip, which is only needed when starting to type a command and not during the command (so it can disappear as the user types into the rprompt).
  • Opening this feature request to track interest - please 👍 if you'd be interested in this feature!
Is your feature request related to a problem? Please describe.

Certain context chips, e.g. the Git chip, are too long and take up too much space, displaying content that I only need in a pre-command state e.g. my current branch.

How important is this feature to you?

3

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

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.