Who it is forA developer working in another app or fullscreen window who needs to know the moment Claude Code asks a question or raises a notification.
The problemPure state changes in Claude Code produce no bubble on the pet, so a session can wait unseen while you work elsewhere.
The outcomeA system banner with the Glass sound lands in Notification Center whenever Claude Code fires a Notification event.
What you need first
- A Mac running macOS
- Clawd on Desk installed from https://github.com/rullerzhou-afk/clawd-on-desk/releases
- Claude Code installed
- git, python3, and node available on the machine
Steps
- Run
git clone https://github.com/ssssssanjiu/clawd-conduit.gitand thencd clawd-conduit - Run
bash install.shand accept the notification script step when asked - In Clawd's settings, set notificationBubbleAutoCloseSeconds to a high value such as 3600, not 0
- Start a new Claude Code session and trigger a notification
- Check Notification Center for the banner and listen for the Glass sound
Prompt for your agent
In the clawd-conduit repo, confirm that ~/.claude/hooks/ contains the notification script after running `bash install.sh`. Report the file listing and state whether the Notification hook is attached in ~/.claude/settings.json.
Caveat. The notification script uses osascript, so it only works on macOS, and setting notificationBubbleAutoCloseSeconds to 0 turns off the notification bubble instead of making it stay.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page