收束 · 装一台能干一切的终端Closing · Install a Terminal That Does Everything.
把整本书压成一句：你装的不是一个终端，是一台终端形状的元工具。命令、agent、Drive、MCP、云端 —— 同一个窗口，让你在一个地方做完命令行、文件、数据、系统、自动化的活。最后给一张 30 天路线图、三条 starter workflows，以及那把判断尺：留下、沉淀、接外部、放出去，还是切走。The whole book in one line: what you installed is not a terminal, it is a meta-tool shaped like one. Commands, the agent, Drive, MCP, the cloud — one window where command-line, file, data, system, and automation work all get finished in one place. The close gives you a 30-day path, three starter workflows, and the final ruler: stay, distill, connect, send out, or step away.
把整本书压成一句：你装的不是一个终端，是一台终端形状的元工具。它把命令行、agent、Drive、MCP、Cloud Agents / Oz 放在同一个工作台上；真正的变化不是多了一个输入框，而是你开始把命令行工作流当成可以派发、审查、沉淀、复用、放到后台的东西。<Footnote n={1} />The whole book in one line: what you installed is not a terminal, it is a meta-tool shaped like one. It puts command line, agent, Drive, MCP, and Cloud Agents / Oz on the same workbench; the real shift is not another input box, but treating command-line workflows as work that can be dispatched, reviewed, distilled, reused, and sent to the background.<Footnote n={1} />
— I
30 天只改三件事Change Only Three Things in 30 Days.
别从「我要把 Warp 用满」开始，那会把工具变成负担。先用 30 天改三件小事：少手敲一次，少丢一次流程，少守一次后台。Do not start with 'I need to use all of Warp.' That turns the tool into homework. Use 30 days to change three small things: type one less thing by hand, lose one fewer workflow, watch one fewer background run.
时间Time
动作Action
验收Validation
第 1 周Week 1
只用 Blocks + Agent 做只读排障：让它解释输出、列风险、给命令，但危险命令必须手动确认。Use Blocks + Agent only for read-only debugging: let it explain output, list risks, and propose commands, but manually approve risky commands.
你能从一个失败命令追到原因，而不是重新搜索一遍互联网。You can trace one failing command to a cause instead of re-searching the web.
第 2 周Week 2
把一个跑通的过程存进 Drive：Workflow 存命令，Notebook 存 runbook，Prompt 存 agent 任务说明。Save one proven process into Drive: Workflow for commands, Notebook for a runbook, Prompt for an agent task brief.
下次同类任务不用翻聊天记录或 shell history。The next similar task does not require digging through chat logs or shell history.
第 3 周Week 3
只接一个低风险 MCP，最好只读；用它回答一个本来要切网页或后台才能查的问题。Connect one low-risk MCP, preferably read-only; use it to answer one question that used to require switching to a web page or admin panel.
多给了上下文，但没有多给写权限。You added context without adding write authority.
第 4 周Week 4
挑一个不用你守着的任务，判断是否值得上 Cloud Agent；如果触发、上下文、验收、回滚说不清，就留本地。Pick one task you should not have to watch, and decide whether it deserves a Cloud Agent; if trigger, context, validation, and rollback are unclear, keep it local.
第一次上云是一个可检查的 run，不是一场放飞。The first cloud run is inspectable, not a leap of faith.
— II
从这三条 starter workflows 开始Start with These Three Starter Workflows.
如果你不知道第一件该交给 Warp 的活是什么，就从下面三条里选。它们都有一个共同点：终端侧、可审查、可复用，且出错时能回滚。If you do not know what to hand to Warp first, pick one of these three. They share one trait: terminal-side, reviewable, reusable, and reversible when something goes wrong.
提示词PromptStarter workflow · local project debugging
请在这个本地项目里做一次只读排障。
目标：
- 找出 <失败现象> 的最可能原因
- 先不要改文件
- 可以运行只读命令、测试、lint、日志查看
请按这个顺序：
1. 先列你要看的文件和命令
2. 每次命令前解释风险
3. 总结证据，不要只给猜测
4. 给出最小修复方案
5. 等我确认后再进入改动阶段Run a read-only debugging pass in this local project.
Goal:
- Find the most likely cause of <failure>
- Do not edit files yet
- You may run read-only commands, tests, lint, and log inspection
Proceed in this order:
1. List files and commands you want to inspect
2. Explain risk before each command
3. Summarize evidence, not just guesses
4. Propose the smallest fix
5. Wait for my confirmation before editing
请在这个本地项目里做一次只读排障。
目标：
- 找出 npm run dev 启动后访问首页就 500、终端报 "Cannot read properties of undefined" 的最可能原因
- 先不要改文件
- 可以运行只读命令、测试、lint、日志查看
请按这个顺序：
1. 先列你要看的文件和命令
2. 每次命令前解释风险
3. 总结证据，不要只给猜测
4. 给出最小修复方案
5. 等我确认后再进入改动阶段Run a read-only debugging pass in this local project.
Goal:
- Find the most likely cause of the home page returning 500 right after npm run dev starts, with the terminal logging "Cannot read properties of undefined"
- Do not edit files yet
- You may run read-only commands, tests, lint, and log inspection
Proceed in this order:
1. List files and commands you want to inspect
2. Explain risk before each command
3. Summarize evidence, not just guesses
4. Propose the smallest fix
5. Wait for my confirmation before editing
提示词PromptStarter workflow · file batch dry-run
请帮我批处理这些文件，但先只做 dry-run。
范围：
- 目录：<path>
- 文件类型：<ext>
- 目标：<rename/convert/extract/clean>
安全要求：
1. 先生成 manifest，列出会碰到的文件
2. 先处理 3 个样本
3. 任何删除、覆盖、移动都必须等我确认
4. 输出完整命令和回滚办法
5. 通过样本后，再给 full-run 命令Help me batch-process these files, but do a dry-run first.
Scope:
- Directory: <path>
- File type: <ext>
- Goal: <rename/convert/extract/clean>
Safety requirements:
1. Generate a manifest of affected files first
2. Process only 3 samples first
3. Any delete, overwrite, or move requires my confirmation
4. Output full commands and rollback steps
5. After samples pass, provide the full-run command
请帮我批处理这些文件，但先只做 dry-run。
范围：
- 目录：./assets/photos
- 文件类型：.png
- 目标：convert，全部转成质量 80 的 .webp，原文件保留
安全要求：
1. 先生成 manifest，列出会碰到的文件
2. 先处理 3 个样本
3. 任何删除、覆盖、移动都必须等我确认
4. 输出完整命令和回滚办法
5. 通过样本后，再给 full-run 命令Help me batch-process these files, but do a dry-run first.
Scope:
- Directory: ./assets/photos
- File type: .png
- Goal: convert all to .webp at quality 80, keeping the originals
Safety requirements:
1. Generate a manifest of affected files first
2. Process only 3 samples first
3. Any delete, overwrite, or move requires my confirmation
4. Output full commands and rollback steps
5. After samples pass, provide the full-run command
提示词PromptStarter workflow · server health runbook
请把一次服务器健康检查整理成 Warp Drive Notebook。
目标主机 / 环境：<host/env>
检查项：
- disk
- memory
- process
- service status
- recent logs
- open ports
要求：
1. 每个检查项给命令、正常输出特征、异常解释
2. 默认只读，不要 restart / delete / deploy
3. 最后给「什么时候升级给人」的判断线
4. 把可参数化的部分标成 <env> / <service> / <log_path>Turn a server health check into a Warp Drive Notebook.
Target host / environment: <host/env>
Checks:
- disk
- memory
- process
- service status
- recent logs
- open ports
Requirements:
1. For each check, include command, healthy-output signals, and abnormal-output interpretation
2. Default read-only; do not restart / delete / deploy
3. End with escalation criteria for a human
4. Mark parameterized parts as <env> / <service> / <log_path>
请把一次服务器健康检查整理成 Warp Drive Notebook。
目标主机 / 环境：web-prod-01 / production
检查项：
- disk
- memory
- process
- service status
- recent logs
- open ports
要求：
1. 每个检查项给命令、正常输出特征、异常解释
2. 默认只读，不要 restart / delete / deploy
3. 最后给「什么时候升级给人」的判断线
4. 把可参数化的部分标成 <env> / <service> / <log_path>Turn a server health check into a Warp Drive Notebook.
Target host / environment: web-prod-01 / production
Checks:
- disk
- memory
- process
- service status
- recent logs
- open ports
Requirements:
1. For each check, include command, healthy-output signals, and abnormal-output interpretation
2. Default read-only; do not restart / delete / deploy
3. End with escalation criteria for a human
4. Mark parameterized parts as <env> / <service> / <log_path>
这三条跑通以后，才谈沉淀。Drive 不是收藏夹，它应该收纳已经被验证过、下次会复用的工作流。2注 2Note 2Warp Docs · Warp Drive —— Drive 保存 Workflows、Notebooks、Prompts、Environment Variables，并在个人与团队空间中同步；适合把跑通过的一次性过程沉淀为可复用资产。Warp Docs · Warp Drive — Drive stores Workflows, Notebooks, Prompts, and Environment Variables, synced across personal and team spaces; it is the place to turn proven one-off runs into reusable assets.如果一个 Workflow 或 Notebook 三个月没人用，就删掉或重写；不更新的自动化，比没有自动化更危险。Only after these work should you distill them. Drive is not a favorites folder; it should hold workflows that have been validated and will be reused.2注 2Note 2Warp Docs · Warp Drive —— Drive 保存 Workflows、Notebooks、Prompts、Environment Variables，并在个人与团队空间中同步；适合把跑通过的一次性过程沉淀为可复用资产。Warp Docs · Warp Drive — Drive stores Workflows, Notebooks, Prompts, and Environment Variables, synced across personal and team spaces; it is the place to turn proven one-off runs into reusable assets. If a Workflow or Notebook goes unused for three months, delete or rewrite it. Stale automation is more dangerous than no automation.
第一条 MCP 不要给支付、生产数据库、客户数据导出、密钥库写权限。Do not give your first MCP write access to payments, production databases, customer exports, or secret stores.
放到 Cloud Agent / OzSend to Cloud Agent / Oz
后台任务、事件触发、团队可见性、持续检查；每个 run 留下状态、元数据、transcript、outputs 的持久记录可复查。<Footnote n={3} />Background jobs, event triggers, team visibility, continuous checks; each run leaves a persistent record — status, metadata, transcript, outputs — for review.<Footnote n={3} />
触发、验收、额度、失败通知、人工回滚说不清，就不要上云。If trigger, validation, credits, failure notification, and human rollback are unclear, do not send it to the cloud.
切给 Cursor / 编辑器Switch to Cursor / editor
大段读代码、跨文件重构、架构迁移、靠 IDE 语义导航推进的活。Large code reading, cross-file refactors, architecture migrations, work driven by IDE semantic navigation.
不要在终端里硬做编辑器的活。Do not force editor work into a terminal.
切给浏览器自动化 / Computer UseSwitch to browser automation / Computer Use
需要看页面、点击 UI、验证前端流程；Warp 的 Computer Use 是云端沙箱，不是本机控制。<Footnote n={4} />Tasks that require seeing pages, clicking UI, or verifying frontend flows; Warp's Computer Use is a cloud sandbox, not local-machine control.<Footnote n={4} />
不要把「能跑命令」误读成「能安全控制你的电脑」。Do not mistake 'can run commands' for 'can safely control your computer.'
— IV
最后的尺子The Final Ruler.
每次你准备把一件活交给 Warp，问这四句就够了。Every time you are about to hand work to Warp, four questions are enough.
它是不是命令行形状的活：文件、日志、脚本、服务、数据、测试、部署、系统状态？Is it command-line-shaped work: files, logs, scripts, services, data, tests, deploys, system state?
它能不能被审查：命令、输出、diff、计划、run transcript 是否看得见？Can it be reviewed: are commands, output, diffs, plan, and run transcript visible?
它值不值得沉淀：下次会不会再来，参数是否稳定，别人是否也能复用？Is it worth distilling: will it recur, are parameters stable, can someone else reuse it?
它该不该出界：编辑器侧、GUI 侧、离线/远程/容器侧、企业治理侧是否已经比 Warp 更自然？Should it step out: is editor-side, GUI-side, offline/remote/container-side, or enterprise-governance-side work more natural elsewhere?
问完这四句，你就不会把 Warp 当玩具，也不会把它当神。它只是一台很强的工作台：命令在这里发生，agent 在这里动手，知识在这里沉淀，后台在这里接力，人仍然在这里负责。After those four questions, you will treat Warp as neither a toy nor a god. It is just a powerful workbench: commands happen here, the agent acts here, knowledge is distilled here, background work takes the handoff here, and the human remains responsible here.
一台终端形状的元工具真正的价值，
不是替你控制电脑，
而是让命令行工作流少丢一次。.
The real value of a terminal-shaped meta-tool
is not that it controls your computer,
but that one fewer command-line workflow gets lost..
Aklman Library
— 讨论Discussion
讨论Discussion.
评论区初始化中…Initializing comments…
01 / 01
没有匹配结果No matches.
换个关键词，或按 Esc 回到页面Try another keyword, or press Esc to return