> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr/insights-and-tips-cortex-xdr/release-and-documentation-updates.md). # Release and documentation updates Cortex XDR is delivered as a cloud service and is updated regularly. New features are announced in release notes before and when they reach your tenant. Detection and agent content updates are delivered separately and more often. * **Release notes:** organized by release and month. * **Agent releases:** see the [Cortex XDR agent documentation](https://cortex-docs.paloaltonetworks.com/cortex-xdr-agent-docs/readme) for agent release notes and end-of-life information. * **Analytics content:** see the [Analytics alerts reference](https://cortex-docs.paloaltonetworks.com/analytics-alerts/cortex-analytics-alert-reference) for current detections. Product documentation on this portal is the single source of truth for administrator guides, references, and APIs. --- # 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://cortex-docs.paloaltonetworks.com/cortex-xdr/insights-and-tips-cortex-xdr/release-and-documentation-updates.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.