> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/release-notes/2025-or-earlier.md).

# 2025 or earlier

- [4.13](https://docs.verge.io/release-notes/2025-or-earlier/4-13-release-notes.md): Release notes for the VergeOS 4.13 series: hardware passthrough (USB/PCI/SRIOV), experimental vGPU live migration, enhanced bonding with split brain detection, multipath vSAN, and HA improvements.
- [4.12](https://docs.verge.io/release-notes/2025-or-earlier/4-12-release-notes.md): Release notes for the VergeOS 4.12 series: dark mode UI, TOTP two-factor authentication, nested virtualization with live migration, offline licensing, faster network migrations, and vSAN meta cache.
- [4.11](https://docs.verge.io/release-notes/2025-or-earlier/4-11-release-notes.md): Release notes for the VergeOS 4.11 series: Site Manager for global administration, Recipe Marketplace, OIDC authentication, VM Export, TPM support, and network and vSAN performance improvements.
- [4.10](https://docs.verge.io/release-notes/2025-or-earlier/4-10-release-notes.md): Release notes for the VergeOS 4.10 series: NVIDIA vGPU support, CPU C-States management, enhanced vSAN performance, CPU pinning, and improved GPU passthrough and live migration.
- [4.9](https://docs.verge.io/release-notes/2025-or-earlier/4-9-release-notes.md): Release notes for the 4.9 series of VergeOS, featuring a complete UI revamp, email-based two-factor authentication, GPU pass-through, port mirroring, and enhanced snapshot and NAS management.


---

# 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.verge.io/release-notes/2025-or-earlier.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 `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.