> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/ai/ai-in-the-dashboard.md).

# AI in the dashboard

AI features built into the Currents dashboard: the likely cause of a failed test, and a plain explanation of what any test checks

Use these pages to get an AI answer about a test right in the dashboard, without connecting an agent. Currents sends the test's recorded data to an AI model and shows the answer in the test's **Insights** section.

| You want to                                      | Read                                                                                           |
| ------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
| Find out why a test failed, with suggested fixes | [AI Failure Analysis](https://docs.currents.dev/ai/ai-in-the-dashboard/ai-failure-analysis.md) |
| See what a test does and what it checks          | [Explain this test](https://docs.currents.dev/ai/ai-in-the-dashboard/explain-this-test.md)     |

Both need the **AI assistance** setting. An organization admin turns it on once, in the organization settings under **AI and data**. See [Turn on AI Failure Analysis](https://docs.currents.dev/ai/ai-in-the-dashboard/ai-failure-analysis.md#turn-on-ai-failure-analysis).

To have an agent fix the failure in your code, see [Fix failing CI tests](https://docs.currents.dev/ai/agentic-testing/fix-failing-tests.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/ai/ai-in-the-dashboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
