> 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/crash-reporting/crashes-for-agents.md).

# Crashes For Agents

Structured crash context that your AI coding agent can actually consume — without blowing up the context window.

Crashes have thousands of occurrences. Reviewing them one by one is impossible, and feeding raw crash data into an AI agent burns tokens and hits context limits fast. Luciq's engine processes those occurrences and distills them into structured, AI-ready aggregations — the kind agents can consume, reason over, and act on.

**The result:** full crash context available in your IDE, with no dashboard context-switching required.

### How It Works

When you open a crash in the **AI debugging assistant**, you get two modes:

<table><thead><tr><th width="141.4296875">Mode</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Debug mode</strong></td><td>Interactive AI analysis for investigating the crash with follow-up questions.</td></tr><tr><td><strong>Agent mode</strong></td><td>Structured crash aggregations formatted for your AI coding agent. Copy or export as Markdown, then paste directly into Cursor, Claude Code, Copilot, or any agent.</td></tr></tbody></table>

Agent mode is where Crashes for AI Agents lives. It gives your agent the distilled signal it needs — not the raw noise.

<figure><img src="/files/tkJrruquPewCInIiv8l9" alt=""><figcaption></figcaption></figure>

### What's in an Aggregation

Each aggregation covers the full crash picture across all occurrences, structured into sections your agent can parse and act on:

**Crash overview** A top-level summary: total occurrences, affected users, first seen, and last seen — with app version pinpointed.

**Stacktrace** The full symbolicated stacktrace with app frames highlighted. Frames are labeled by origin (app code vs. system), so your agent knows exactly where to look.

**Environment** Distribution breakdowns across device model, OS version, app version, and app status (foreground/background). Your agent sees which configurations are hit hardest — e.g. "67% of occurrences on OS Level 35."

**Device health** Hardware metrics at crash time — memory usage, battery level, storage, and session duration — with mean, p50, and p90 distributions. Surfaces low-memory or long-session patterns that raw stacktraces miss.

**Screen flows** The navigation paths users took before crashing, ranked by frequency. Helps your agent understand the user journey and reproduce the conditions.

**Crash screens** The specific screens active at crash time, with occurrence counts and percentages. Narrows down which view or fragment is in the hot path.

### Privacy & AI Processing

> **No LLM calls are required.** Crashes for AI Agents runs entirely on Luciq's own data processing engine. No crash data is sent to an external model to generate the aggregations.
>
> The one exception is **Screen flows**: if screen flow summarization is enabled for your app, screen names are passed to an LLM to generate path labels. This involves no PII — only screen names (e.g. `MainActivity → ReadingStatsFragment`). This can be disabled per request if your organization has AI or LLM restrictions.

### Availability

Crashes for AI Agents is available across **all platforms** and requires only an **app token** to enable. Contact your success manager or reach out to the team to enable it.

### Related

* [Luciq MCP Server](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server) — Pull crash aggregations directly into your coding agent via MCP, no dashboard required.
* [Agent Skills](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/agent-skills) — Methodology that turns crash data into a real fix, end-to-end.
* [AI Debugging Assistant ](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/resolve-agent/ai-debugging-assistant)— Debug mode for interactive crash analysis.


---

# 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/crash-reporting/crashes-for-agents.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.