> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/guides/development.md). # Using BugSplat This section includes articles that are useful for using BugSplat and getting the most out of the app. [**Using the App**](/guides/using-the-app.md) - is a walkthrough of the different pages in the app, how to navigate inside the app, and how to begin using the app to view crash data. [**Symbol Files**](/guides/working-with-symbol-files.md) - are a critical component of getting useful data from your crashes. They're also a common stumbling block for new users. [**Table Filtering**](/guides/searching/search.md) - contains instructions on how to search application crash data to find and isolate specific crashes or crash groups. [**Table Grouping**](/guides/searching/grouping.md) - is an overview of how to compare groups of crashes to see into crash and stability trends. [**Grouping Crashes**](/guides/grouping-crashes.md) - define rules that group a set of crashes at some level other than the top level of the call stack. [**Commenting**](/guides/commenting.md) - is BugSplat's built-in comment tool and issue tracker. [**3rd Party Tools**](/guides/integrating-with-tools.md) - compliment your workflow by integrating BugSplat with your issue tracker, messaging app, or another tool. [**API**](/api-reference/web-services.md) – is an overview of the BugSplat API. --- # 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.bugsplat.com/guides/development.md?ask=&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.