singularity/singularity-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
singularity-forge/gitbook/configuration/notifications.md
ace-pm 35dc87ef53 chore: sync workspace state after rebrand 
- Rebrand commits already in history (gsd → forge)
- Sync pre-existing doc, docker, and CI config updates
- All rebrand artifacts verified in place:
  * Native crates: forge-engine, forge-ast, forge-grep
  * Log prefixes: [forge] across 22+ files
  * Binary: ~/bin/sf-run
  * Workspace scopes: @sf-run/*, @singularity-forge/*
  * Nix flake: Rust toolchain ready

System ready for: nix develop && bun run build:native

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-15 14:54:20 +02:00

1.3 KiB
Raw Blame History

Notifications

SF sends desktop notifications during auto mode to keep you informed without watching the terminal.

Configuration

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

SF uses terminal-notifier when available, falling back to osascript.

Recommended: Install terminal-notifier for reliable delivery:

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: 
    terminal-notifier -title "SF" -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 for more details.