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

# AI Assistant

The Assistant is a project-aware chat, reached from the navigation rail. It can explain a feature, improve Gherkin, generate test code, triage a failing run, and navigate you to the right view. Conversations are saved per project, so you can return to earlier threads from the list rail.

![The Assistant view](/files/dRH07lzJ9nzsjEETBks8)

## Ways To Reach It

| Entry point                  | What it does                                                                                                                                                 |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Navigation rail → Assistant  | Opens the conversation list and the active chat.                                                                                                             |
| Search bar → "Ask assistant" | Sends whatever you typed in the command bar (Ctrl/Cmd+K) as a new conversation.                                                                              |
| Per-view **Ask AI** buttons  | Runs, Features, and Load results each have an Ask AI button that seeds a conversation with a data-rich summary of the selected run, feature, or load result. |
| **Fix with assistant**       | From a failing test result, opens a guided flow that reproduces the failure and proposes a fix.                                                              |

## What To Ask

* "Why did run #25 fail?" — the Assistant reads the run's results and evidence.
* "Tighten the scenarios in NewFeature.feature" — it can propose Gherkin edits.
* "Summarize load test run #31" — or use the Ask AI button on the load result for the same thing with the data pre-attached.

## Tips

* Quick actions on the empty chat state cover the most common starting points.
* Seeded Ask AI conversations show the summary as your first message — edit and resend it to steer the analysis.
* The Assistant works against the currently selected project; switch projects from the header first if needed.

## Related Help

* [Assistant form reference](/reference/forms/assistant.md)
* [Troubleshoot failed generation](/ai-generation/troubleshoot-failed-generation.md)
* [Run failed](/troubleshooting/run-failed.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 dynamically by asking a question.

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

```
GET https://docs.testvibe.com/assistant.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.