> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/screen-recorder/settings/open-saved-recording.md). # Open Saved Recording Automatically open your capture in a new tab after upload. Choose whether Screendesk opens your uploaded capture in a new tab. This setting applies to screenshots, screen recordings, and Instant Replay. ## Change the setting Open the extension's **Settings** and turn **Open Saved Recording** on or off. Your choice saves automatically. * **On:** the uploaded capture opens in a new tab when upload finishes. * **Off:** you stay on your current tab and receive an upload notification. Review the capture before choosing **Upload**. This setting controls what happens after upload; it does not replace the review screen. See [Review and share](/screen-recorder/review-and-share.md) for the complete workflow. --- # 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.screendesk.io/screen-recorder/settings/open-saved-recording.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 `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.