You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
I know when any agent needs my help, at home and at work #299
When an agent needs my input, a decision or my help, I often don't find out until I happen to look at its session, so it can wait, or carry on around a problem, for hours. The only signal today is the Notification hook, which shows a banner saying a session "Needs your attention in " when Claude Code raises a notification, and it doesn't say what the session needs. An unattended session skips the work logins, so when it meets an expired login it carries on without telling anyone. A failed switch between the subscription and Vertex AI shows only on the status line of the sessions that are open.
Ideal state
When an agent stops to wait on my input, a decision or my help, I find out, and I'm told what it needs from me
When an agent keeps working but needs my help soon, such as a work login it cannot renew, I find out, and the agent keeps a record of what to check again once I have helped
At home and at work, I am told through a notification surface chosen for that place
Out of scope
Replying to a notification, by typing an answer or picking one of the options it offers, so the agent receives it and carries on. I want this later, so the surface chosen here should allow it.
Decisions
Constraints
No recorded decision covers how agents reach me (checked the titles in docs/decisions/).
Open
Which notification surface reaches me at home, and which at work, and can each carry a typed reply or a chosen option back to the agent? (user-facing pattern people will learn)
Where does an agent that keeps working record what it needs from me? (new persistent data shape or store)
Starting points
tools/claude/notify.bash: the Notification hook's banner
tools/claude/config/settings.json: the hooks that run today
tools/claude/cc.bash: where an unattended start skips the work logins
Another place an agent waits unseen: hub now starts every investigation through cc.bash (ooloth/hub#435), and hub never passes --unattended, so on the work laptop each one runs the work logins first. Hub opens Rex tabs in the background (hub decision 032), so a tab can sit at a browser login, or wait on another run's login lock, with nothing telling me. The Notification hook can't fire, because Claude Code hasn't started yet.
Activity
ooloth commentedon Nov 19, 2026
Another place an agent waits unseen: hub now starts every investigation through
cc.bash(ooloth/hub#435), and hub never passes--unattended, so on the work laptop each one runs the work logins first. Hub opens Rex tabs in the background (hub decision 032), so a tab can sit at a browser login, or wait on another run's login lock, with nothing telling me. TheNotificationhook can't fire, because Claude Code hasn't started yet.