> 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/guides/features/automating.md).

# Automating

TV Rename aims to do as much as it can to automate the storage of media files. To make the process as automated as possible it can:

* ***Auto Add shows*** – see ‘[Automated Addition](https://www.tvrename.com/guides/features/adding-movies-and-tv-shows.md)’.
* ***Auto folder creation*** – TV Rename can be set up via preferences [(**here**)](https://www.tvrename.com/menu/preferences/scan-settings.md) to automatically create folders for shows and series. This will create based on the defaults.
* ***Auto folder & file deletion*** – TV Rename can identify files and folders that can be removed and then get rid of them.
  * *‘Delete Empty Folders after moving Files’* - Review Folders as movie files are copied out of the folder. Sometimes files are downloaded with many accompanying files which are not needed. If this is the case then this function can clean up the unused files. [**It is configured here**](https://www.tvrename.com/menu/preferences/folder-deleting.md).
  * *‘Clean-Up’* - Files and folders in the download directory that match episodes already in the library. This is useful when something else keeps hold of the lock on the files and they cannot be removed after the move operation, but occasionally deletes ‘PROPER’ or improved files that are improvements to what is already in the library. [**It is set up here**](https://www.tvrename.com/menu/preferences/folder-deleting.md).
  * Suggest recycling files/folders rather than deleting [**as specified here**](https://www.tvrename.com/menu/preferences/folder-deleting.md).
* ***Multi-episode Merging***
  * Proactive. TV Rename can be pro-actively set up to create merge rules. If a library file [(**see here**)](https://www.tvrename.com/menu/preferences/scan-settings.md) or a downloaded file [(**see here**)](https://www.tvrename.com/menu/preferences/search-folders.md) matches a multi episode file then it will automatically create a merge rule.
  * Reactive. [**Tools>Find Merged Episodes...**](https://www.tvrename.com/menu/tools-menu/find-merged-episodes.md) will scan the library and look for files that look like they are multi-episode files based on a few criteria:
    * The two (or more) episodes have the same air-date
    * The episodes' names are similar.
    * One or more of the episodes are missing.
    * The file that is on disk is larger than normal which would indicate that there is more than one episode in the file.
* ***Auto-update***
  * On start-up TV Rename will check to see whether it is on the latest version and suggest that it is updated if not (set on the [**App Updates**](https://www.tvrename.com/menu/preferences/app-updates.md) tab of **Options>Preferences**).
  * From “Help” in the menu bar you can manually check for an update.
* ***Auto Scanning***
  * As files change (set on the [**Search Folders**](https://www.tvrename.com/menu/preferences/search-folders.md) tab of **Options>Preferences**) or on a fixed period (set on the [**Scan Settings**](https://www.tvrename.com/menu/preferences/scan-settings.md) tab).
* ***Auto Upgrades***
  * As better quality files are identified then they are used to replace lesser quality versions.


---

# 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/guides/features/automating.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.
