Task notifications CLI · send
Get told when a long task finishes
Leave a build, test or SSH job running. Receive its result on your phone when it finishes.
Connect your scriptsUpdated
When to use it
Tests take twenty minutes, a build runs on another machine, or an SSH job needs time. Add a notification after the job so its result reaches you. Pair the machine that actually runs the command, and keep its normal job logs for details.
Connect in three steps
Pair the task machine
Install the CLI, authorize it with your phone and check its Topic with ntfyx topics.
Capture the task result
Record the exit status before sending a success or failure message. Choose an explicit Topic if more than one is available.
Receive the summary
Check both success and failure paths with harmless tasks before attaching the notification to your real job.
Start here
First, get Ntfyx on your phone
On a computer? Click a store to scan its QR code with your phone.
Check that it works
Run this POSIX shell example with sh after pairing. It preserves the task status even when notification delivery fails. The sample task succeeds; replace true with false for a harmless failure test. Use your actual task only after both paths work.
# Run as a script with sh; replace true with your task later.
task_status=0
true || task_status=$?
if [ "$task_status" -eq 0 ]; then
message="Task finished successfully"
else
message="Task failed (exit $task_status)"
fi
ntfyx send "$message" || printf '%s\n' 'Notification failed; inspect the job log.' >&2
exit "$task_status"What to know
A notification reports the status your script observes; it is not a remote terminal. Use your existing job runner if work must survive an SSH disconnect. Keep private log contents out of the message. Windows has CLI and local MCP support; this shell example targets macOS/Linux.