drip is a free, open-source macOS CLI that shows scriptable notification cards from the MacBook notch, for builds, deploys and coding agents like Claude Code, Codex and Gemini CLI.
Interactive demo · Documentation
brew install jrnxf/tap/drip
drip ok "hello"Requires macOS 13 or newer. Tested on macOS 15 and 26. Homebrew installs a prebuilt binary for Apple silicon and Intel, with no Xcode needed. No Notifications permission: drip draws its own card. On a Mac without a notch, the card grows out of the top edge of the screen. See installation for source builds and uninstall instructions.
Pipe text into a card, give it an action, or use an answer to decide what happens next.
# The first line becomes the title, the rest becomes the detail
git log -1 --format='%s%n%an' | drip ok
# Open a report from the card
drip ok "Report ready" --open ./report.html --button "View report"
# Continue only when you click Deploy
drip warn "Deploy to prod?" --yes Deploy --no Cancel && ./deploy.sh
# Show a command's result and duration, and keep its exit status
drip run make testSee usage for more examples and the contract for exit codes and scripting guarantees.
When the agent needs you, a card comes from the notch. Click it to go back to the agent's terminal.
The fastest way: ask your agent.
Install drip with Homebrew (brew install jrnxf/tap/drip) and add the permission-cards recipe from https://github.com/jrnxf/drip/blob/main/recipes/permission-cards/README.md to my Claude Code settings. Keep my other hooks.
- Claude Code by hand: paste the snippet from permission-cards into
~/.claude/settings.json. - Codex: the Codex snippet goes in
~/.codex/hooks.json. - Gemini CLI: the Gemini CLI snippet goes in
~/.gemini/settings.json. - Allow and Deny on the card, for Claude Code and Codex: approve-from-card.
For a shared settings file, use command -v drip >/dev/null && drip hook claude || true as the command, as the team recipe does. It is silent on a machine without drip, so a settings file shared across machines is safe.
More recipes, such as a done card for every turn, are in the recipe catalog.
To let your agent send cards itself, add the drip skill: npx skills add jrnxf/drip. Then say "tell me with drip when the tests are done". It adds no hooks.
Set the size, stacking and reusable presets in ~/.config/drip/config.toml. Every key is optional.
size = "regular" # compact | regular | large
stack = "chain" # chain | off
[preset.deploy]
icon = "paperplane.fill"
color = "#a78bfa"
sound = "Submarine"Then drip deploy "shipped" uses the preset. Configuration lists every setting and its DRIP_* environment variable.
Clicks can activate an app or run your own command. Cards wait while the screen is locked, and drip history --missed shows missed cards.
Use drip pause 30m for a meeting or screen share. Drip does not follow Focus or Do Not Disturb automatically.
See click actions, history, and pausing.
Recipes are snippets you copy and adapt, such as slow shell commands or a custom click action. See the recipe catalog. To show cards from a Linux machine on your Mac, see remote notifications.
- terminal-notifier and other Notification Center tools: they need the Notifications permission and follow Focus. drip draws its own card, and
drip runwraps a command. - Notch apps for coding agents: they set up the hooks for you, so they are the easier choice if agent activity in the notch is all you want. drip is a command, so the same card works for a build, a deploy or a long script, and a script can act on the answer.
- The agent's own terminal notification: a drip card names the project, goes when you answer in the terminal, and a click brings that terminal back.
See the comparison.
- Usage and scripting contract
- Configuration and recipes
- Coding agents: every hook event and flag
- Troubleshooting: permissions, privacy, and missing cards
- Development and the interactive card tour
Drip collects no analytics. Its only network connection is the SSH connection used by drip follow.
See privacy.
MIT