> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/reference/step-definitions/cache-content.md).
# Cache content
Starting with DeployR 1.1, this step definition is available for use in task sequences.
When running a caching task sequence, or when you want to cache additional items during OSD, use this step to cache specific items based on their tags.
This step can also be used to cache boot images.
### Options
| Option | Description |
| ----------------------------------- | ----------------------------------------------------------------------------------------- |
| Tag to include | Only content items with this tag are cached. Leave blank to cache all content. |
| Include all active versions | Caches content item versions with a status of **Active**. Default: `true`. |
| Include all in-development versions | Caches content item versions with a status of **In development**. Default: `false`. |
| Cache boot files | Also downloads the Windows PE boot files so they are cached for peering. Default: `true`. |
On the content item, add a tag of your choosing:
Then add the **Cache content** step to the task sequence and specify the tag.
---
# 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://documentation.2pintsoftware.com/deployr/reference/step-definitions/cache-content.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.
