You stay in control. The agent always opens a PR, it never merges to your default branch. Reviewers approve the fix before it reaches production.
Enable from the Bolt UI
In the schedule’s Self-healing section, selecting an agent enables self-healing:- Select a Channel — the Slack channel the agent runs in. It must already be configured as a Slack notification channel on this schedule.
- Select an Agent name — the DinoAI programmable agent that diagnoses and fixes the run. The list is populated from
.dinoai/agents/*.ymlon the schedule’s Git branch. - Save the schedule.
Configure from YAML
If you manage schedules as code, add aself_healing block to the schedule:
What happens when a run fails
- The standard failure notification posts to every Slack channel in
notifications.slack_channels. - In the Self-Healing channel, Paradime posts
🦖 Self-healing enabled — starting healing session...into the failure thread and triggers the DinoAI agent. - In every other notification channel, Paradime posts
🦖 Self-healing started in #<healing-channel>so reviewers know where to follow along. - The agent works in-thread, posts progress, and ends with a PR link for the proposed fix.
- If the same schedule has been self-healed recently, the agent is given a summary of those prior sessions so it doesn’t duplicate work — for example, if an open PR already proposes a fix.
Related
- Notification Settings - Configure the Slack channel Self-Healing reuses
- Schedules as Code - Configuration Reference — Full YAML schema
- DinoAI Self-Healing - How the agent diagnoses and fixes the failure
- Fix with DinoAI - Manual one-click equivalent
- Programmable Agents - Author a custom
agent_name
Define this as code
Configure the
self_healing block (enabled, slack_channel, agent_name).