Getting the most out of Opus 5.5 in Claude and Claude Code

如何在 Claude 和 Claude Code 中充分利用 Opus 5.5

How to prompt Opus 5.5, steer a long run, and check your results in Claude apps and Claude Code. 本指南将介绍如何在 Claude 应用和 Claude Code 中提示 Opus 5.5、引导长任务运行以及检查结果。

AUTHOR: Addy Osmani | PUBLISHED: Sep 22, 2026 | READING TIME: 9 min 作者： Addy Osmani | 发布日期： 2026年9月22日 | 阅读时间： 9 分钟

Opus 5.5 works well with the way you already use Claude. A few things behave differently, though: it works for longer on its own, it tells you plainly what it did, and it thinks before every reply. This guide covers how to work with Opus 5.5 in Claude apps and Claude Code, including how to prompt the model, steer a long run, and check your results. Opus 5.5 与你现有的 Claude 使用习惯兼容良好。不过，有几点表现有所不同：它能更长时间地独立工作，会清晰地告诉你它做了什么，并且在每次回复前都会进行思考。本指南涵盖了如何在 Claude 应用和 Claude Code 中使用 Opus 5.5，包括如何提示模型、引导长任务运行以及检查结果。

TRY THIS FIRST: Three things to try in your first session with Opus 5.5

先试一试：在首次使用 Opus 5.5 时尝试这三件事

Hand over the whole task. Say what “done” looks like and when you want it to stop and ask. Then let it work.
全权交付任务。 说明“完成”的标准是什么，以及你希望它在何时停下来询问。然后让它开始工作。
Delete “think carefully” lines. Opus 5.5 already thinks before every reply.
删除“仔细思考”之类的指令。 Opus 5.5 在每次回复前都会自动思考。
When a long run ends, read what it needs from you first.
当长任务结束时，先阅读它需要你提供什么。

1. HOW TO ASK: Say what “done” looks like, then let it run

1. 如何提问：说明“完成”的标准，然后让它运行

What to do. Give the whole task in one message. Name the finish line, like “the tests pass” or “every endpoint is migrated.” Then let it cook. 怎么做。 在一条消息中给出完整任务。明确终点线，例如“测试通过”或“所有端点已迁移”。然后让它去执行。

Why it matters on Opus 5.5. Opus 5.5 keeps going on long, multi-part work better than Opus did. Compared to prior Opus models, its biggest gains are on multi-step work, like carrying a change through a large repository until the tests pass. Early testers had it run long coding tasks for hours with little oversight. With a clear finish line, it knows when it’s done. 为什么这对 Opus 5.5 很重要。 Opus 5.5 在处理长期的、多部分组成的工作时，表现比 Opus 更好。与之前的 Opus 模型相比，它在多步骤工作（例如在大型代码库中进行更改直到测试通过）上的提升最为显著。早期测试者让它在几乎无人监管的情况下运行了数小时的长编码任务。有了明确的终点线，它就能知道何时完成。

How. In Claude Code, for example: 如何操作。 以 Claude Code 为例：

PROMPT: Migrate the payment endpoints from the old client to the new one. Done means: every endpoint uses the new client, the old client is deleted, and the test suite passes. Stop and ask me only if a test fails for a reason you can’t explain. 提示： 将支付端点从旧客户端迁移到新客户端。完成意味着：每个端点都使用新客户端，旧客户端被删除，且测试套件通过。只有当测试因你无法解释的原因失败时，才停下来问我。

Stop telling it to “think hard”

停止要求它“深度思考”

What to do. Remove “think carefully,” “think step by step,” and similar lines from your prompts and your saved instructions. 怎么做。 从你的提示词和保存的指令中删除“仔细思考”、“一步步思考”及类似的语句。

Why it matters on Opus 5.5. Opus 5.5 always thinks before it replies, and it decides how much. You don’t need to ask it to think. In our testing in a chat product, removing a “think carefully” line made replies start sooner, with no clear drop in quality. 为什么这对 Opus 5.5 很重要。 Opus 5.5 在回复前总是会思考，并且它会自行决定思考的深度。你不需要要求它思考。在我们对聊天产品的测试中，删除“仔细思考”指令后，回复开始得更快，且质量没有明显下降。

Add to a running task

在任务运行中追加指令

What to do. If you remember something mid-run, you can type a follow-up while it works. 怎么做。 如果你在任务运行中想到了什么，可以在它工作时输入后续指令。

Why it matters on Opus 5.5. Runs are longer now, so a restart costs more. 为什么这对 Opus 5.5 很重要。 现在的任务运行时间更长，因此重启的成本更高。

How to do it. In Claude Code, type the message and press Enter while Claude works, for example, “Also keep the old endpoint names as aliases.” 如何操作。 在 Claude Code 中，当 Claude 正在工作时，输入消息并按回车键，例如：“同时保留旧的端点名称作为别名。”

For design work, name the styles you don’t want

对于设计工作，列出你不想要的风格

What to do. When you ask for a page, an app, or an artifact, list the design habits you want left out. 怎么做。 当你要求生成页面、应用或工件（artifact）时，列出你想要避免的设计习惯。

Why it matters on Opus 5.5. With no design direction, Opus 5.5 falls back on a few default styles. A general instruction like “avoid a generic look” mostly swaps one default for another. A list of specific patterns works much better. 为什么这对 Opus 5.5 很重要。 如果没有设计指导，Opus 5.5 会退回到几种默认风格。像“避免平庸外观”这样笼统的指令通常只是从一种默认风格换成另一种。列出具体的模式效果要好得多。

How. Name the patterns: 如何操作。 列出模式：

PROMPT: Build a personal website with placeholder content. Don’t use a cream or off-white background, italic accent words in headings, numbered “01 / 02 / 03” section labels, monospace labels, or pill-shaped buttons. 提示： 建立一个带有占位内容的个人网站。不要使用奶油色或灰白色背景，不要在标题中使用斜体强调词，不要使用“01 / 02 / 03”编号的章节标签，不要使用等宽字体标签，也不要使用药丸形状的按钮。

2. STEERING A LONG RUN IN CLAUDE CODE

2. 在 CLAUDE CODE 中引导长任务运行

Tell it which stops you want. Put a short rule in your CLAUDE.md file about when to stop and ask, and when to keep going. 告诉它你希望在何处停止。 在你的 CLAUDE.md 文件中加入一条简短规则，说明何时停止询问，何时继续执行。

Why it matters on Opus 5.5. Opus 5.5 keeps you posted as it works. On a long task, it sometimes stops to report instead of going on: a summary that names the next step without taking it, an offer to continue, or a list of choices that don’t block the work. It follows instructions that name these stops. 为什么这对 Opus 5.5 很重要。 Opus 5.5 在工作时会随时向你通报进度。在长任务中，它有时会停下来汇报而不是继续执行：提供一个总结并指出下一步但不执行，询问是否继续，或者提供不阻塞工作的选项列表。它会遵循你设定的这些停止指令。

How. Add this to CLAUDE.md, and edit it to fit your project: 如何操作。 将以下内容添加到 CLAUDE.md，并根据你的项目进行编辑：

PROMPT: When a step doesn’t need my input, keep going. Put status notes in the same message as your next action. Stop and ask only when you can’t continue without me, or before anything destructive: deleting data, force-pushing, or changing anything outside this repository. 提示： 当某一步骤不需要我的输入时，请继续执行。将状态说明放在与下一步行动相同的消息中。只有在没有我的参与无法继续，或在进行任何破坏性操作（删除数据、强制推送或更改此仓库之外的任何内容）之前，才停下来询问。

Ask it to split big work across subagents

要求它将大型工作分配给子代理

What to do. For an audit, a migration, or a review across a large codebase, ask Opus 5.5 to split the work across subagents and check each result. 怎么做。 对于大型代码库的审计、迁移或审查，要求 Opus 5.5 将工作分配给子代理，并检查每个结果。

Why it matters on Opus 5.5. Early testers had Opus 5.5 coordinate parallel subagents on long audits and migrations, with little oversight. 为什么这对 Opus 5.5 很重要。 早期测试者让 Opus 5.5 在几乎无需监管的情况下，协调并行子代理完成了长期的审计和迁移工作。

How. 如何操作。

PROMPT: Audit every service in services/ for the retry bug in the linked issue. Give each service to its own subagent. When a subagent reports back, check its evidence before you accept it. Finish with one table: service, affected yes or no, and the evidence. 提示： 审计 services/ 目录下的每个服务，查找链接问题中提到的重试错误。将每个服务分配给一个独立的子代理。当子代理汇报时，在接受其结果前先检查其证据。最后生成一个表格：服务名称、是否受影响（是/否）以及证据。

Keep the task list in a file

将任务列表保存在文件中

What to do. For a run that will take a while, ask Opus 5.5 to keep its task list in a file and update it as it goes. Then read the file, not the scrollback, to see where the run is. 怎么做。 对于需要较长时间的任务，要求 Opus 5.5 将任务列表保存在文件中并随进度更新。然后通过阅读该文件（而不是滚动查看历史记录）来了解任务进度。

Why it matters on Opus 5.5. Runs are longer now. A long run fills the context window, and Claude Code then summarizes older turns. A list in a file survives that, and it shows you at a glance what’s done and what’s left. 为什么这对 Opus 5.5 很重要。 现在的任务运行时间更长。长任务会填满上下文窗口，Claude Code 随后会总结旧的对话。保存在文件中的列表可以避免被清理，让你一眼就能看出哪些已完成，哪些还未完成。

How. “Keep a checklist in TASKS.md. Tick each item when it’s done.” 如何操作。 “在 TASKS.md 中维护一个检查清单。每完成一项就勾选一项。”