Notifications
Know when Claude needs you or has finished, on your Mac or on your phone, and jump straight to whoever is waiting.
What Termlux tells you about
| When | You see, for example |
|---|---|
| Claude asks to run something | ⏳ Allow Bash: npm test? |
| Claude has a question | ⏳ Asks: Which database should I use?, with the choices |
| Claude has a plan for you to approve | ⏳ Plan ready to approve |
| Claude finished | ✓ Fix the login test done — 3 files changed |
| Claude couldn't finish | ⚠ Couldn't finish: Fix the login test, with the first line of the error |
| A task on the board is done or blocked | ✓ #12 done / ⛔ #12 blocked, with Open board |
| A terminal waits for input | ⏳ name needs your input |
| A command that ran more than 15 seconds ends | ✓ Command done, or the exit code if it failed |
| A trigger matched (see below) | The trigger's name |
Under each title is the workspace and its Claude account. Keys, tokens and passwords in a command are masked before a notification goes anywhere.
While Termlux is in the background, these are Mac notifications. While it's in front, they show inside the app, with a button to go there. Nothing is sent about the chat you're looking at.
The first notification asks macOS for permission. To turn them all off, use Settings › Notifications › Allow notifications.
Jump to whoever is waiting
When agents wait on you, the top bar shows N waiting. takes you to the next one. A chat that finished or failed keeps a dot on its tab until you've looked, and the Dock icon counts the workspaces waiting for you.
On your phone
Termlux can send the same notifications to your phone through ntfy, a free app for iPhone and Android:
1. Install ntfy on your phone and subscribe to a topic: a name only you know, such as
termlux-k3v9q2.2. In Settings › Notifications › Push to your phone, enter the same Topic.
3. Click Send test.
Leave Topic empty to turn it off. Server is https://ntfy.sh unless you run your own.
On the phone, approvals, questions, plans, failures and blocked tasks arrive at high priority, so they buzz; a finished chat arrives at normal priority.
Triggers
A trigger watches terminal output for a pattern and tells you when it appears: a build failing, a server starting, a test run ending.
1. In Settings › Notifications › Triggers, click Add trigger.
2. Enter a Pattern: a regular expression, matched without regard to case, such as
error|failed.3. Give it a Name if you like, and choose Notify or Bell.
A trigger fires at most once every 4 seconds per session.