> For the complete documentation index, see [llms.txt](https://docs.acecentre.org.uk/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecentre.org.uk/products/eyecommander/bug-reports-or-feature-requests.md).

# Bug Reports or Feature Requests

## Online form

If you have found a bug or you would like to request a new feature then you can let us know. [Fill in this online form with your idea or bug](https://forms.office.com/r/ThSe8Mgx6Y). Please note that your response will be publicly shared (without your email) on our bug tracking system.

If you cannot use the form or want to provide more detail then email me at <ghenderson@acecentre.org.uk>

## Github

If you are familiar with GitHub then you can open a detailed issue on our [Github repository](https://github.com/acecentre/eyecommander) outlining your request and we will get back get back to you.


---

# 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.acecentre.org.uk/products/eyecommander/bug-reports-or-feature-requests.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.