Warp Agent CLI: The Terminal Agent That Does What Others Can't
The Warp Agent CLI
Warp has launched a standalone CLI version of its Warp Agent, bringing its multi-model coding agent to any terminal—Ghostty, iTerm 2, VS Code, and more. Built on Warp's terminal infrastructure, it natively multiplexes agent sessions, enabling persistent sessions across directory changes and remote machines without installing binaries. It can drive full-screen apps like sqlite and vim, auto-detects shell commands vs. prompts, and supports multi-agent orchestration and cloud handoff. The CLI includes cost-optimizing model routing and custom routers.
The Warp Agent CLI has a unique mux'ing architecture: within an agent session, we actually run and manage pty connections with a layer of indirection between the agent and the underlying shell, similar to how tmux works.
- lexicality
I used to really like Warp, back when it was just a terminal. Then as they went more and more in on AI the actual terminal features became more and more buggy and I ended up having to go back to WezTerm.
Why is every company seemingly trying to re-implement agents themselves rather than making their product work with the existing ones?
- ArvidSu
My absolute favorite thing about Warp is the function that suggest a new command intelligently when the one I just ran failed or changes to the code when execution failed. Haven't been able to replicate that as smoothly in Ghostty which I really want to enjoy but honestly haven't really felt the same delight I got from Warp.
- Jonovono
The other day in warp I literally couldn't run `ls` because it kept interpreting it as a AI command. I still love warp, but some of the stuff is crazy.
- daveidol
So this is a competitor to something like OpenCode or Pi? I suspect for most developers, they are using Claude Code or Codex CLI mainly just so they don't have to pay-per-token and can use the subscription products - which I assume can't be done with Warp Agent?
- giancarlostoro
> Cloud agent handoff
> Start work in the CLI, then hand it off to the cloud when you want to close your laptop. All cloud agents are tracked centrally and can be monitored and steered via the web so you can continue work on the go.
They hype up not needing a third party binary to remote and run agents against SSH'ed systems, but how does this "cloud agent" work then? Are they shelling you through their own back-end? Because that sounds bad and probably wrong? Maybe its a different use case.