‹ BackHN Continuity

Thread

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

232 points · 156 comments · saikatsg

  1. kingcauchy · · focus · HN ↗
    I've had troubles with it getting stuck "waiting" for a day on some hook or something in CC that never completed and during a task that was waiting on an orphaned process. That maybe saves token money on checks waiting for long-running processes but makes it hard to trust for long-horizon work.

    It's been amazing at making sure OOMs for multiple heavy builds on my machine don't happen, adding queues and locks to make sure performance measurements are isolated and gpu stays clean during experiments.

    It's also way more able to execute subagent tasks all at once than GPT 6.1 I tried to give it 10 different subtasks all at once that were overlapping and unrelated issues and it did a good job spinning up isolated worktees, agents and then coordinating the merge back together and then verifying them with agents in batches.

    1. driverdan · · focus · HN ↗
      I've been encountering the same waiting problems. It likes to run things in the background with suppressed output, waiting for it to exit before it takes action. That's great when nothing goes wrong but today alone I've had to break in two or three times when something obviously broke and it was sitting for over 10 min.

      IMO it should have the option to observe background tasks with a small model to make sure it's working correctly.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.