lucieleblanc
commented
2 weeks ago Thanks for reporting this! It looks like Warp's natural language auto-detection falsely categorized "history" as natural language, when it should have been interpreted as a command. There's a dedicated link to report these errors here.
In the meantime, there's an autodetection denylist in the Settings menu, under "AI" > "Agent Mode" > "Natural language denylist" (see docs). Does adding history to that list solve the issue?
Dupe Check
Describe the bug
When you type history in the terminal of an SSH session in linux to view previous commands it auto goes into AI and you cant execute the command.
To reproduce
command in SSH session: $ history
Expected behavior
No response
Screenshots
Operating system
Linux
Operating system and version
deb 12
Shell Version
bash or zsh
Current Warp version
latest
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?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None