Support PROMPT_COMMAND, to enable saving history across sessions

Open
#2,380 1 comment 2 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
bash, rust
Domain
cli

Research direction

No file or test is named in the issue. Begin by locating Warp's shell-integration entry point and how Bash prompt hooks are handled, then compare the expected behavior with the linked PROMPT_COMMAND examples. Done means users can configure PROMPT_COMMAND so commands are captured across sessions without losing existing history behavior.

Written by the indexing model from the issue text.

Description

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

No response

Describe the solution you'd like?
Having a list of all commands run on a host is useful for remembering how to perform actions, or how you achieved a certain result. Prior to Warp, I achieved this using PROMPT_COMMAND (example of how this is recommended to be set up in https://www.digitalocean.com/community/tutorials/how-to-use-bash-history-commands-and-expansions-on-a-linux-vps and https://unix.stackexchange.com/questions/1288/preserve-bash-history-in-multiple-terminal-windows). 

Warp does not support the PROMPT_COMMAND environment variable, and I've found no way to have an extra command invoked on each command run.
Is your feature request related to a problem? Please describe.

No response

Additional context

No response

How important is this feature to you?

2

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

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.