Hacker News Reader

Comment by hadlock | Hacker News Reader

Opus is so slow these days what I really want is a bell sound to ring when it's done. I kick off some task and then it takes 3-12 minutes to complete. It's wrong, so I tell it to revert and try again with slightly different instructions.

View on HN

You can use edit your settings.json in ~/.claude and put a hook for it like this:

    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "afplay ~/.claude/hooks/chime.wav",
            "async": true
          },

That hook is also called when subagents stop which means you'll get a lot of false positives.

Ideally you are only notified when the main agent stops, the main agent has a question, or a subagent has a question.

I created a script that figures out if any of those states apply before emitting a macOS notification and then called it in each hook:

    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "script.sh",
            "timeout": 10
          }
        ]
      }
    ],
    "PreToolUse": ...
    "PermissionRequest": ...
    "Elicitation": ...

Have you tried analysing all your prompts, and then telling it to "figure out" what custom skills might improve your prompts? I do actually have another project I'm working on that does this... it's been super useful for seeing how I prompt, what Skills I use and getting them to evolve and improve (I know Hermes does some of this, but it's been interesting rolling my own - will release soon!!)

I have a pretty specific workflow, I deal with live systems a lot (primarily in staging but occasionally prod) and have a really neat skill that has hooks into all the various things and then writes (&& checks in git) an investigation doc (.md) using a template into a git knowledgebase by month/quarter. That knowledgebase is really useful for frontloading the context of my new sessions as a lot of my work is iterative on previous work. It is really good at 80% of tasks, but simple stuff like using sops or modifying subcharts in helm it really struggles with. I do a lot of integration work between monorepos and Opus 4.7/4.8 really struggle with that kind of work. Opus is so bad at sops work I just outsource that to Codex/GPT5.5 now because the failure rate is so high.

The other high failure rate things is opus correctly predicting where endpoints will end up (stacked endpoints), when you have an ingress with a main monorepo but it's endpoints are the outputs (not just json regurgitated/passed forward).

I figured by having the clanker write it's own documentation about what it did, and then the next time saying "go look at invest doc 2026-06-29-TICKT_1234.md, do that again, but here's what we're doing differently and why..." and it would immediately grep the situation, but it doesn't. As alluded to earlier I've been exploring other models since the corporate blessed one is struggling to keep up.

Curious to see what you release.

Cmux notifications does this too

Try superset, it does that

Reply on news.ycombinator.com