Article URL: https://www.warp.dev/blog/introducing-the-warp-agent-cli-coding-agent Comments URL: https://news.ycombinator.com/item?id=49171766 Points: 50 # Comments: 18

Today we are excited to launch the Warp Agent CLI, a new standalone CLI that lets you use the Warp Agent anywhere. It’s the same multi-model agent that’s built into Warp Terminal, now available in Ghostty, iTerm 2, VSCode, the built-in Windows terminal, or whatever terminal you prefer. The Warp Agent CLI has everything you’d expect from a modern CLI coding agent: it’s a multi-model, cost-optimizing harness built for pro developers. Out of the box, you get access to frontier and open-weight models and auto-routing based on task complexity. The CLI was truly built to fix gaps we were seeing with other agentic CLIs related to how well they integrate with the shell itself— especially important for developers doing real work in the terminal. Technically, we accomplished this by building the CLI agent on top of Warp’s unique terminal infrastructure: think of our CLI agent as a built-in mux’er across agent sessions. This allows more natural interactions, like being able to switch directories in agent sessions, have the agent drive full-screen terminal commands (e.g. sqlite and mysql), and even run across ssh sessions with no remote binary install. Let’s dive into the features that make the Warp Agent CLI extremely useful for folks who live in the terminal. The Warp Agent CLI has a unique mux’ing architecture. Within an agent session, we are actually running and managing pty connections with a layer of indirection between the agent and the underlying shell, a similar architecture to how tmux works. The mux’ing is managed by Warp’s terminal infrastructure, so our agent is natively aware of terminal inputs and output (what we call “blocks” in Warp). This allows for a richer experience than any other CLI agent. Here are some of the features it unlocks. The Warp Agent CLI lets you switch directories while in an agent session, and even run agents on remote machines without installing remote binaries. This is all because the agent session continues even when the base “state” of the session changes. Persistent sessions are useful when you are working across multi-repo projects, or when you want agent assistance on cloud machines where you might have limited permissions to install software.