Notify
cmd/crewship/cmd_notify.go manages OS-level desktop notifications. Crewship pings you when a long run completes, an approval is waiting, or an escalation arrives — useful when the CLI is in the background.
The preference is stored in ~/.crewship/cli-config.yaml (notifications: true|false).
crewship notify enable
Opt in. Sets notifications: true in the config file.
crewship notify disable
Opt out.
crewship notify status
Show the current setting.
crewship notify test
Fire one notification right now via cli.OSNotify. Confirms the OS integration is wired up.
crewship notify send <title> <body>
Ad-hoc notification — scripting hook.
| Flag | Type | Default | Effect | ||
|---|---|---|---|---|---|
--level <urgency> | string | info | info, warn, or critical. Maps to `cli.NotifyInfo | Warn | Critical`. |
Long-run threshold
The internal helpermaybeNotifyRunComplete only fires when:
- The user opted in via
notify enable, and - The run took longer than the threshold (default
30s).
CREWSHIP_NOTIFY_LONG_RUN=<seconds> — tighter cadence for quick feedback, looser cadence to suppress noise from short routine runs.
Failed runs land with the title Crewship — run FAILED at Critical urgency; normal completion lands as Crewship — run done at Info.
See also
crewship config— direct view of thenotificationskey.crewship escalation— escalations are one of the events that fire notifications.crewship wait— script-blocking alternative to desktop pings.