Live data from Hacker News

Show HN: Claudoro, Pomodoro timer embedded in the Claude Code statusline

github.com

21–30 of 40 posts

Re: Show HN: Claudoro, Pomodoro timer embedded in the Claude Code statusline

#21
post #20

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.

Try superset, it does that

Re: Show HN: Claudoro, Pomodoro timer embedded in the Claude Code statusline

#22
post #16

I like this. Small tools inside the workflow feel much more useful than separate productivity apps I have to remember to open.

I ended up building a vs-code/IDE style workflow for claude that has a "file browser" of CC sessions in the left column, sorted by repo, and then terminal in the right column, and then I've been tacking features like this onto it

Re: Show HN: Claudoro, Pomodoro timer embedded in the Claude Code statusline

#23
post #19

Love that it follows you from terminal to terminal, super useful. Though, if you're following Cal Newport-ian rules, watching over multiple agents doing their work is no longer a 25 minute "deep work" Pomodoro, and god knows Newport has been complaining about it [1] [1]: https://calnewport.com/avoiding-digital-productivity-traps/#...

Nice! I love Cal Newport. I've definitely found spinning up multiple Claude Code instances eats into your focus, and you can "lose yourself" quite quickly. I find I use pomodoros more as nudges, and use the "beeps" to bring me back if I'm in the browser or something. but yeah... it's a trap for sure!

Re: Show HN: Claudoro, Pomodoro timer embedded in the Claude Code statusline

#24
post #20

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.

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!!)

Re: Show HN: Claudoro, Pomodoro timer embedded in the Claude Code statusline

#25
post #22
post #16

I like this. Small tools inside the workflow feel much more useful than separate productivity apps I have to remember to open.

I ended up building a vs-code/IDE style workflow for claude that has a "file browser" of CC sessions in the left column, sorted by repo, and then terminal in the right column, and then I've been tacking features like this onto it

Fantastic! You should open source it

Re: Show HN: Claudoro, Pomodoro timer embedded in the Claude Code statusline

#26
post #20

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.

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
          },

Re: Show HN: Claudoro, Pomodoro timer embedded in the Claude Code statusline

#27
post #20

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.

Cmux notifications does this too

Re: Show HN: Claudoro, Pomodoro timer embedded in the Claude Code statusline

#28
post #20

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.

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": ...
Post reply on HN