> 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-vdo.ninja.md). # Updates - VDO.Ninja Recent highlights only (rolling window) For real-time release notes and announcements, use: * [https://updates.vdo.ninja](https://updates.vdo.ninja/) * [https://discord.vdo.ninja](https://discord.vdo.ninja/) ## Scope of this page This page is intentionally short to reduce stale or cached snippets. * 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 the permanent docs are updated. * This page is not a long-term changelog archive. ## Recent highlights (rolling) * **Approval-system room controls** Added `&requireapproval`, `&roomcap` / `&rcap`, and `&roomkey` / `&rk` for claimed-room admission control. Trusted room keys can bypass approval and cap checks. These controls are tied to the current director session. * **Queue and co-director sync improvements** Held-guest activation state now syncs correctly to co-directors through the normal director state flow, and `&hold` / `&holdwithvideo` activation behavior is documented in line with the current code path. * **Chunked/WebCodecs reliability controls** Recent chunked work includes `&chunkfec`, `&chunknack`, `&chunkbuffer`, `&chunkbufferfloor`, `&chunkbufferceil`, `&chunkjitterslack`, `&chunkadapt`, and `&chunkprofile` for opt-in reliability, buffering, and adaptation experiments. * **PTZ and recovery controls** Added or expanded `&pendingicettl`, low-latency chunked presets, PTZ remote actions, and the dedicated PTZ control surface at . * **Standalone helper app growth** New public helper surfaces now include the standalone Screen Recorder, Game Capture app, Ninja OBS Plugin, and Ninja VST3 Plugin. ## Editor maintenance rule * Add highlights only for recent changes inside the active rolling window. * For each highlight, ensure a stable doc page exists in the correct section. * Remove highlights when 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-vdo.ninja.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.