edf9d0be6f
33 markdown files organized for GitBook import with SUMMARY.md navigation. Covers installation, core concepts, auto mode, configuration, all providers, cost management, skills, parallel orchestration, remote questions, teams, headless CI, and full command reference. User-facing only — no internal/dev content. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
# Notifications
|
|
|
|
GSD sends desktop notifications during auto mode to keep you informed without watching the terminal.
|
|
|
|
## Configuration
|
|
|
|
```yaml
|
|
notifications:
|
|
enabled: true
|
|
on_complete: true # notify on unit completion
|
|
on_error: true # notify on errors
|
|
on_budget: true # notify on budget thresholds
|
|
on_milestone: true # notify when milestone finishes
|
|
on_attention: true # notify when manual attention needed
|
|
```
|
|
|
|
## macOS Setup
|
|
|
|
GSD uses `terminal-notifier` when available, falling back to `osascript`.
|
|
|
|
**Recommended:** Install `terminal-notifier` for reliable delivery:
|
|
|
|
```bash
|
|
brew install terminal-notifier
|
|
```
|
|
|
|
**Why?** The `osascript` fallback attributes notifications to your terminal app (Ghostty, iTerm2, etc.), which may not have notification permissions. `terminal-notifier` registers as its own app and prompts for permission on first use.
|
|
|
|
### Notifications Not Appearing?
|
|
|
|
1. Check **System Settings → Notifications** for your terminal app
|
|
2. Install `terminal-notifier` (recommended)
|
|
3. Test with:
|
|
```bash
|
|
terminal-notifier -title "GSD" -message "working!" -sound Glass
|
|
```
|
|
|
|
If your terminal app doesn't appear in Notification settings, it may need to send at least one notification first to register. See [Troubleshooting](../reference/troubleshooting.md) for more details.
|