> For the complete documentation index, see [llms.txt](https://www.tvrename.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.tvrename.com/help-and-support/feedback.md).

# Support & Feedback

## Questions & Issues

Your starting point for discussing any questions, issues and bugs should be the [TV Rename Forum](https://groups.google.com/forum/#!forum/tvrename). Here you can search to see if the question or issue has been raised before. If you can’t find a solution to your conundrum just create a “NEW TOPIC” and ask away.

A number of people (including the developers) keep a “weather eye” here; it shouldn’t be too long before you get a response. If requested please pack up your configuration files and send them to us; this will help with the diagnosis (see the [“Technical Guide”](https://www.tvrename.com/technical/logs-and-configuration.md) for details).

{% hint style="danger" %}
**For security reasons it is advisable to only send the log/configuration package to the person helping you with your problem**.
{% endhint %}

## Reporting Bugs

If you’ve found a bug that has been verified, please make sure it has been raised on the [GitHub Bug Tracker](https://github.com/TV-Rename/tvrename/issues). Once it’s there it will definitely get the developers' attention (and hopefully a quick response).

## Requests for New Ideas & Features

If you have an idea for a great new feature you can post it in our [GitHub ](https://github.com/TV-Rename/tvrename/issues/new/choose)(as well as discussing it in the forum). Apart from suggesting new features, GitHub lets you comment and vote on other ideas and suggestions.


---

# 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://www.tvrename.com/help-and-support/feedback.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.
