# Reporting issues

1.Click on `view` --> `toggle developers tools` (or `⌥` + `⌘` +`i` )\
\
2.In the new panel, click on `console`, if you are not already on it

![click on console to view errors](https://3454478899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LzxDa5M0ZjC8OZg1Atb%2F-M-MK186cFImFf1uErFw%2F-M-MKkHvCY3tFUg3WP-l%2FScreen%20Shot%202020-02-05%20at%204.51.41%20PM.png?alt=media\&token=9b34340d-1a10-481c-9288-9f7a274ecdb8)

if you see any red error message, feel free to take a screenshot. 

3.[Raise an issue](https://github.com/pietrop/digital-paper-edit-electron/issues/new?assignees=pietrop\&labels=bug\&template=bug_report.md\&title=), and upload the screenshot alongside a description.

This will provide useful context to help narrow down the context of a problem.

{% hint style="warning" %}
Note that every time you restart the app the `console` gets wiped, and it is therefore only representative of the current "session".
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://autoedit.gitbook.io/autoedit-3-user-manual/reporting-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.