> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/updates/updates-miscellaneous.md).
# Updates - Miscellaneous
Recent highlights only (rolling window)
For live updates, use:
*
*
## Scope of this page
* Only highlights from the last 120 days are kept here.
* Current window: **November 9, 2025 to March 9, 2026**.
* Anything older should be removed after permanent docs are updated.
* This page is not a long-term changelog archive.
## Recent highlights (rolling)
* No curated highlights are currently pinned in this docs branch. Use the live sources above.
## Editor maintenance rule
* Add only recent, high-signal items in the active rolling window.
* Prefer documenting stable behavior in guides/reference pages, not in update logs.
* Remove items as they age out of the window.
---
# 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.vdo.ninja/updates/updates-miscellaneous.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.