Summary: Warp is no longer “just a pretty terminal.” It is an agentic development environment: a modern terminal, a built-in Warp Agent that runs real shell commands with your approval, a Warp Agent CLI you can run in any terminal, and optional cloud agents / factories for unattended work. This playbook shows three daily workflows verified against Warp’s docs and pricing page on 2026-11-05 — start an agent conversation in the app with sensible permissions, run the same agent from the CLI, and reuse Drive prompts plus notifications — then helps you pick Free, Build, or Max without inventing limits.
What Warp is now (terminal + Warp Agent + cloud at a glance)
Warp’s documentation describes the product as an agentic development environment. The pieces that matter for day-to-day work are:
- Warp terminal — a GPU-accelerated terminal for macOS, Windows, and Linux with block-based output, modern editing, and the surface where Agent Mode lives.
- Warp Agent — Warp’s built-in coding agent. It runs multi-step tasks by executing commands in a real terminal, reading live output, and asking you before risky actions land. The same agent is available in the Warp app, via the Warp Agent CLI in any terminal or over SSH, and as a cloud agent on Warp’s Automation Platform.
- Cloud agents and Factories (high level) — cloud agents run in the background from a trigger, schedule, or integration without keeping a local session open. Warp Factories sit on top of that platform when you want a team of cloud agents to triage, implement, review, and verify work. This playbook stays on local daily use; cloud and factories are the next layer once the local agent habits stick.
Official docs stress that context follows the agent: Rules, Skills, MCP servers, and Codebase Context apply the same way in the app, the CLI, and the cloud. You approve commands and review diffs before changes land, and you can dial autonomy up or down with Agent Profiles. See the official screenshots at the end of this post for the Profiles and Permissions UI.
Playbook 1: Daily agent work inside the Warp app
This is the highest-signal path if you already live in Warp as your terminal.
Install and open Warp
Platform support from the install guide: macOS (Intel and Apple silicon, 10.14+ with Metal), Windows 10 version 1903+ or Windows Server 2022+, and Linux with glibc >= 2.31 plus OpenGL ES 3.0+ or Vulkan.
- macOS: download from warp.dev/download or
brew install --cask warp. - Windows: download the installer or
winget install Warp.Warp. - Linux: use the package for your distro from the download page (deb / rpm / pacman / AppImage and others).
Sign in with a Warp account. Agent Mode replaced the older AI chat panel; starting an AI query opens a conversation tied to your session.
Start a conversation and keep related work together
- Open a project directory in Warp (
cdinto a Git repo, or open the folder from the file tree). If Codebase Context is enabled, Warp detects the Git repo and begins indexing; check Settings > Code > Indexing and projects until status shows Synced. Free plan indexing supports up to 5,000 files per repository; larger repos need ignore files or a higher plan. - Start a new Agent Mode conversation: on macOS press
⌘+Enter(or use/new); on Windows/Linux pressCtrl+Shift+Enter. You can also open the Conversations menu (⌘+Y/Ctrl+Shift+Y) and choose New Conversation. - Ask in plain language about the repo, for example “Explain the architecture of this project” or “What are the main entry points?” When Codebase Context is synced, answers should cite real files rather than generic guesses.
- Keep follow-ups in the same conversation when the next question builds on the last answer. Start a fresh conversation for unrelated work — long threads get slower and noisier. Queue follow-ups while the agent is still working if you use prompt queueing.
Set permissions so “approve” means something
Go to Settings > Agents > Profiles. Each profile sets base model, autonomy, and tool access. Permission types include applying code diffs, reading files, creating plans, executing commands, interacting with running commands (Full Terminal Use), and asking clarifying questions.
Autonomy levels documented by Warp:
- Agent Decides — acts when confident, asks when uncertain.
- Always ask — explicit approval every time (good for sensitive actions).
- Always allow — no confirmation for that action type.
- Never — the agent will not take that action.
Two gotchas the permissions docs call out explicitly:
- The Command denylist beats “Always allow.” Default denylist patterns include things like
curl,wget,rm, andeval. If the agent keeps asking about those, check the denylist before you crank every permission to Always allow. - Run until completion (auto-approve for the current task:
⌘+Shift+Ion macOS,Ctrl+Shift+Ion Windows/Linux) bypasses your personal denylist by default. To keep the denylist during auto-approve, turn off Allow auto-approve to bypass command denylist under Settings > Agents > Warp Agent > Input. Team denylist rules from the Admin Panel are never bypassed.
A practical daily profile: Always ask (or Agent Decides) for execute/apply-diff on production repos; allowlist only read-only patterns such as ls, grep, find, which, echo if you want fewer prompts without going YOLO.
Playbook 2: Same agent from any terminal via Warp Agent CLI
When you are on a remote box, inside another terminal emulator, or you simply do not want the full Warp app open, the Warp Agent CLI runs the same agent with warp.
- Install (install script preferred because it auto-updates): macOS/Linux
curl -fsSL https://app.warp.dev/download/agent-cli | bash; Windows PowerShellInvoke-RestMethod "https://app.warp.dev/download/agent-cli.ps1" | Invoke-Expression; or Homebrewbrew install --cask warp-agent-cli(Homebrew does not auto-update — usebrew upgrade --cask warp-agent-cliwhen prompted). - Verify with
warp --version. - Run
warp. The CLI shows a verification link and device code, opens the browser, and unlocks after you approve. Same Warp account as the app; the app itself is not required. For CI/headless use, preferWARP_API_KEY=...over putting the key on the command line. - Type a natural-language prompt such as
What does this project do?and press Enter. Approve or reject permission requests the same way you would in the app. - For a quick shell command without leaving the CLI, type
!on an empty input to enter Shell mode, run something likegit status, then Backspace on empty input to return to agent prompts. Optional:/natural-language-detectionclassifies recognized shell vs natural language as you type. - Exit with
Ctrl+Ctwice or/exit. The CLI prints a resume command:warp --resume CONVERSATION_TOKEN.
Free plan includes Warp Agent CLI access according to the public pricing page. Usage for Warp-provided models still draws from your allowance or pay-as-you-go balance; BYOK routes inference to your provider instead.
Playbook 3: Reusable Drive prompts and agent notifications
Once the agent is part of your day, two features reduce friction without requiring cloud factories.
Save parameterized prompts in Warp Drive
Warp Drive stores Workflows, Notebooks, Prompts, and Environment Variables for personal use or a team. Open Drive from the status bar, the web experience, or the side panel (⌘+\ on macOS, Ctrl+Shift+\ on Windows/Linux).
- In Warp Drive, click + and choose Prompt.
- Name it, write the natural-language query, and add arguments with
{{argument}}or “New argument” (names: letters, digits, hyphen, underscore; first character not a digit). - Run it later from Drive, or search the Command Palette / Command Search (type
prompts:to list prompts). UseShift+Tabto cycle arguments when the prompt is selected.
Good candidates: “summarize git diff for a PR description,” “generate conventional commit message from staged changes,” “explain failing CI log pasted as context.” Keep secrets in Drive Environment Variables rather than hard-coding them into prompt text.
Notice when the agent needs you
Warp Agent notifications work out of the box: Complete, Request (blocked on approval/input), and Error. You get toast notifications, a notification mailbox (bell icon), tab status badges, and desktop alerts when Warp is in the background. Third-party CLI agents (Claude Code, Codex, OpenCode) need a one-time notification setup documented on their Warp pages — skip that until you intentionally run those harnesses inside Warp.
How to choose: Free vs Build vs Max
Prices and inclusions below are taken from warp.dev/pricing and Warp’s plans/billing docs as of 2026-11-05. Check your own Settings > Billing and usage for the allowance that actually applies to your seat — existing seats can differ from new-plan marketing numbers.
| Plan | Price (USD) | Agent usage included | Key limits / features (from pricing + docs) |
|---|---|---|---|
| Free | $0 / month | No bundled Warp Agent usage; pay-as-you-go for Warp-provided inference (purchases priced at a premium) or BYOK | Modern terminal; Warp Agent CLI access; bring your own AI inference*; limited cloud agents; limited Warp Drive / collaboration; limited cloud conversation storage; Free codebase indexing up to 5,000 files per repository |
| Build | $20 / month (monthly) or $18 / month when billed annually | $20 of agent usage included each month at API rates; add-on usage, auto-reload, team-wide spend cap | Everything in Free, plus full Warp Agent access (frontier and open-source models from OpenAI, Anthropic, z.ai, and more); extended cloud agents; highest codebase indexing limits; unlimited Warp Drive objects and collaboration; unlimited cloud conversation storage; private email support |
| Max | $200 / month (monthly) or $180 / month when billed annually | $200 of agent usage included each month (10× Build); add-on usage, auto-reload, team-wide spend cap | Everything in Build, with the larger included usage pool |
*Bring Your Own API Key (BYOK) is documented for Free and eligible paid plans for individuals and organizations with 10 or fewer employees (Anthropic, OpenAI, or Google keys). Larger orgs need Business/Enterprise with team-managed keys. ChatGPT consumer subscription linking is supported for eligible OpenAI models; Claude consumer subscriptions are not — use an Anthropic API key via BYOK instead.
Decision shortcuts: stay on Free if you mainly want the terminal, light agent trials, and BYOK. Move to Build when you want a predictable $20/month included pool at API rates plus unlimited Drive collaboration. Choose Max when you are burning through Build’s included usage every month and want the 10× pool without constantly buying add-ons. Team SSO and admin controls start at Business ($50/user/month monthly, $45 annual on the pricing page) — outside the personal Free/Build/Max choice.
Included usage resets monthly even on annual subscriptions and does not roll over. Purchased usage is separate and rolls over until its original 12-month expiration. Regular shell commands and non-AI terminal features do not consume agent usage; Generate and AI Autofill in Workflows do.
Editor’s note
Who this is for: developers who already live in the terminal and want an agent that runs real commands with visible approvals — not a separate chat tab you copy-paste into. Especially useful if you hop between laptop and remote SSH sessions (app + Agent CLI).
Who this is not for: people who only want a hosted no-code agent builder, or orgs that need SAML SSO and admin-managed BYOK on day one (look at Business/Enterprise instead of Free/Build/Max).
Gotchas verified in docs: (1) Denylist overrides Always allow — remove curl/rm patterns or expect prompts. (2) Run until completion bypasses personal denylist unless you disable that bypass. (3) Free has no bundled agent usage — BYOK or paid usage purchases required for sustained Warp-hosted inference. (4) Homebrew Agent CLI installs do not auto-update. (5) “Monthly request/credit limit exceeded” means check Billing and usage, then buy usage, enable auto-reload, switch to BYOK, or wait for the monthly reset.
Related on this blog: if you compare agentic editors and CLIs, see our Raycast AI playbook, Zed AI tutorial (agent panel + own keys), and Claude Code error fixes.
FAQ
Q1. Does the Free plan include Warp Agent CLI?
Yes. The public pricing page lists Warp Agent CLI access on Free. Free does not include bundled Warp Agent usage for Warp-provided models; use pay-as-you-go purchases (at a premium) or bring your own inference.
Q2. Can I bring my own LLM API key?
Yes. Warp documents BYOK for Anthropic, OpenAI, or Google keys on Free and eligible paid plans for individuals and organizations with 10 or fewer employees. Larger organizations need Business or Enterprise with team-managed keys/endpoints. Your provider bills that inference separately; Warp may still meter compute/platform for eligible cloud runs.
Q3. Why does the agent still ask before running curl or rm?
Those commands match the default Command denylist. The denylist takes precedence over Always allow and over Agent Decides. Edit the denylist under Settings > Agents > Profiles, or use Run until completion knowing it bypasses the personal denylist by default unless you change the Input setting.
Use Warp as your daily terminal first, then let Agent Mode take the repetitive investigation and patch loops under permissions you actually understand — that combination is the playbook, not a bigger subscription by default.
Last verified: 2026-11-05
Sources:
- Warp pricing
- Warp docs llms.txt index
- Agents overview
- Profiles & Permissions
- Agent Notifications
- Warp Agent CLI quickstart
- Interacting with agents
- Agent model choice
- Agent FAQs (BYOK, limits)
- Installation and setup
- Warp Drive overview
- Warp Drive prompts
- Plans, pricing, and refunds
- Usage and billing
- Codebase Context
Image credit: official Warp docs screenshots (Agent Profiles, Permissions, toast notification) from docs.warp.dev Astro assets, plus an own screenshot of the public warp.dev/pricing page — captured 2026-11-05. See the official screenshots at the end of this post.
댓글
댓글 쓰기