Notifications
Notifications are how a long-running or unattended agent reaches you when it finishes, fails, or needs an approval.
Sending one
arble mobile notify "Migration finished — 14 tables, 0 errors"
arble desktop notify "Nightly triage complete"The useful pattern
Make the last step of any background job a notification. Without one, a detached run that finished hours ago is indistinguishable from one that is still working.
#!/usr/bin/env bash
set -euo pipefail
count=$(arble run --json --no-prompt \
"Count files in src/ importing the deprecated retry helper" | jq '.count')
arble mobile notify "$count files still use the deprecated retry helper"Permission requests
A run that needs approval while you are away enters requires_action and waits. It
expires after 15 minutes. If you run agents unattended, either pre-grant the capability or subscribe
to the permission.requested event — a notification alone does not keep the run
alive.
What a notification should contain
An outcome and a number, not a transcript. Notifications land on a lock screen; assume they are read by someone other than you, and keep anything sensitive out of the body.