> For the complete documentation index, see [llms.txt](https://docs.ostara.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ostara.dev/features/application-features/manage/caches.md).
# Caches
### Overview
Caches at the application level is exactly the same as the instance level [Caches](/features/instance-features/manage/caches.md), but apply their changes to every active instance within the application.
Evicting a cache will attempt to evict it for all active instances, and cache statistics when present represent an aggregation of all instances where such statistics were found.
### Usage
There are 3 ways to evict caches.
1. Click on the broom icon next to an individual cache
2. Check several caches, and click on the broom icon in the green bar that appears
3. Click the broom icon at the top right, to evict all caches
When the **Cache Statistics** ability is present, the cache rows become expandable, and upon expansions display the cache statistics.
### Required Abilities
* [Caches](/features/abilities.md)
* [Cache Statistics ](/features/abilities.md#abilities)(For statistics only)
---
# 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://docs.ostara.dev/features/application-features/manage/caches.md?ask=&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.
