> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/linkrui/preferences/local-asset-cache-folder.md).
# Local Asset Cache Folder
Set where LinkrUI stores cached assets.
#### Local Asset Cache Folder
The default location of the Local Asset Cache Folder is in the documents[^1] folder on your local device.
You can choose a different location for the LinkrUI cache folder by selecting the Choose button.
In addition, LinkrUI allows you to force clear the asset cache folder.
When you select the Clear Cache button, the asset's cached resources are immediately removed from your local device.
{% hint style="info" %}
Clear Cache only removes assets that are not open in any app.
If assets are still open, LinkrUI shows a dialog listing the assets that were not cleared.
{% endhint %}
[^1]: `C:\Users\\Documents`
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.santacruzsoftware.com/linkrui/preferences/local-asset-cache-folder.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.