Long-running background sessions — data pipelines, AI training jobs, test runners — fail silently far too often. You find out an hour later when you check the output, not within seconds when there's still time to restart and recover.
VibeControls webhooks change the notification model from pull to push. Create a webhook subscription: select session.error and session.stopped events, and point the endpoint at your Slack incoming webhook URL.
VibeControls signs every payload with HMAC-SHA256 so your endpoint can verify authenticity. The payload includes the session name, agent hostname, error message, and exit code. Configure Slack to format and route it to the right channel — maybe #infra-alerts for production agents, #dev-channel for staging.
From the moment a session fails, your team has the alert in Slack. The webhook delivery log in VibeControls shows every event — delivered, failed, retry status — so you can debug notification reliability too. Retry backoff (30s, 5m, 30m) means transient webhook endpoint failures don't lose events.
Do it yourself
Set up a signed webhook subscription so a Slack channel gets an instant alert whenever a VibeControls session fails or stops.
In Slack, add an Incoming Webhook app to the channel where you want alerts, then copy the generated webhook URL.
You should see: You have a Slack webhook URL ready to paste into VibeControls.
Ready to make this your story?
