Had Warp agent mode open in a split pane on macOS. Left pane was my local Next app. Right pane was SSH into a staging box.
I asked it to clear node_modules and reinstall. It ran rm -rf node_modules in the SSH pane.
Staging is fine (we rebuild from image) but my heart rate is not. Is there a "confirm before run on remote" toggle I'm missing, or do people just never split agent + SSH?
Indexed our Nx monorepo Friday. Context looked solid until it auto imported lodash/get from a package we yanked in July. CI went green because the test suite never touches that path. Review caught it…
Recorded a 12 min founder update Thursday. Overdub on the Pro plan ($24/mo) kept inserting my March cold voice on every cut. I re trained the clone twice. Still got that rasp on the last 40 seconds.…
Gave Augment a week on our Go monorepo ( 1.8M LOC, lots of internal packages). Indexing took most of Tuesday. After that it was weirdly good at finding the right service — way less "here's a helper f…
5 comments
Join the discussion
Log in to comment.
yeah i did the same thing last month except it was
drop databaseon a preview env. warp is great until the agent forgets which pane has focus.i just stopped ssHing inside warp when agent mode is on. separate iterm window for remote now. boring but my saturday nights are quieter.
I keep an allowlist for agent mode now. Anything that can nuke state (
rm -rf,drop,kubectl delete) needs a keypress.Separate SSH client is the boring fix. Still use Warp for local, just not for remote while the agent is awake.
wait does Warp even show which pane the agent is bound to? i keep thinking its always the focused one but after reading this im not sure.
had a milder version friday — agent ran
pnpm installlocally while i was staring at the remote logs pane. nothing broke, just confusing. a confirm step for remote hosts would save a lot of people.yeah. i screenshot the pane title before every agent run now which is ridiculous for a $20/mo tool.
if it highlighted the bound pane in red for remote hosts i'd stop doing that. until then, iterm for ssh.
This is a blast radius problem, not a UX quirk.
If the agent session can see an SSH pane, assume it will eventually run there. Confirm dialogs help. Session-scoped host allowlists help more. Pane focus is not a security boundary.