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

# AI & Intelligence

- [AI overview](https://docs.screendesk.io/debug-with-ai/overview.md): Understand how Screendesk AI turns customer evidence and support knowledge into a clearer next step.
- [AI settings](https://docs.screendesk.io/debug-with-ai/ai-settings.md): Control workspace AI processing, automatic report analysis, AI labels, and your Gemini API key.
- [Report intelligence](https://docs.screendesk.io/debug-with-ai/ai-summary.md): Use AI summaries, issue findings, and reproduction steps to understand recordings and reports faster.
- [AI transcripts](https://docs.screendesk.io/debug-with-ai/ai-transcripts.md): Search spoken content, jump to timestamps, and copy or export transcripts from eligible recordings.
- [Data sources](https://docs.screendesk.io/debug-with-ai/data-sources.md): Connect trusted documentation, files, text snippets, and resolved support conversations to Screendesk AI.
- [AI Resolution](https://docs.screendesk.io/debug-with-ai/ai-resolution.md): Investigate recording-linked Zendesk tickets and give agents evidence-backed private notes to review.
- [AI in your helpdesk](https://docs.screendesk.io/debug-with-ai/ai-in-your-helpdesk.md): See how recording requests, report intelligence, knowledge sources, and AI Resolution fit your support workflow.
- [AI Suggest (legacy)](https://docs.screendesk.io/debug-with-ai/ai-suggest.md): Find the current guides for report intelligence, data sources, and Zendesk AI Resolution.
- [MCP](https://docs.screendesk.io/debug-with-ai/mcp.md): Connect AI assistants to your workspace to inspect recordings, captures, logs, and network data.
- [CLI](https://docs.screendesk.io/debug-with-ai/cli.md): Inspect Screendesk evidence from the terminal, scripts, CI, and coding agents.


---

# 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.screendesk.io/debug-with-ai.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.
