底座 · 大多数人停在的那层The Base · The Layer Most People Stop At.
Blocks（命令加输出成一块）、现代输入编辑、补全、命令面板、主题 —— 这是 Warp 最先让你眼前一亮的一层，也是九成用户唯一用到的一层。它值得开，但它不是 Warp 是元工具的理由。这章讲这层各自省什么、哪些值得改习惯，以及什么时候一个普通终端、iTerm、tmux 就够，不必为它纠结。Blocks (a command plus its output as one unit), a modern input editor, completions, the command palette, themes — this is the layer that first makes Warp feel nice, and the only layer nine in ten users ever touch. It is worth turning on, but it is not the reason Warp is a meta-tool. What each part saves, which are worth a habit change, and when a plain terminal, iTerm, or tmux is enough.
这一章讲你已经在用的那层 —— Blocks、现代编辑、补全、命令面板、主题。九成 Warp 用户只用到这里就停了。它确实比上一个终端顺手，但这章的目的不是教你用它，是替你判断：这层里哪些值得改习惯，哪些不必，以及它为什么不是你留下 Warp 的理由。This chapter is about the layer you already use — Blocks, the modern editor, completions, the command palette, themes. Nine in ten Warp users stop right here. It really is smoother than your last terminal, but the point of this chapter isn't to teach it — it's to judge for you: which parts here are worth a habit change, which aren't, and why this layer isn't the reason you keep Warp.
— I
Block 是后面一切的起点The Block Is Where Everything Later Starts.
Block 把「一条命令加它的输出」做成一个可定位的单元 —— 这一步不起眼，却是后面所有能力的地基。A Block turns 'a command plus its output' into one addressable unit — an unremarkable move that is the foundation everything later is built on.传统终端是一条连续往下滚的字符流，命令和输出混在一起，找上一条命令的结果要靠眼睛扒。Warp 把每次执行切成一块：你能单独复制命令或输出、跳到输出开头、重跑、带格式分享、给常用命令加书签。1注 1Note 1Warp Docs · Blocks —— 截至 2026-07-10，Block 把一条命令和它的输出合成可定位单元，可单独复制命令或输出、跳到输出开头、重新输入、分享、搜索、过滤、作为 agent 上下文。Warp Docs · Blocks — as of 2026-07-10, a Block groups one command and its output into an addressable unit; you can copy command/output, jump to output start, re-input, share, search, filter, and use Blocks as agent context.真正的意义在后面 —— agent 能「指着某一块」说话、Code Review 能把 diff 框起来、分享能精确到一次执行，全都因为输出不再是一片连续的流。底座这层最有价值的，就是这块结构本身。A traditional terminal is one continuous downward-scrolling stream, command and output mixed together, finding a past command's result a matter of scanning with your eyes. Warp cuts each run into a block: you can copy the command or output alone, jump to the output start, re-run, share with formatting, and bookmark frequent commands.1注 1Note 1Warp Docs · Blocks —— 截至 2026-07-10，Block 把一条命令和它的输出合成可定位单元，可单独复制命令或输出、跳到输出开头、重新输入、分享、搜索、过滤、作为 agent 上下文。Warp Docs · Blocks — as of 2026-07-10, a Block groups one command and its output into an addressable unit; you can copy command/output, jump to output start, re-input, share, search, filter, and use Blocks as agent context. The real significance comes later — the agent can talk about 'that block,' Code Review can frame a diff, sharing can point at a single run, all because output is no longer one continuous stream. The most valuable thing in the base layer is that block structure itself.把底座拆成几块看，别把它们混成「漂亮终端」四个字：Break the base into pieces; don't flatten it into 'pretty terminal':
底座功能Base feature
它省什么What it saves
什么时候够用When it is enough
Blocks
命令与输出混在一起的阅读成本Reading cost when commands and output are mixed
这层里真正值得为它改习惯的，是命令面板和现代输入编辑 —— 不是主题。In this layer, what's actually worth changing a habit for is the command palette and the modern input editor — not themes.输入编辑带语法高亮和多光标，长命令不再是一行黑字；补全把记参数的负担挪走；命令面板用一个键盘入口搜命令、workflow 和设置，省掉到处找。2注 2Note 2Warp Docs · Command Search —— 截至 2026-07-10，Command Search 面板统一搜索终端输入、保存的命令与 agent 对话历史，与历史、补全、YAML workflows、命令纠错同属 terminal/entry 一节（原 command-entry 路径已迁移）；Command Palette 有独立页面，用一个入口搜索 Warp 功能、workflow 与设置。Warp Docs · Command Search — as of 2026-07-10, the Command Search panel provides unified search across terminal inputs, saved commands, and agent conversation history, alongside history, completions, YAML workflows, and command corrections under the terminal/entry section (the old command-entry path has moved); Command Palette has its own page, one entry to search Warp features, workflows, and settings.这三样每天都用，值得花十分钟练进肌肉记忆。主题和外观好看，但它不改变你做事的速度 —— 别在那上面花一下午。The input editor brings syntax highlighting and multi-cursor, so a long command is no longer a black wall; completions move the burden of remembering flags off you; the command palette gives one keyboard entry to search commands, workflows, and settings.2注 2Note 2Warp Docs · Command Search —— 截至 2026-07-10，Command Search 面板统一搜索终端输入、保存的命令与 agent 对话历史，与历史、补全、YAML workflows、命令纠错同属 terminal/entry 一节（原 command-entry 路径已迁移）；Command Palette 有独立页面，用一个入口搜索 Warp 功能、workflow 与设置。Warp Docs · Command Search — as of 2026-07-10, the Command Search panel provides unified search across terminal inputs, saved commands, and agent conversation history, alongside history, completions, YAML workflows, and command corrections under the terminal/entry section (the old command-entry path has moved); Command Palette has its own page, one entry to search Warp features, workflows, and settings. You use these three every day — worth ten minutes to drill into muscle memory. Themes and looks are nice, but they don't change how fast you work — don't spend an afternoon there.
— III
普通终端就够的时候When a Plain Terminal Is Enough.
如果你只用到这一层，一个普通终端、iTerm 或 tmux 就够 —— 不必为底座纠结。If you only use this layer, a plain terminal, iTerm, or tmux is enough — no need to agonize over the base.说句公道话：底座这层 Warp 不是全面赢。论纯定制深度，iTerm2 的触发器、smart selection、Python 脚本 API 攒了多年，Warp 给不齐；论会话持久化和多路复用，tmux 仍是标准，Warp 的 tmux 支持只能算够用。3注 3Note 3Warp Docs · Supported shells / Downloads —— Warp 支持 macOS、Linux、Windows，终端层依赖 shell integration 与本机 shell；远程、容器、离线环境仍要保留普通终端判断。Warp Docs · Supported shells / Downloads — Warp supports macOS, Linux, and Windows; the terminal layer depends on shell integration and local shells; remote, container, and offline environments still need plain-terminal judgment.真正把 Warp 和它们拉开的，是从下一章开始的 agent，不是这层底座。所以判断很简单：在 SSH 进的服务器上、容器里、不联网的环境里，普通终端反而更稳 —— Warp 的甜区是你本机那台、要常调 agent 的终端。只为好看的 block 和主题换工具，不值；为后面那台发动机换，才值。To be fair: in the base layer Warp doesn't win across the board. On raw customization depth, iTerm2's triggers, smart selections, and Python scripting API have accreted over years and Warp doesn't match them; on session persistence and multiplexing, tmux is still the standard and Warp's tmux support is merely adequate.3注 3Note 3Warp Docs · Supported shells / Downloads —— Warp 支持 macOS、Linux、Windows，终端层依赖 shell integration 与本机 shell；远程、容器、离线环境仍要保留普通终端判断。Warp Docs · Supported shells / Downloads — Warp supports macOS, Linux, and Windows; the terminal layer depends on shell integration and local shells; remote, container, and offline environments still need plain-terminal judgment. What actually separates Warp from them is the agent, starting next chapter — not this base layer. So the call is simple: on a server you've SSH'd into, in a container, in an offline environment, a plain terminal is steadier — Warp's sweet spot is the local terminal where you call the agent often. Switching tools for pretty blocks and themes isn't worth it; switching for the engine behind them is.
场景Situation
先用Start with
原因Reason
远程服务器上一条状态命令One status command on a remote server
普通终端 / SSHPlain terminal / SSH
少依赖、少同步、默认可用Fewer dependencies, less sync, always available
本地项目反复跑测试并读输出Repeated local tests with output reading
Warp Blocks
输出可定位、可引用、可丢给 agentOutput is addressable, referenceable, and agent-ready
重复命令链且参数固定Repeated command chain with stable parameters
Workflow
别让 agent 每次现编Do not have the agent improvise every time
什么时候不需要 Agent：命令你已经记得；输出你一眼能看懂；动作是只读、小步、能立即重跑；或者这台机器不能承受 agent 误判。此时底座层就够了。When you do not need the Agent: you already remember the command; you can read the output at a glance; the action is read-only, small, and immediately rerunnable; or the machine cannot tolerate agent misjudgment. The base layer is enough.把这层用到一次自检上：Apply this layer to one self-check:
先看命令本身：是不是你以为的目录、环境和账号。Read the command first: is it the directory, environment, and account you think it is.
再看退出状态和最后 20 行，不要只看第一屏。Then read the exit status and last 20 lines, not just the first screen.
把异常输出单独复制出来，别把整段 scrollback 丢给 agent。Copy the anomalous output alone; do not dump the entire scrollback into the agent.
挑出你每天重复 3 次以上的一条长命令，给它加个书签或存进面板。Pick one long command you repeat 3+ times a day and bookmark it or save it to the palette.
数一数你上周真正用过几次主题 / 外观设置 —— 大概率是零。Count how many times you actually used theme/appearance settings last week — probably zero.
写下一个你宁可用普通终端的场景（远程 / 离线 / 容器 / 重定制），记住那条线。Write down one scenario where you'd rather use a plain terminal (remote/offline/container/heavy customization) and remember that line.
底座让你留下，
发动机才让你不走.
The base gets you to stay,
the engine is what keeps you.
Aklman Library
— 讨论Discussion
讨论Discussion.
评论区初始化中…Initializing comments…
01 / 01
没有匹配结果No matches.
换个关键词，或按 Esc 回到页面Try another keyword, or press Esc to return