English | 中文

bark-notify

A Claude Code plugin that pushes a notification to your iPhone via Bark when Claude Code finishes a turn, errors out, or asks for your approval.

Why I built this

• In vibe coding, especially when juggling multiple projects, I often need to glance back at the terminal just to see whether Claude is done, has failed, or is stuck waiting for my approval.
• In an office, sound alerts are not always practical. And when you're looking at your phone while doing something else in parallel, that repeated “should I check the terminal again?” interruption gets annoying fast.
• Claude does have an official mobile notification path, but it is more aligned with the Cowork / Dispatch / Remote Control experience: install the Claude mobile app, enable notifications, keep the connection healthy, and in mainland China that usually also means keeping a VPN on all the time. If you're casually multitasking on your phone, that extra network friction gets annoying too.
• If you mainly use Claude Code CLI, the official customization surface is still mostly hooks; the official phone-push experience lives more in Remote Control / Dispatch, not as a lightweight phone notification path built into plain CLI usage.
• There are other workarounds too — Feishu or DingTalk bots, iMessage, email — but they are either heavy on setup, permission-gated, or too tied to one platform for this kind of frequent reminder.
• If you also use ccswitch to swap models, the desktop-first route is not always the smoothest fit. My own setup is ccswitch + Doubao voice input + this plugin, and the overall vibe coding loop feels much better.
• So I built this plugin to do one thing well: notify me when Claude is actually done or needs me. Bark is simple to set up, does not require an extra account, generates a key for you, and becomes usable as soon as you hand the URL to Claude.
• If privacy matters, you can turn on encryption or self-host Bark. At least for the notification layer, you do not have to route everything through a work chat tool or another third-party notification chain.

Requirements

• macOS with Claude Code installed
• iPhone with the Bark app installed and a push URL ready (https://api.day.app/<your-device-key>)

Install

In any Claude Code session:

/plugin marketplace add RUIIIOVO/claude-code-bark-notify
/plugin install bark-notify@bark-notify
/reload-plugins

Configure

/bark-notify:bark-notify-setup

You will be asked for:

1. Your Bark push URL — https://api.day.app/<device-key>
2. Plain or encrypted mode (encrypted is recommended if your push URL is sensitive)
3. If encrypted: a 16-character key (must match your iPhone Bark settings: AES128 / CBC / pkcs7)

Verify:

/bark-notify:bark-notify-test

Notifications

The push title is always the project directory name. The body is differentiated per event:

tmux

The script emits a terminal bell after every notification. To surface it in tmux:

tmux set -g monitor-bell on
tmux set -g visual-bell on

Uninstall

/bark-notify:bark-notify-uninstall

Removes the Bark hooks from ~/.claude/settings.json and deletes the local script.

Troubleshooting

Ask Claude in any session — the bark-notify plugin includes a guidance skill for setup and troubleshooting. Or re-run setup to reconfigure.

Privacy

• Your Bark URL and encryption key are stored locally in ~/.claude/ and never sent anywhere except your Bark server.
• Setup merges into your existing ~/.claude/settings.json without overwriting other entries.
• In encrypted mode, the notification body is AES-128-CBC encrypted before leaving your Mac.

For contributors

git clone https://github.com/RUIIIOVO/claude-code-bark-notify.git
cd claude-code-bark-notify
claude --plugin-dir .

Skills:

Changelog

See CHANGELOG.md or CHANGELOG.zh-CN.md.

License

MIT