{
  "id": 11845767,
  "title": "Getting the most out of Opus 5.5 in Claude and Claude Code",
  "url": "https://urgent.news/2026/10/03/getting-the-most-out-of-opus-5-5-in-claude-and-claude-code-11845767",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-03T18:29:30.000Z",
  "source": {
    "name": "Hacker News Best",
    "slug": "hacker-news-best",
    "url": "https://claude.dev/blog/getting-the-most-out-of-opus-5-5/"
  },
  "original_language": "en",
  "account": "To work with Opus 5.5 in Claude apps and Claude Code, follow these steps. First, give the entire task in one message and specify the finish line, such as \"the tests pass\" or \"every endpoint is migrated.\" Let Opus 5.5 work on long, multi-part tasks, as it handles them better than Opus 5 did.\n\nAvoid using phrases like \"think carefully\" or \"think step by step\" in your prompts and saved instructions, as Opus 5.5 always thinks before it replies, and you don't need to ask it to do so. If you need a quick answer to a simple question, add \"Answer directly\" to your message.\n\nWhile Opus 5.5 is running, you can type a follow-up message while it works. It is better to provide specific design habits you want to avoid when asking for a page, app, or artifact. Include a short rule in your CLAUDE.md file to help you decide when to stop and ask for more information.\n\nWhen a run stops with \"Want me to continue?\" respond with \"continue\" to prevent frequent stops. Keep permission prompts on for destructive commands. For pair programming, you may want to provide a one-line plan before starting and a short recap at the end. Set this up in your CLAUDE.md file.\n\nFor audits, migrations, or reviews across a large codebase, ask Opus 5.5 to split the work across subagents and check each result. Use a file to keep track of the task list, updating it as the run progresses. This way, you can read the file to see the current status of the run.\n\nAfter a long run, look for any decisions or changes left open by Claude and read the summary for more information. To change the summary's format, specify it in your CLAUDE.md file. Ask Opus 5.5 to review a diff or pull request before a person does, as it tends to catch more bugs and provide explanations in plain language.\n\nWhen providing an image for analysis, attach it directly and ask a specific question about it. Opus 5.5 is better at reading and understanding charts, diagrams, screenshots, and slides compared to Opus 5. Lastly, provide a long plan, report, or deck to Opus 5.5 and ask it to find mistakes. It will help you identify any issues that may have been overlooked.",
  "summary": "Article URL: https://claude.dev/blog/getting-the-most-out-of-opus-5-5/ Comments URL: https://news.ycombinator.com/item?id=49946567 Points: 191 # Comments: 132",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 2,
    "also_reported_by": [
      {
        "outlet": "XDA Developers",
        "title": "After a month switching between Claude Code and its open-source rival, I only open Claude for one kind of task",
        "url": "https://urgent.news/2026/10/03/after-a-month-switching-between-claude-code-and-its-open-source-rival",
        "published": "2026-10-03T20:00:18.000Z"
      }
    ]
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}