Why
Amp's entire async story is Slack: a scheduled agent DMs you when something finishes or stalls, and their users live with it happily despite no push existing at all. Teams live in Slack, and a notification channel that needs no device pairing has its own value.
Rough scope
- Settings holds a Slack webhook URL or bot token, per user, stored on the daemon.
- Daemon posts on: session finished after a long run, session blocked on a prompt (from the needs-you detection), and optionally a daily digest of the insights totals.
- No flue infrastructure, no OAuth app to start with. A raw incoming webhook covers the solo case in an afternoon.
Priority
Backlog. Web push (see the push notifications epic) beats this for the solo phone-in-pocket case and shares the same triggers, so this lands after that detection work exists. This is the cheap second consumer of it.
Why
Amp's entire async story is Slack: a scheduled agent DMs you when something finishes or stalls, and their users live with it happily despite no push existing at all. Teams live in Slack, and a notification channel that needs no device pairing has its own value.
Rough scope
Priority
Backlog. Web push (see the push notifications epic) beats this for the solo phone-in-pocket case and shares the same triggers, so this lands after that detection work exists. This is the cheap second consumer of it.