Warp.dev Terminal – Overpriced, Buggy, and AI-Sabotaged My Code
I used Warp.dev on the Business Plan. Blew through usage limits in 3 days, and suddenly I’m being charged for over-usage. Even after disabling that, their LITE version (supposedly "unlimited tasks") is borderline unusable.
The AI started actively breaking working code after I hit the limit. Repeated errors, no learning, and corrupted scripts. It destroyed bots I had already built.
Anyone else feel this service is more hype than functionality?
I find it mad people use this stuff outside of a vm or virtualisation.
Everything reinforces my choice of Aider+Openrouter+code. I use models 20x cheaper than Sonnet, completely pay as you go, nobody is playing games with models, their LLM bills and my context to turn a profit. I generate Python scripts with Mongo and Cloudwatch queries instead of getting angry at the mystical sparkly button UX on their apps.
I would really like to learn more about your setup. Can you share details?
I actually had good results with the free plan but with strong edit limitations (which I explicitly prompt for). Its the same underlying models as cursor (claude 4 is by far the best) and I find it a little easier to use because it takes up the full screen and is less eager than cursor somehow.
I installed this, lasted about 90 seconds on my machine before I went back to iTerm.
Nearly everything about the experience of a terminal is better than iTerm though? I turned off all of the AI stuff since I can just use Claude directly for one off things. But it's very nice having the terminal treated like a text file instead of terminals pretending the mouse doesn't exist and there have been no advancements in text editing GUI in decades. It has issues with ssh ing into one machine but I just use command ssh for that single machine.
[dead]
Yep. Exactly as described, pure hype.
"AI started actively breaking working code" is vibe coding talk, you should monitor what it does and undo at the step that breaks. I've been able to do that just by prompting "undo last step/<specific action>"
I used it before as a free Claude Code to do ad-hoc scripting, pretty useful. Now I have found a bunch of TUI programs (Amazon Q, rovo dev, opencode) that can assist with that kind of workflow. I don't like that it's a GUI app, but I like the fact that it's a terminal app where I can type command directly into, not just prompt. Claude 4 should be fine, was on free, never hit limit so not sure what's the lite experience is.
I've found Claude to be terrible at undoing.
It feels analogous to what would happen if you put me in front of a broken project without source control that I've never seen before and asked me to fix it without giving me enough time to actually understand it. It starts from errors and bugs, guesses corresponding source code, and tries to narrowly fix just that snippet. Generally it favors deleting, but not specifically deleting new code.
I would have thought it could record a log of its actions and use that log to think about undoing. I would also think it could annotate lines with git blame so it knows undoing wouldn't involve changing anything more than say a day old. Unfortunately that isn't consistent with what I've seen.
I just make a WIP git commit and run git commit -A --amend --no-edit after manually reviewing each unit of work.
Edit: I also wish Claude implemented undo at a higher level instead of relying on the model. Some combination of snapshotting the whole repo and tracking operations that have precise inverses. But I understand that would have drawbacks.
I agree - people saying that kind of stuff I just can’t take seriously. Programmers know to use revision control systems, practically from the start of their being programmers. For the same reason: because you can break your own code. Not using a vcs when letting ai make changes just doesn’t make sense at all. And them complaining ai broke their code means they broke their code.
why... would anyone want... AI in a terminal?
For the same reason someone want AI in their text editor and search results.
It's faster than poring thru bad manpages for commands you don't remember.
I must be very old school then. I am 30 years old, but I still read man pages often, whether I am writing C code, or just use an utility. It is a choice, however. I do not care if people use LLMs for this.
Sure it's way easier to type "show me the list of files in current directory" and wait for LLM to do it's magic than it is to type "ls".
the same people open a bare terminal and immediately jump into Claude Code