Skip to main content
When a Bolt run fails on a schedule with Self-Healing enabled, Paradime automatically triggers a DinoAI agent against the failure — inside the same Slack thread as the failure notification. The agent diagnoses the run, implements a fix, and opens a pull request for your team to review.
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.
Prerequisites
  • A Slack notification channel must be configured for this schedule under Notification Settings — Self-Healing reuses the failure-notification thread to run the agent in.
  • Aa Programmable Agent defined under .dinoai/agents/<name>.yml if you want a custom healer instead of the default Bolt-fix agent.

​
Configure from the Bolt UI

In the Bolt schedule editor:
  1. Open the Self-Healing section.
  2. Toggle Enable Self-Healing.
  3. Pick the Slack channel the agent should run in. It must already be configured as a Slack notification channel on this schedule.
  4. Pick an Agent Name from the dropdown — the list is populated from .dinoai/agents/*.yml on the configured git branch. Leave empty to use Paradime’s default Bolt-fix agent.
  5. Save the schedule.

​
Configure from YAML

If you manage schedules as code, add a self_healing block to the schedule:
self_healing.slack_channel must also appear in notifications.slack_channels for the same schedule. The validator rejects the schedule otherwise. The agent threads into the failure notification, so the notification has to exist for the agent to find its thread.

​
What happens when a run fails

  1. The standard failure notification posts to every Slack channel in notifications.slack_channels.
  2. In the Self-Healing channel, Paradime posts 🦖 Self-healing enabled — starting healing session... into the failure thread and triggers the DinoAI agent.
  3. In every other notification channel, Paradime posts 🦖 Self-healing started in #<healing-channel> so reviewers know where to follow along.
  4. The agent works in-thread, posts progress, and ends with a PR link for the proposed fix.
  5. 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.
For the full agent-side narrative, see DinoAI → Self-Healing.

Related topics

Self-HealingBolt Pipeline AgentBolt Pipeline Healerbolt-ci-healerPipeline Insights