Warp integrates Auggie and Pi agents

Warp is turning its terminal into a host for outside coding agents, not just its own built-in assistant. The company said on social media that Warp now supports Augmentcode’s Auggie and Pi agents inside the terminal. (x.com) Warp also said it added customizable toolbars for Agent mode, the chat-style view it uses for longer agent workflows. Warp’s documentation says Agent mode already includes controls such as model selection, voice input, image attachments, and conversation history. (x.com) (docs.warp.dev) Auggie is Augmentcode’s command-line coding agent. Augment’s documentation says Auggie runs in a terminal session, understands a codebase, and can analyze code, make edits, and automate routine tasks through natural-language prompts. (docs.augmentcode.com) (github.com) Warp’s own pitch has moved in the same direction for months. In June 2025, Warp launched Warp 2.0 and called itself an “Agentic Development Environment,” combining a modern terminal with coding agents that can build, test, deploy, and debug code. (warp.dev) (docs.warp.dev) The product already separates plain command entry from agent work. Warp’s documentation says Terminal mode keeps the interface closer to a traditional shell, while Agent mode opens a dedicated conversation view for multi-step tasks. (docs.warp.dev 1) (docs.warp.dev 2) That matters because the new integrations slot into controls Warp already exposes. Warp says developers can speak to agents with Voice instead of typing, and can attach screenshots or other images so an agent can use visual context when generating responses. (docs.warp.dev 1) (docs.warp.dev 2) Warp has been steadily adding more agent features around that interface. In November 2025, the company introduced “Agents 3.0,” including full terminal use, a planning command, interactive code review, and integrations with Slack, Linear, and GitHub Actions. (warp.dev) The Auggie and Pi support pushes Warp further toward being an agent hub inside the terminal, rather than a terminal tied only to Oz, Warp’s in-house agent system. Warp’s documentation describes Oz as the orchestration layer for its cloud agents, while the new posts show the company opening that workspace to third-party agents too. (docs.warp.dev) (x.com) For developers, the practical change is simple: the same terminal window is becoming the place to run commands, review code, talk to agents by voice, and attach images when text is not enough. Warp’s latest posts suggest the company is now competing on interface and workflow control as much as on the underlying model. (docs.warp.dev 1) (docs.warp.dev 2)