---
title: Ask AI
description: Get an AI-generated diagnosis with cause, explanation, and suggested fix for any failed build or deployment in Capawesome Cloud.
---

# Ask AI

**Ask AI** is the first feature in [Capawesome Cloud Assist](./index.md). On any failed build or deployment, click the **Ask AI** button to get a structured summary of what went wrong and a suggested fix — without leaving the [Capawesome Cloud](/){:target="_blank"} Console.

## How It Works

On a failed build or deployment, members with write access see an **Ask AI** button (sparkles icon, "New" badge) in the toolbar.

1. Open the failed build or deployment in the [Capawesome Cloud Console](https://console.cloud.capawesome.io){:target="_blank"}.
2. Click **Ask AI**.
3. A consent dialog explains what data is shared. Click **Generate**.
4. After a few seconds, a markdown summary appears in the dialog with three sections:
    - **Cause** — the line(s) that actually broke the job.
    - **Explanation** — why it broke, in plain English.
    - **Suggested fix** — a concrete next step, often with a `bash` snippet.
5. Click **Copy** to put the raw markdown on your clipboard. Paste it into a PR description, ticket, Slack message, or as context into a local AI coding agent like [Claude Code](https://www.anthropic.com/claude-code){:target="_blank"} or [Cursor](https://www.cursor.com/){:target="_blank"} to apply the fix directly to your codebase.

## Anatomy of a Result

Every Ask AI response has the same three sections, rendered as markdown in the dialog and available verbatim via the **Copy** button.

!!! example "Sample result"
    **Cause**

    `android/app/build.gradle:42` — Could not resolve `com.google.firebase:firebase-bom:33.0.0`.

    **Explanation**

    Your Android build failed because Gradle could not download the `firebase-bom` artifact at version `33.0.0` from any configured Maven repository. This usually means the version doesn't exist yet, was renamed, or your `repositories` block is missing Google's Maven repo.

    **Suggested fix**

    Pin `firebase-bom` to a published version and confirm `google()` is listed under `repositories` in `android/build.gradle`.

    ```groovy
    implementation platform('com.google.firebase:firebase-bom:32.7.0')
    ```

The output is capped at around 400 words to keep the result a summary rather than a wall of text. Code snippets are formatted as fenced code blocks so they paste cleanly into PRs, tickets, or chat.

## Workflow Integrations

Ask AI's output is plain markdown by design. A few patterns work well:

- **Paste into a PR description.** When the failure prompted a fix, dropping the diagnosis into the PR body gives reviewers the full context without making them re-read the logs. Renders correctly in GitHub, GitLab, Bitbucket, and Azure DevOps.
- **Hand off to a local AI coding agent.** Paste the diagnosis as context into [Claude Code](https://www.anthropic.com/claude-code){:target="_blank"}, [Cursor](https://www.cursor.com/){:target="_blank"}, or any other agent. The agent now has the exact cause and suggested fix, and can apply the change directly to your codebase.
- **Async debugging via shared cache.** When someone links to a failed build in chat or a stand-up, anyone with permission sees the same cached diagnosis instantly — no duplicate AI runs, no inconsistent answers across teammates.