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

# Logs

Where to find your task logs in Refract, and what the app data dev logs are (and are not) for.

Refract has two kinds of logs: task logs you view in the bot, and dev log files in the app data folder. For checking what a task did, task logs are the ones you want.

## Task logs: right-click the task

Right-click any task and click **View Logs**. This is the user-facing log: it shows what that task has been doing, in a readable format. When troubleshooting a task or asked for logs in a ticket, this is the log to check.

## Dev logs: the app data folder

Refract also writes log files to its app data folder on your machine.

{% hint style="warning" %}
**App data logs are not user friendly, and they are not designed to be.** A lot of things are missing from them. They exist for our development team, not for users, so do not try to troubleshoot from them. Your logs are the right-click **View Logs** on a task. Only dig out the app data files if support asks you for them.
{% endhint %}

If support does ask, here is where the folder lives:

{% tabs %}
{% tab title="Windows" %}

1. Press **Win + R** to open the Run box.
2. Type `%appdata%` and press Enter.
3. You land in `AppData\Roaming`. Open the **Refract** folder.

Or in File Explorer: click the address bar, type `%appdata%`, press Enter, and open the **Refract** folder.
{% endtab %}

{% tab title="Mac" %}

1. Open **Finder** (or click the desktop so Finder is active).
2. Press **Cmd + Shift + G** to open the Go to Folder box.
3. Type `~/Library/Application Support` and press Enter.
4. Open the **Refract** folder.

Or from the Finder menu bar: click **Go**, then **Go to Folder...**, and enter the same path.
{% endtab %}
{% endtabs %}


---

# 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://help.refractbot.com/general-setup/logs.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.