> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/dino-ai/bolt-pipeline-agent/fix-with-dinoai.md).

# Fix with DinoAI

When a [Bolt run fails](/app-help/products/bolt.md), DinoAI can go beyond just explaining what went wrong — it can fix it. The **Fix with DinoAI** button spins up a full Slack Agent session scoped to the failed run, implements the fix in your codebase, and opens a PR for your team to review.

### How It Works

When you click **Fix with DinoAI**, the agent:

1. Reads the Bolt run logs from the failed run to understand exactly what went wrong
2. Spins up a Slack Agent session and posts the analysis to your connected Slack channel
3. Creates a new branch in your connected repository
4. Implements the fix directly in the codebase
5. Opens a pull request for your team to review and merge

The entire process runs in the background. You'll see progress updates and the final PR link posted in Slack.

<div data-with-frame="true"><figure><img src="/files/BKGz4aOBPWiTKjyHawBu" alt="" width="563"><figcaption></figcaption></figure></div>

### Triggering a Fix

When Bolt posts a run failure notification to Slack, the thread includes a **Fix with DinoAI** button alongside the error summary. Click it directly from the thread to kick off the fix.

### Example

The screenshot below shows a Bolt run failure posted to Slack. The `dbt build` command failed because a model references a source that doesn't exist in the project. DinoAI surfaces the root cause, an action plan, and the **Fix with DinoAI** button — all in the same Slack thread.

Clicking **Fix with DinoAI** will spin up an agent session, create a branch, resolve the missing dependency, and open a PR.

<div data-with-frame="true"><figure><img src="/files/r6V9U1a5SdaKKAQwTyso" alt=""><figcaption></figcaption></figure></div>

> **You stay in control.** Fix with DinoAI always opens a pull request — it never merges directly to your default branch. Your team reviews and approves before anything reaches production.

### What DinoAI Has Access To

To implement the fix, the agent uses:

* **Bolt run logs** — the full output of the failed command, including error messages and stack traces
* **Your connected repository** — cloned from the workspace selected at session start
* **Warehouse connection** — to run validation queries if needed
* **Slack** — to post progress updates and the final PR link

> The environment used (warehouse connection, integrations, repository) is determined by the workspace configured in [DinoAI Background Agent](/app-help/products/settings/connections/dinoai-background-agent-environment.md)

### Related

* [Run Summaries](/app-help/products/dino-ai/bolt-pipeline-agent/production-pipelines.md) — Understand what went wrong before triggering a fix
* [Self-Healing](/app-help/products/dino-ai/bolt-pipeline-agent/self-healing.md) — Automatically fix and re-run pipelines without manual intervention
* [Slack Agent](/app-help/products/dino-ai/slack-agent.md) — How the underlying agent session works


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paradime.io/app-help/products/dino-ai/bolt-pipeline-agent/fix-with-dinoai.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.