> 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/keyboard-shortcuts.md).

# Logs

If you are having problems with TV Rename or maybe someone on the [forum](https://groups.google.com/forum/#!forum/tvrename) has asked you about the content of your log file you have a couple of options…

If you are happy navigating through the Windows file structure the log file (TVRename.log) can be found in: -

> \Users\\\<username>\AppData\Roaming\TVRename\log\\

However, if you are uncomfortable doing this there is a handy entry in the **Help** menu (**Help>Log**).

This will either “tee” the log data (as it happens) into a new window so you can read it or copy the relevant bits for pasting in a [forum](https://groups.google.com/forum/#!forum/tvrename) message.

*To use this feature click **Help>Log** first and then run the action (a Scan for example) you wish to monitor/capture.*

{% hint style="info" %}
Optionally, if you wish to view the entire log file clicking the `View Full Log` button in the bottom right corner of the window will open the file in Notepad.
{% endhint %}

More detailed information about the logs can be found in the [Technical Guide](https://www.tvrename.com/technical/logs-and-configuration.md).


---

# 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/keyboard-shortcuts.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.
