> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/changelog/readme.md).

# Changelog

StrongDM provides the following resources in this section for tracking changes to StrongDM software, in addition to occasional announcements or migration guides regarding current or coming-soon changes:

* [Monthly Recap](/changelog/monthly-recap.md) - This is a curated summary of important changes to the platform, released early each month and covering changes that occured during the previous calendar month.
* [Release Notes ](/changelog/release-notes.md)- An itemized list of software releases with public-facing changes and the specific release notes for those releases.
* [Archives](/changelog/archive.md) - Release note summaries from previous years.
  * [2023 Release Notes](/changelog/archive/2023.md)
  * [2022 Release Notes](/changelog/archive/2022.md)
  * [2021 Release Notes](/changelog/archive/2021.md)
  * [2020 Release Notes](/changelog/archive/2020.md)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.strongdm.com/changelog/readme.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 `build a script that syncs our docs to a CMS` 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.