> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/detect-agent.md).

# Detect Agent

Most of what breaks in a mobile app is never reported. Users abandon a flow, retry, or quietly churn, and nothing reaches your team. Detect Agent looks through your Session Replay recordings and surfaces those problems on its own, without anyone filing a report.

It detects two kinds of issue:

* [**Broken Functionality**](/product-guides-and-integrations/product-guides/ai-features/detect-agent/broken-functionality.md) - dead buttons, forms that fail to submit, and flows that break mid-process.
* [**Visual Issues**](/product-guides-and-integrations/product-guides/ai-features/detect-agent/visual-issues.md) - misaligned or overlapping elements, layout shifts, text that clips or overflows, and other rendering defects.

Both are built on Session Replay, both run server-side with no SDK changes or instrumentation, and both behave the same way once detected:

* **Grouped by default.** Issues describing the same underlying problem are collected into a single group with an occurrence count, so a defect spanning hundreds of sessions reads as one item rather than hundreds. You can still open any individual occurrence to see the exact screenshot and session behind it.
* **Open to feedback.** Every detection can be marked valid or not valid, and ungrouping asks you why. That feedback improves detection and grouping accuracy over time.
* **Surfaced alongside everything else.** Detected issues appear on the AI Issues page and in the [Issues List](/product-guides-and-integrations/product-guides/inbox/issues-list.md) on the Inbox page, next to your crashes, bugs, and performance issues.

Start with the page for whichever detection type you're setting up.


---

# 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.luciq.ai/product-guides-and-integrations/product-guides/ai-features/detect-agent.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.