> 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/beta-access.md).

# Beta Access

Firstly, there is TV Rename itself. Hidden away in the **Options>Preferences** [***General***](https://www.tvrename.com/menu/preferences/general.md) tab is a “Mode:” drop down which is probably set to “Production”. Changing this to “Beta” will make a new **Beta** menu appear between **View** and **Help**. This menu will give you access to functionality that is being developed for future inclusion.

{% hint style="info" %}
**Note:** If you change the mode to “Beta”, you may find that you start to get alerts for new test versions (Betas and Release Candidates) of the software. If you’d like to try a newer version that may still have a bug or two then please go ahead and do the upgrade, otherwise setting “Mode:” back to “Production” will stop the alerts.
{% endhint %}

Additionally, for a longer term view of what’s going on you can visit the “[Roadmap](https://github.com/TV-Rename/tvrename/milestones?direction=asc\&sort=due_date\&state=open)” which will give you a high level view of what's planned for when.

{% content-ref url="/pages/n2pa9aX83ZrXITCvnKPF" %}
[Beta Menu](https://www.tvrename.com/menu/beta-menu.md)
{% endcontent-ref %}


---

# 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/beta-access.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.
