Warp Keyboard Shortcuts
Warp's defining structural difference from a traditional terminal is its Blocks system — each command and its output are grouped into a distinct, individually selectable and shareable unit rather than one continuous scrolling text stream, and several of its shortcuts exist specifically to navigate and manipulate these blocks rather than raw terminal text. Beyond that structural innovation, Warp layers in AI-powered natural-language command search and suggestion, plus modern text-editing conventions (multi-cursor-like input editing) borrowed more from code editors than traditional shell input handling. Being currently Mac and Linux-focused with Windows support in active development, shortcuts below reflect the Mac/Linux release. Developers who spend hours a day pairing on shared infrastructure or debugging together remotely find Warp's Block-sharing feature solves a genuinely recurring annoyance with traditional terminals — pasting a wall of unformatted scrollback into a chat message to show a teammate an error, versus generating one clean shareable link to exactly the command and output in question, is a meaningfully different experience once you're used to it. This page is aimed at developers already comfortable in a traditional terminal who are evaluating or actively using Warp specifically for its Block-based model and AI features, rather than someone brand new to command-line work generally, since most of what's distinctive here builds on top of, rather than replaces, standard shell fluency. If you're switching from iTerm2, Terminal, or a Linux terminal emulator, expect your existing shell configuration and muscle memory for typing commands to transfer directly, with the genuinely new habits concentrated in Block navigation and the AI-assisted search features covered below.
Block Navigation
| Action | Windows | Mac | Description |
|---|---|---|---|
| Jump to next Block | — | Cmd+Down | Moves selection to the next command Block, Warp's grouped unit of a command plus its output, letting you navigate command history structurally rather than by raw text scrolling. |
| Jump to previous Block | — | Cmd+Up | Moves selection to the previous command Block, the reverse companion to next-Block navigation. |
| Copy entire Block (command + output) | — | Cmd+Shift+C (Block selected) | Copies the selected Block's full command and output together as one unit, useful for sharing a complete command-and-result pair (in a bug report or documentation) rather than manually selecting and copying scrolling terminal text. |
| Share Block as a link | — | Click share icon on Block, no default key | Generates a shareable web link to a specific command Block's content, a Warp-distinctive collaboration feature for sharing terminal output with teammates without manually copying and reformatting text. |
| Collapse/expand a Block's output | — | Click collapse arrow on Block, no default key | Toggles whether a Block's output is fully shown or collapsed down to just its command line, useful for tidying up a long session's scrollback after a verbose command has already served its purpose and doesn't need to stay fully expanded. |
| Select current Block | — | Cmd+Click on Block, or Shift+Up/Down to extend | Explicitly selects a Block (or extends selection to adjacent Blocks) as a distinct action from simply clicking into it to position your cursor, useful before running a bulk action like copy or delete across more than one Block at once. |
Command Input
| Action | Windows | Mac | Description |
|---|---|---|---|
| Open Command Palette | — | Cmd+P | Opens Warp's own Command Palette, a fuzzy-search entry point into terminal settings, theme switching, and app-level commands generally, modeled on the same command-palette idea popularized by modern code editors. |
| Clear current input line | — | Cmd+U | Clears the currently typed but unexecuted command from the input line, standard terminal line-clearing behavior. |
| Search saved Workflows | — | Cmd+Shift+R | Opens search across Warp's Workflows feature — saved, reusable command templates with fillable parameters — letting you quickly find and run a frequently repeated complex command without retyping or remembering its exact syntax. |
Ai Search
| Action | Windows | Mac | Description |
|---|---|---|---|
| AI natural-language command search | — | Cmd+` (or # prefix in input) | Opens Warp's AI-powered command search, letting you describe what you want to do in plain English (like 'find all files larger than 100MB') and receive a suggested actual shell command to run, rather than needing to recall exact command syntax and flags from memory. |
| AI: Explain this command | — | Right-click command or Cmd+I in some flows | Requests an AI-generated explanation of what a specific command or command block actually does, useful for understanding an unfamiliar command encountered in documentation or copied from an external source before running it. |
Frequently Asked Questions
What's the actual point of grouping commands into Blocks instead of a continuous scroll?
Blocks give each command and its output a discrete, individually addressable identity — selectable, copyable, and shareable as one unit — which solves a genuinely common terminal pain point of trying to precisely select just one command's output from a long, continuously scrolling wall of undifferentiated text, especially when several commands' outputs run together visually with no clear separation.
Is Warp's AI command search sending my terminal activity to an external server?
Using the AI-powered natural-language command search and command-explanation features does send the relevant query or command text to Warp's AI service for processing, which is worth being aware of for anyone working with sensitive or proprietary command content — Warp's own documentation and privacy settings address exactly what is and isn't sent, and the AI features are generally optional rather than required for basic terminal usage.
Why is Warp not yet available as a full native Windows release?
Warp was built initially targeting Mac and Linux, with its underlying Rust-based rendering engine developed and optimized for those platforms first — Windows support has been in active, publicly acknowledged development, but as of the most recent releases remains behind Mac and Linux in availability and feature parity, which is worth checking directly against Warp's own release notes for the most current status.
Does sharing a Block as a link expose any sensitive information beyond what's visibly shown in that command's output?
The shared link is generated from the visible content of the specific Block, so it shouldn't include unrelated scrollback or system information beyond that command and its output, but it's still worth reviewing the actual output content before sharing, since command output itself can sometimes include sensitive details like file paths, environment variable values, or internal hostnames that you may not want posted publicly.
Are Warp Workflows shared automatically across a team, or are they personal by default?
Workflows can be personal, stored locally for an individual's own reuse, or shared with a team depending on how they're set up and Warp's team/workspace features being used — a personal Workflow for a repeated local dev task and a team-shared Workflow for a standardized deployment command serve different purposes and are configured differently rather than existing under one single sharing model.
Does Warp support the same shell configuration (zsh, bash, fish) I already use, or does it require switching shells?
Warp runs as a terminal emulator on top of whatever shell you already have configured on your system — zsh, bash, fish, or others — so your existing shell configuration, aliases, and prompt customization continue working exactly as before, since Warp's Blocks and AI features are layered on top of the terminal experience rather than replacing the underlying shell itself.
What's the difference between clicking into a Block and explicitly selecting it?
Clicking into a Block's output or command area simply places your text cursor there, functioning much like clicking anywhere in a normal terminal for copying a snippet of visible text. Explicitly selecting the Block itself (Cmd/Ctrl+Click, or extending with Shift+Up/Down) treats the entire Block as one selected unit, which matters when you want to copy, collapse, or share the whole command-and-output pairing rather than just a fragment of visible text within it.