Why blocks matter
- Copy command only
- Copy output only
- Re-input prior commands
- Bookmark important terminal moments
- Share formatted output more cleanly
Warp is not just a prettier terminal. Its main advantage is that it turns terminal work into a more structured workflow using blocks, better editing, saved workflows, notebooks, prompts, and agents.
The right mental model is: Warp helps you think, edit, save, repeat, and collaborate around terminal work.
Warp’s official docs describe a block as the atomic unit that groups commands and outputs. Once you understand blocks, the rest of the interface becomes much easier to use.
Core shift: instead of one endless stream of text, Warp gives you structured command history you can copy, bookmark, re-run, and share.
Stop scrolling blindly. Select the block you need, inspect it, then copy, rerun, or save from there.
Warp’s input editor supports modern text editing behavior, which makes longer commands and edits much less painful than traditional terminals.
Edit before executing instead of treating terminal input as disposable.
The more complex your command line work gets, the more Warp’s editor becomes a real advantage.
Warp’s Command Palette and command search are central features. They help you find workflows, notebooks, prompts, shortcuts, files, sessions, and actions faster.
Warp Drive is the saved workspace for workflows, notebooks, prompts, and environment variables. These objects sync and are meant to be reusable and searchable.
Saved parameterized commands for actions you repeat. Best for repeatable command-line operations.
Saved parameterized natural-language instructions for Agent Mode. Best for repeatable AI-assisted tasks.
Runnable documentation with markdown, shell snippets, and searchable operating instructions.
Use when the task is command-first and predictable.
Use when the task is reasoning-first and still benefits from AI flexibility.
Notebooks are runnable documentation with markdown and executable shell snippets. They are useful for onboarding, ops playbooks, setup docs, and repeatable procedures.
If someone else would benefit from a sequence of commands plus explanation, it should probably be a notebook.
Warp’s current agents can write and edit code, debug issues, run commands, and automate workflows while using local environment context. They become stronger when you give them rules and codebase context.
Current Warp docs describe reusable rules for coding standards and project conventions, and codebase context for indexing local Git-tracked repositories so agents understand the real project.
AGENTS.md or WARP.mdWarp is best when you combine terminal execution with saving and reuse. Do the task once, then decide whether it should become a workflow, prompt, or notebook.
The most common failure is using Warp exactly like a plain terminal and never using the features that make it different.
These are the fastest ways to feel the benefit of Warp.
Save your most common run, test, build, and open commands as workflows with parameters where needed.
Create a notebook for machine setup, project setup, or deployment steps so you stop reconstructing the same process.
Save a reusable prompt that tells the agent to inspect current changes, find issues, and summarize risks.
Good Warp question: "I run this workflow often. Should this be a saved Workflow, a Prompt, or a Notebook?"
Use this guide to decide which Warp features matter for your real work.
These official Warp docs are worth reading after this HTML guide.