vev vs Warp
Warp made a beautiful terminal. It also made an account mandatory and a cloud dependency permanent. Pick your trade-off.
| feature | vev | Warp |
|---|---|---|
| Account required | no | yes |
| Works offline | fully | degraded — blocks and AI off |
| AI runs where | your provider, BYOK | Warp's cloud |
| Keystroke telemetry | off, period | opt-out, default on |
| Source model | binary + opt-in plugin SDK | closed |
| Binary size | 5MB | ~150MB |
| Cold start | <40ms | 600ms-1.2s |
| SSH fleet manager | yes | limited |
| P2P file transfer | yes | no |
| Notebooks | yes | Warp Drive (cloud-synced) |
| Pricing | $99/yr Pro · $199 lifetime | freemium + AI-metered |
No account is not a feature. It's an absence.
It means there is no password reset email. No TOS update. No server-side outage that breaks your ls. No product manager on the other end deciding which commands are worth remembering.
vev runs on your laptop, reads your disk, writes its config to ~/.config/vev/, and shuts up.
yes, warp's block UI is nice
It is. We took the good parts — selectable command blocks, AI over output — and dropped the cloud tether. Your blocks live in ~/.local/share/vev/blocks/. You can grep them. You can delete them. No sync button, no account boundary, no share-dialog you didn't ask for.