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

# Developer tools

BetterBugs.io automatically attaches technical information and data with every bug report you create for debugging purposes.

Debugging can be difficult without the related technical details of the issue. QA engineers have to worry no more about sending the logs from dev tools separately while reporting the issues to the developers.

BetterBugs.io automatically attaches key information like console logs, network requests and logs, and system information to the generated bug report.

### What are the Technical Details Auto-Attached to Every BetterBugs.io bug report for Debugging Purposes?

#### Quick Overview of BetterBugs.io Bug Report

<table><thead><tr><th width="301.7777099609375">Detail name</th><th>Value(s)</th></tr></thead><tbody><tr><td>Workspace name</td><td>My Workspace (default)</td></tr><tr><td>Project name</td><td>My Project (default)</td></tr><tr><td>Share the report with the integrated tools: "<strong>+ Send to your PM Tool</strong>"</td><td>Jira, Linear, Slack, ClickUp, Asana, GitHub, MS Teams, Trello, Azure Boards, Notion, and others.</td></tr><tr><td>Invite</td><td>Invite members or share using the report link</td></tr><tr><td>Visual proof</td><td>Screenshot, Screen recording, Rewind session video</td></tr><tr><td>Summary</td><td>Bug title, Manually added or AI-generated description of the issue</td></tr><tr><td>Upload files</td><td>Add up to 5 files | Supported formats: Doc, Excel, PDF, Txt, Image, and Video</td></tr><tr><td>Details</td><td>Priority, Status, Assignee, Tags (up to 10)</td></tr><tr><td>Comments/Activities</td><td>System/user generated actions</td></tr></tbody></table>

#### Technical Details for Developers for Manual + AI Debugging Workflows

<table><thead><tr><th width="164">Detail name (from the devtools tabs)</th><th>Value(s)</th></tr></thead><tbody><tr><td>Info</td><td>Timestamp (Time zone when captured, Your time zone, UTC time zone), URL, Network Speed, Device, Browser Mode, Charging Status, Available Battery, Browser, Window Size, Screenshot Dimensions, Extension Version, App Version, Bug Reporter, IP Address, Country, Time zone, User Agent</td></tr><tr><td>Console</td><td>Info, Warning, Log, Error, Network Error</td></tr><tr><td>Network</td><td>Fetch/XHR, JS, CSS, WS, Media, Font, Doc, Manifest, Method, Status</td></tr><tr><td>Backend</td><td>Event logs from Sentry (after Sentry integration)</td></tr><tr><td>Steps</td><td>Page navigation, Network errors, User activities</td></tr><tr><td>MetaData</td><td>Custom data as "<strong>Title</strong> and <strong>Value</strong>"  or <code>key: value</code> pairs added by the reporter</td></tr><tr><td>Application</td><td>Cookies, Local Storage, Session Storage</td></tr><tr><td><a href="/debug-a-report/mcp.md">MCP Server</a></td><td>Documentation link to connect BetterBugs MCP Server for AI debugging </td></tr><tr><td><a href="/debug-a-report/ai-debugger.md">AI Debugger</a></td><td>AI-powered root cause analysis, test cases, and possible solutions</td></tr></tbody></table>


---

# 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.betterbugs.io/product-features/developer-tools.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.