As long as those native (Objective-C / Swift) menu bar apps are ported as native (Go, Rust, Zig, etc.) binaries for Agent CLI(s) like Claude Code or Codex CLI to use, instead of JavaScript, as this project is written, then the broader community of Agent CLI users will be fine. Otherwise, it will be another nightmare induced by JavaScript.
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/#...
https://github.com/Hadlock/cscope/
It's not amazing code but it's tooling that works for me.
It's a long road to recovery. I'm 5 months in and still in a lot of pain, but it does (slowly) get better. Hope you're spirits stay up!
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.
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "afplay ~/.claude/hooks/chime.wav",
"async": true
},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": ...