> For the complete documentation index, see [llms.txt](https://djthorpe.gitbook.io/go-llm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://djthorpe.gitbook.io/go-llm/feedback-and-issues.md).

# Feedback & Issues

## Reporting a bug

Open an issue on [GitHub](https://github.com/mutablelogic/go-llm/issues/new), with:

* what you did, and what happened, and what you expected;
* go-llm's version, and how it runs, such as Docker, or `llm run`;
* the provider, and the model;
* any error, from the web UI, the command line, or the server's log.

Leave out API keys, and anything private, from logs and screenshots.

## Asking for a feature

Open an issue saying what you'd like to do, and why. A feature which the assistant can do with a tool is preferred to one in the web UI.

## The roadmap

What's planned is in the [issue list](https://github.com/mutablelogic/go-llm/issues), by milestone:

* [**1.6**](https://github.com/mutablelogic/go-llm/milestone/3)**: Make it work.**
* [**1.7**](https://github.com/mutablelogic/go-llm/milestone/2)**: Add authentication and a workspace.**
* [**1.8**](https://github.com/mutablelogic/go-llm/milestone/1)**: Assistant capabilities and permissions.**

## Security

go-llm has no authentication yet. Don't run it where others can reach it. Report a security issue privately, from the repository's [Security](https://github.com/mutablelogic/go-llm/security) tab, rather than in a public issue.


---

# 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://djthorpe.gitbook.io/go-llm/feedback-and-issues.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.