StayFresh

Static archive of workflow research and patterns

March 2026

psay Agent Notifications

Initial reconnaissance started with KittenTTS and purr.

Execution moved to Piper because the Python toolchain was cleaner for local automation, scripting, and reproducible agent setup.

Three Solid Use Cases

Use CaseWhy It Matters
Long-running builds/testsStops terminal polling and returns focus only when work is done.
Agent handoff pointsFlags when an agent needs human input so loops do not stall silently.
Risky local operationsAnnounces success/failure and duration for migrations, deploy scripts, and data jobs.

Advantages

Local Push Notifications on macOS

Yes. This is straightforward with Notification Center and does not require a cloud service.

Preferred channel is terminal-notifier when installed; fallback is osascript "display notification ...".

Hacker News Signal

Engineering Enhancement Implemented

scripts/psay-notify.sh is the highest-leverage first upgrade for this setup.

It wraps any command, tracks runtime, emits local notification on completion, and speaks status through Piper (or falls back to say).

# notify + speak only when runtime >= 15s
scripts/psay-notify.sh --threshold 15 --title "Agent Run" -- make test

# quiet mode: desktop notification only
scripts/psay-notify.sh --no-speak --threshold 5 -- pnpm build

Why This Enhancement Wins

It solves the real bottleneck first: delayed awareness of completion and failure.

No retraining, no custom voice dataset, no external infra. Just faster operator feedback loops with local-only primitives.